
Facebook Research
Collect and summarize public Facebook page, group, and post data via PostPlus for grounded competitive or audience research.
Overview
Facebook Research is an agent skill most often used in Launch (also Idea and Grow) that collects public Facebook page, group, and post content through PostPlus for metrics-backed summaries.
Install
npx skills add https://github.com/postplusai/postplus-skills --skill facebook-researchWhat is this skill?
- Routes public Facebook URLs through PostPlus keys: facebook-profile-posts, facebook-group-posts, facebook-post-by-url
- Enforces public-only scope—stops and redirects when login-only or private audience data is required
- Default workflow: confirm scope, compile a brief, run collection, preserve collection-report.json while pending
- Shares postplus-shared rulebook and user-guidance with other PostPlus platform-research skills
- Supports page, group, single-post, and small discovery query targets
- 3 default public Facebook source keys: facebook-profile-posts, facebook-group-posts, facebook-post-by-url
Adoption & trust: 2 installs on skills.sh; 8 GitHub stars; 2/3 security scanners passed (skills.sh audits); trending (+200% hot-view momentum).
What problem does it solve?
You need credible Facebook market or competitor signal but only have ad-hoc screenshots instead of a bounded public collection workflow.
Who is it for?
Indie marketers researching public Facebook pages, groups, or posts for campaign ideas, positioning, or content patterns.
Skip if: Private audience analytics, follower/following lists, or anything requiring Facebook login— the skill explicitly stops and asks for another source of truth.
When should I use this skill?
User wants Facebook public post research, public content metrics, or source-grounded summaries via PostPlus Cloud collection.
What do I get? / Deliverables
You get a scoped public-content collection and summary grounded in PostPlus outputs, with clear stops when the task needs non-public data.
- Public-content collection brief
- collection-report.json when async collection is pending
- Source-grounded summary of public posts and metrics
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Launch distribution is the shelf because the skill supports go-to-market research on public social surfaces before or during campaigns—not building product code. Distribution fits platform-level public content collection used to inform channels, creative angles, and what competitors post publicly.
Where it fits
Sample public group posts to see which pain points recur before you commit to a niche.
Compare recent public posts from two competitor pages before choosing ad creative themes.
Ground a content calendar in recurring public post formats that already earn engagement in your category.
Re-run public post collection to see whether competitor posting cadence shifted after your launch.
How it compares
PostPlus public-collection integration, not native Meta Graph API analytics or ads reporting inside your repo.
Common Questions / FAQ
Who is facebook-research for?
Solo builders and growth marketers using PostPlus skills who need public Facebook post research with hosted collection entrypoints.
When should I use facebook-research?
In Launch for channel and competitor post research; in Idea for audience discovery from public groups; in Grow when summarizing public engagement patterns—only when public content is sufficient.
Is facebook-research safe to install?
Review the Security Audits panel on this Prism page; collections call PostPlus cloud services and handle public URLs—confirm credentials and data handling in your PostPlus setup.
SKILL.md
READMESKILL.md - Facebook Research
# Facebook Research Use this skill for public Facebook page, group, or post research through the PostPlus hosted public-content collection surface. Apply shared rulebook and user-guidance rules from `postplus-shared`. ## Before Collection Boundary Confirm the task can be answered from public Facebook page, group, or post content. If the goal requires follower, following, private audience, login-only, or exhaustive audience data, stop and ask for a different source of truth. ## Collection Route Default public Facebook targets: - public page/profile URL -> recent public posts, - public group URL -> recent public posts, - direct public post URL -> one post, - broad query -> small discovered public post set, then public content collection. Use the installed entrypoints: The entrypoint maps public Facebook URLs onto released source keys: - `facebook-profile-posts` - `facebook-group-posts` - `facebook-post-by-url` ## Default Workflow 1. Confirm Facebook public source scope. 2. Compile a small page, group, post, or discovery brief. 4. If the result is pending, preserve the emitted `collection-report.json`. until `pending` is `0`. 6. Normalize or summarize public post facts without treating them as private audience exports. While collection is pending, tell the user the public collection is running from a saved checkpoint and continue independent brief or source-review work. ## Output Return source-grounded summaries, public post metrics when present, stable URLs or ids, and clear notes about what the public collection cannot prove. ## Failure Modes - Stop if the request includes non-Facebook platforms. - Stop if no Facebook public URL or query can be used. - Stop on hosted capability, auth, DNS, proxy, network, or malformed-output hard errors. - Do not request private user data, login-only surfaces, or hidden audience exports. ## Handoff Facebook summaries can feed `benchmark-to-brief`, campaign research, or broader cross-platform synthesis. Publishing belongs in `social-media-publisher`. ## Public Command Boundary - Choose the smallest matching command or workflow from the user input and run it directly. - Readiness diagnostics: `postplus doctor --skill facebook-research`. - If an owned CLI or script command fails, report the exact error and stop. Do not bypass the failure with metadata-only answers, readiness probing, local payload rewrites, fallback providers, or unpublished tools. - Use `postplus research schema --json` only when constructing or repairing an unknown request shape. - Public content collection: `postplus research capability --request <hosted-capability-request.json> --output <collection-result.json>`. - Use `public-content-collection` with `sourceKey` `facebook-profile-posts`, `facebook-group-posts`, or `facebook-post-by-url`. - Keep the first pass bounded; expand only after inspecting the first result. - If the CLI returns a quote-confirmation challenge, run `postplus quote confirm --json --challenge-file <challenge.json>` and retry with the returned token.