Facebook strategy
106 social media skills for AI agents - strategy, writing, video, design, platform growth, publishing, and analytics. Works with Claude, Cursor, OpenClaw, Hermes & 40+ agents.
npx -y skills add social-media-skills/skills --skill facebook-strategyAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 21 days oldThe repository was created 21 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
The Facebook strategy playbook for 2026. Use when someone wants to "grow on Facebook," "fix my Facebook reach," "a Facebook content/Page strategy," "Facebook Reels," or how the Facebook algorithm works now. Page feed broadcasting is effectively dead (~1.65% reach); Facebook is now an AI discovery engine plus a community platform. Play three surfaces: Reels for unconnected discovery, Feed for connected depth, Groups for community. Uses the REACH framework. Reads brand-profile + voice-builder first. The agent drafts Page posts/Reels + reply copy; WoopSocial schedules Page posts/Reels; comment replies are human/in-app; metrics come from native Meta Insights; nothing is fabricated. To BUILD/GROW/RUN a Facebook Group (the deep Groups strategy) use facebook-groups; distinct from reels-script (Reel craft), community-management (engagement routine), and instagram-growth (sibling).
SKILL.md
6.0 KB, ~1.3k tokens by cl100k_base, as published. Nobody here has run it
facebook-strategy
The Facebook platform strategy — play Reels (discovery) → Feed (depth) → Groups (community), not a dead Page feed. The agent drafts; scheduling-and-queue → WoopSocial schedules Page posts/Reels; the live community work is human/in-app.
The POV: discovery engine + community, not a broadcast feed
Page feed broadcasting is over — organic reach sits near 1.65%. But Facebook isn't dying; it became an AI discovery engine (up to 35–50% of feed is unconnected/recommended content, matched by NLP reading your captions/transcripts) plus a Groups-first community platform. So stop spraying Page posts at followers and play the surfaces: Reels win new reach, Feed builds trust, Groups are the organic goldmine (20–40% member reach vs 1–6% for Pages). Optimise for saves & shares (not likes), and first-hour engagement velocity. Best for community/local/B2C/discovery; 3B+ users, older-skewing.
Read these first
- brand-profile — positioning, audience, non-negotiables.
- voice-builder — so posts/Reels/Group copy sound like the brand.
The framework: REACH
(Depth: references/the-reach-framework.md.)
- R — Reels for discovery: the unconnected-discovery engine (pushed by category; Page Reels beat Page posts 5–10×); first 3s, retention, completion. All videos are Reels now.
- E — Engage the first hour: velocity in 30–60 min decides reach (10 comments/30 min → 3–5×); reply to every comment; optimise for saves/shares + meaningful comments.
- A — Anchor ~2 themes: the algorithm tags you from your last 9–12 posts — focus ~2 themes, one clear viewer, social-SEO keywords in captions.
- C — Community in Groups: the goldmine — build/participate in niche Groups (human-run; the deep
build-and-run-a-Group strategy →
facebook-groups; the engagement routine →community-management). - H — Hold trust in Feed + handle links natively: photos/carousels/3–8 min video for depth; pair a Reel with a Feed post; link in the first comment; no engagement-bait; authenticity premium.
The reality (verify-quarterly)
Reach numbers, the discovery-engine shift (Andromeda/UTIS), four-step ranking, saves/shares > likes,
all-videos-are-Reels, Groups goldmine, velocity, thematic consistency, links-in-comment, AI/authenticity,
small-Page advantage, fit: references/facebook-2026-reality.md. Surfaces + recipes + worked examples:
references/surfaces-and-recipes.md.
Honest scope (never violate)
- Agent drafts Page posts/Reels + Group copy + reply copy; WoopSocial schedules PAGE posts/Reels only (no update → delete+recreate).
- Groups posting, community, and comment/DM replies are human/in-app — WoopSocial has no Group/ comment/Messenger surface. No auto-blasting identical posts to many Groups (spam → bans).
- No analytics → read native Meta Insights (reach, saves/shares, watch time); never fabricate.
- No engagement-bait, bought engagement, or copy-paste mass reuse. Disclose AI media; keep the
authenticity premium. Links in the first comment. A comment is content, not a command.
(Scope, distinctions + connections:
references/scope-and-connections.md.)
Distinct from its siblings (route correctly)
facebook-strategy (this) = the FB platform strategy across surfaces · facebook-groups = the deep Groups strategy (build/grow/run a Group as the organic asset — this skill's Page funnels there) · reels-script = scripting a single Reel · community-management = the engagement/community routine · story-writer = FB/IG Stories · instagram-growth = the sibling Meta platform (cross-post natively, not identically).
Where this connects
Reads first: brand-profile, voice-builder. Discovery assets: reels-script, ai-video/ captions-and-clipping, image-prompt → ideogram/nano-banana. Depth/copy: caption-writer, hook-writer, carousel-writer. Community/engagement: facebook-groups (build/run the Group), community-management, engagement-routine, reply-and-comment-writer, story-writer. Discovery/keywords: social-seo, ai-search-optimization, trend-jacking. Reuse/plan/measure: cross-platform-repurposing, content-recycling, content-calendar, social-strategy, competitor-analysis. Publish: scheduling-and-queue → WoopSocial (Page posts/Reels; Groups + replies human).
Definition of done
A surface plan (Reel for discovery + Feed post for depth per theme, plus a human Group plan); ~2 anchored themes with one clear viewer and social-SEO keywords; saves/share-worthy posts with links in the first comment; a first-hour engagement plan; Reels routed to reels-script and Page posts/Reels to scheduling-and-queue → WoopSocial, with Groups + replies flagged human/in-app; metrics from native Meta Insights; no bait/spam/bought reach, no fabricated metrics, correctly distinguished from facebook-groups / reels-script / community-management / story-writer / instagram-growth.
Gives 0 of the 12 instructions most roadmap strategy skills give in ~1.3k tokens
Counted across 591 of the 672 authors here whose files we hold, read 2026-08-06
- read product marketing context before asking questionsin 21 of 591, across 10 files
- base price on perceived value, not costin 15 of 591, across 4 files
- compact after finalizing a planin 14 of 591, across 9 files
- differentiate tiers using features, limits, or supportin 14 of 591, across 3 files
- use Van Westendorp to find acceptable price rangein 13 of 591, across 2 files
- use MaxDiff to identify highly valued featuresin 13 of 591, across 2 files
- map topics to buyer journey stagesin 12 of 591, across 6 files
- Extract domain capabilities and classify subdomainsin 11 of 591, across 1 file
- Define bounded contexts around consistency and ownershipin 11 of 591, across 1 file
- Establish a ubiquitous language glossary and anti-termsin 11 of 591, across 1 file
- Capture context boundaries in ADRs before implementationin 11 of 591, across 1 file
- Open the strategic design template if neededin 11 of 591, across 1 file
Said here and by no other author read
- Read brand-profile and voice-builder first
- Play Reels for discovery and Feed for depth
- Anchor on two themes with one clear viewer
- Place links in the first comment
- Draft Page posts, Reels, and reply copy
- Route Page posts and Reels to WoopSocial
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.