Social Media Extractor
Enter PostPlus public Instagram and Meta extraction workflows when you need ad creative, benchmark, or UGC signals but have not picked a platform-specific skill yet.
Overview
social-media-extractor is an agent skill most often used in Launch (also Validate, Grow) that routes public Instagram and Meta extraction requests to the correct PostPlus platform skill.
Install
npx skills add https://github.com/postplusai/postplus-skills --skill social-media-extractorWhat is this skill?
- Routes Instagram benchmark and creator shortlist work to Instagram skills
- Routes Facebook/Meta page, group, and post evidence to facebook-research
- Explicit stop: no guessing when user intent or source evidence is missing
- CLI/script failures must be reported exactly—no metadata-only bypass
- Non-Meta platforms are outside this release lane
Adoption & trust: 1 installs on skills.sh; 8 GitHub stars; 2/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
You want public social signals for ads or creators but have not specified Instagram versus Facebook/Meta, risking the wrong extractor or guessed results.
Who is it for?
Solo builders running PostPlus for Meta-family campaign research with an explicit brief and acceptable public-source limits.
Skip if: Scraping non-Meta platforms, tasks that belong to ideation or QA skills in the handoff list, or runs where required inputs are missing.
When should I use this skill?
User wants public Instagram or Meta content signals for ad creative, benchmark, creator shortlist, or UGC planning but has not named a platform-specific workflow.
What do I get? / Deliverables
The agent routes to the right PostPlus skill, runs owned CLIs when inputs are complete, and returns structured output or a clear blocker instead of hallucinated social data.
- Structured extraction output or hosted result
- Poll command when async
- Explicit blocker when inputs or CLI fail
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Launch/distribution is the primary shelf because the skill gathers public social evidence to plan campaigns, creatives, and creator shortlists for go-to-market. Distribution subphase covers routing benchmark and creator research into the right Instagram or facebook-research skills before spend goes live.
Where it fits
Decide whether Instagram creator shortlist or Meta page research fits your launch hypothesis before building landing creative.
Route a vague 'get competitor Reels' request into the correct Instagram benchmark skill with owned CLI output.
Refresh UGC references for lifecycle email and paid social without mixing in non-Meta platforms.
How it compares
Routing contract inside the PostPlus skill family—not a standalone scraper or generic web-research skill.
Common Questions / FAQ
Who is social-media-extractor for?
Founders and marketers using PostPlus agents who need Instagram or Meta public data for creative and benchmark work before choosing a platform-specific skill.
When should I use social-media-extractor?
Use it at launch distribution planning for ad and creator research, during validate when scoping campaign evidence, and in grow when refreshing benchmarks—only when the platform workflow is not yet named.
Is social-media-extractor safe to install?
Review the Security Audits panel on this page; respect public-data scope, stop conditions, and your platform ToS— the skill forbids bypassing failed owned commands.
SKILL.md
READMESKILL.md - Social Media Extractor
# Social Media Extractor ## Use When - The user wants public Instagram or Facebook/Meta content signals for ad creative, benchmark, creator shortlist, UGC, or campaign asset planning. - The user has not named a platform-specific workflow yet. ## Scope - Instagram benchmark or creator shortlist work routes to Instagram skills. - Facebook/Meta public page, group, or post evidence routes to `facebook-research`. - Non-Meta platforms are outside this release lane. ## Do Not Use When - The task belongs to ideation, QA, or another released skill listed in the handoff section. - Required inputs are missing and guessing would change the result. ## Required Input - Explicit user brief or JSON input matching the artifact contract. ## Stop Conditions - Stop when required user intent, source evidence, or owned input artifacts are missing and guessing would change the result. - 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. ## Handoff - Return the structured output, hosted result, poll command, or explicit blocker. ## Public Command Boundary - Choose the smallest matching command or workflow from the user input and run it directly. - 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. - This public skill is instruction-driven. Produce the artifact described by the workflow directly from the available evidence. - Do not call private provider/runtime paths or unpublished local tools. - If the CLI returns a quote-confirmation challenge, run `postplus quote confirm --json --challenge-file <challenge.json>` and retry with the returned token.