Facebook Research

Use this skill when the user needs public Facebook evidence - page/profile posts, direct posts, public group posts, reels, comments, ad-library creative, events, marketplace listings, page profiles, or public search - for a growth, marketing, creator, community, competitor, or funnel decision.

Read only the one narrow reference matching the job.

Collection Routes

Facebook has URL-led routes for public page/profile/group/post content and specialized routes for reels, comments, ads, events, marketplace, pages, and search. Pick the route by user intent; PostPlus handles execution details.

All post collections return output.items[]; fields differ between ordinary posts, group posts and Reels. Follow the selected reference. facebook-group-posts and facebook-groups sample the same public group posts; do not run both as independent corroboration. Both group routes return a chronological post sample with no server-side keyword filter. Missing group membership, founding dates or verification are unavailable, not zero or false.

Use web-search for external source discovery only; its snippets are not Facebook post or comment evidence. Follow references/public-content.md for search-page field reading.

Route

First Question

Ask only when the answer changes the route, source, privacy boundary, sample size, or output shape.

For ads, a product URL, unfamiliar brand, category, or problem is a sufficient seed. Discover related products yourself; follow the ad-specific quantity and stopping rules in references/ads-and-funnel.md.

Do not ask the user for internal route identifiers, schemas, implementation choices, retries, credentials, hidden filters, or internal routing.

Run Discipline

1. Pick one reference and one lane.
2. For ads, collect fresh evidence as described in references/ads-and-funnel.md; do not automatically search the stored ad library. Explicit library browsing is a separate user goal. Otherwise run the smallest real collection that can answer the decision.
3. Parallelize independent sources when they do not depend on each other.
4. If execution succeeds but evidence is empty, sparse, noisy, or off-topic, apply the quality rules below before accepting or exhausting the evidence.
5. Produce JSON as the source of truth and a compact HTML evidence artifact when item-level evidence was collected.
6. Return a short chat answer: scope, counts, strongest finding, biggest gap, artifact path, and next action.

Use only the public filters shown by the selected route.

Public Command Boundary

• Choose the smallest matching research route and run it directly.

• Readiness diagnostics: postplus doctor --skill facebook-research.

• Inspect one route with postplus research run <route> --help when its semantic flags are not already clear.

• Run postplus research run <route> --<semantic flags> --wait --output <result.json>.

• Pass only public URLs, search terms, locations, scope, and result limits.

• For non-ad routes, keep the first pass bounded; expand only after inspecting the first result. For ads, collect toward the requested evidence outcome, using the ad reference. Stop on hard errors. Do not silently swap sources or invent missing data.

• Requested tasks use existing PostPlus credits after the current price and balance are checked. Estimate-only requests do not execute. Stop on insufficient credits; do not recharge, buy a subscription, or repeat an uncertain paid operation.

Command Selection

Only if platform scope or evidence interpretation remains unclear, consult platform contract; it is not a preflight.

Evidence Quality

1. Check that page/post/comment/ad records match the requested lane; public group posts are not automatically comment evidence.
2. Change the public source URL or a supported query when evidence misses; keep ad creative separate from organic posts.
3. For non-ad routes, allow at most two changed follow-up passes after successful but insufficient results, within approved scope and budget; do not repeat an identical request or hide a failed/pending operation.
4. For ads, use the ad reference's evidence-based stopping conditions. Otherwise stop when sufficient, at the bound, or when another pass would not help. Report useful evidence and uncertainty; preserve raw results and source links.

Ad-library visibility is not spend or ROAS; preserve the source URL and observed dates, and distinguish comments from post text. Full machine fields belong to postplus research schema --route <route> --json; consult it only when required for processing, not before every request.

postplus research run facebook-ads-library \
  --query "example topic" \
  --wait \
  --output ./result.json

Follow the CLI's structured result and reported next action; do not infer recovery from free-text messages. Reuse explicit user approval that already covers the requested scope and maximum cost; otherwise obtain approval before confirming a quote. Never infer spending authorization from a task alone. Resume the same operation through its returned checkpoint or action; never resubmit uncertain work, repeat exhausted recovery, or switch providers to bypass failure.