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.
Two Lanes
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.
Route
First Question
Ask only when the answer changes the route, source, privacy boundary, sample size, or output shape.
Do not ask the user for internal route identifiers, schemas, implementation choices, retries, credentials, hidden filters, or internal routing.
Run Discipline
- Pick one reference and one lane.
- Run the smallest real collection that can answer the decision.
- Parallelize independent sources when they do not depend on each other.
- If execution succeeds but evidence is empty, sparse, noisy, or off-topic, apply the quality rules below before accepting or exhausting the evidence.
- Produce JSON as the source of truth and a compact HTML evidence artifact when item-level evidence was collected.
- 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> --helpwhen 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.
-
Keep the first pass bounded; expand only after inspecting the first result. Stop on hard errors. Do not silently swap sources or invent missing data.
-
If the CLI returns a quote-confirmation challenge, reuse existing explicit user approval only when it covers the challenge scope and maximum cost; otherwise obtain approval before running
postplus quote confirm --json --challenge-file <challenge.json>and retry with the returned token.
Command Selection
Only if platform scope or evidence interpretation remains unclear, consult platform contract [blocked]; it is not a preflight.
Evidence Quality
- Check that page/post/comment/ad records match the requested lane; public group posts are not automatically comment evidence.
- Change the public source URL or a supported query when evidence misses; keep ad creative separate from organic posts.
- 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.
- 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.
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.
<!-- END GENERATED EXECUTION EXAMPLE -->