agentleFS
sergebulaevsergebulaev/facebook-skills/skills/fb-post-writer/SKILL.md

fb-post-writer

Skill75 starsChanged 4 months agoMITView on GitHub

Draft a short punchy Facebook Page post, or a longer story post, using a 2026 Facebook hook formula (one-line opinion, tiny number, ask-the-page question, this-or-that, useful tip, story post) picked by goal (shares, comments, reactions). Favors the under-80-character engagement sweet spot, runs the humanizer pass, and publishes via Publora on approval. Use to write a Page post from notes. Not for replying to comments (use fb-engagement-drafter) or auditing a draft (use fb-humanizer).

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Pick the container: Default to a short post (aim under 80 chars).

    line 55
  2. Distinctive:

    Pick the formula: Use the goal table to shortlist, then suggest 2-3 that also fit the topic and let the user choose.

    line 59
  3. Distinctive:

    If the post includes a link, write framing text above it (Facebook builds a preview card) and warn that link posts reach fewer people …

    line 67
  4. Very specific:

    On approval: Call lib.publish(kind="post", draft_text=<approved>, target_url="https://www.facebook.com/YourPage", …

    line 79
  5. Distinctive:

    Never open with "We are thrilled / excited / delighted to announce".

    line 94
  6. Distinctive:

    Do not beg for engagement.

    line 95

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Facebook Page Post Writer

Ship a short punchy Page post, or a longer story post when the material earns it, using hook shapes that actually travel on a Facebook Page in 2026. The single highest-engagement move on a Page is the short post: posts under 80 characters get a reported ~66% engagement lift, so this skill leads short and only goes long on purpose.

When to use

  • User says "write me a Facebook Page post about X"
  • User has a topic or a rough line and wants a sharper, shorter hook
  • User wants to pick a proven Page-post shape and fill in their voice
  • User wants a quick draft that auto-publishes on approval

Formulas this skill uses

CodeFormulaPrimary goalBest for
FB1One-Line Opinionsharesa sharp, defensible take in one short line
FB2The Tiny Numbersharesone concrete number that reframes a thing
FB3Ask-the-Page Questioncommentsan easy, fun question the audience answers
FB4This-or-Thatcommentsa friendly binary choice readers pick a side on
FB5Relatable One-Linerreactionsa specific shared moment, no setup
FB6Behind-the-Scenesreactionsa real human moment inside the business
FB7Useful Tipsharesone usable tip the reader passes on
FB8Story Post with a Turnsharesa longer true story with a quotable turn
FB9Announcement with Stakessharesa launch or news, led human not corporate
FB10Community Spotlightsharesfeaturing a real customer or team member

Full skeletons in ../../references/hook-formulas.md. FB1-FB7 are short-post shapes (lead here). FB8-FB10 are longer story shapes (use on purpose).

Pick by goal first

GoalReach for
SharesFB1, FB2, FB7, FB8, FB9, FB10
CommentsFB3, FB4, FB8
ReactionsFB5, FB6

Steps

Voice profile first (all drafts). If ../../references/voice-profile.md has filled: yes, load it and match the user's voice fingerprint, hard rules, and CTA/link style throughout. If it is not filled, mention once that fb-humanizer --mode profile can learn their voice from a few posts, then proceed with the generic voice rules.

Story bank next. If ../../references/story-bank.md has filled: yes, load it and take every concrete detail (numbers, dates, named projects, positions) from there instead of asking mid-draft. Never invent a figure, a date or a client name that is not in the bank or supplied by the user in this conversation. If the bank has nothing that fits, ask the user, or say once that fb-humanizer --mode interview fills it in 20 to 40 minutes. A draft with a plausible invented number is worse than a draft with none: one is vague, the other is a retraction.

  1. Gather inputs. Topic, angle, any rough draft, target audience (B2C / B2B / local / community), and the goal (shares / comments / reactions).
  2. Pick the container. Default to a short post (aim under 80 chars). If it is one opinion, number, question, or moment, it stays short. Only escalate to a story post (FB8-FB10) if the idea is a true narrative, a real launch, or a spotlight that needs room.
  3. Pick the formula. Use the goal table to shortlist, then suggest 2-3 that also fit the topic and let the user choose.
  4. Draft the post. Fill the skeleton in the user's voice. Respect the 2026 Facebook rules:
    • Lead short. Try to land the whole point under 80 chars.
    • First line carries the post (Facebook folds longer posts behind "See more").
    • One idea per post. Line breaks as beats.
    • 0-2 hashtags, 0-2 emoji, none on a serious take.
    • If the post includes a link, write framing text above it (Facebook builds a preview card) and warn that link posts reach fewer people organically.
  5. Humanizer pass. Scrub 2026 AI vocab by paragraph density, cap em dashes (about one per 100 words, never swap one for a period), strip "We are thrilled to announce" and every corporate opener, break stacked triads and reveal bridges. Fix only a story paragraph that reads machine-flat; never manufacture variance, and never fragment a short post for punch. Add an odd-precision number with a named referent or a named entity where the claim allows it. Canonical rules: fb-humanizer V3.
  6. Optional audit. Invoke fb-humanizer --mode audit for a pass-fail check.
  7. Approval card. Show: formula used, full draft, char count (flag if it crosses the 80-char sweet spot), suggested posting window, primary goal.
  8. On approval. Call lib.publish(kind="post", draft_text=<approved>, target_url="https://www.facebook.com/YourPage", platforms=[<FACEBOOK_PLATFORM_ID>], scheduled_time=<iso_or_None>). For a deliberate long story post, pass kind="story". The wrapper handles Publora / manual / diy routing.

Hard rules

Global voice rules: see root SKILL.md Voice rules. Additional skill-specific rules:

  • Lead short. Default to under 80 chars; that is the engagement sweet spot. A long post is a deliberate choice for a story, not the fallback.
  • The first line must carry the post on its own (everything above the "See more" fold).
  • One specific number where the claim allows it. "4 minutes" beats "fast".
  • Never open with "We are thrilled / excited / delighted to announce".
  • Do not beg for engagement. Earn the share or comment with the post itself.

Anti-patterns (skill will refuse)

  • "We are thrilled to announce.." and every variant.
  • Engagement bait ("LIKE and SHARE if you agree", "comment YES", "tag 3 friends").
  • Em dashes above the cap (more than about one per 100 words), or an em dash swapped for a period.
  • "Here's what" or "Stop X, start Y" as the opener; "The result?" as a reveal.
  • Announced candor ("We'll be honest with you", "real talk") with no dated fact behind it.
  • Staccato stacks ("No X. No Y. Just Z.") and one-word lines added for drama.
  • Padding a one-line idea into five paragraphs.
  • Rule-of-three lists without specifics.
  • "leverage", "fundamentally", "game-changer", "deep dive".
  • A bare external link with no framing text.
  • 5+ hashtags stuffed at the bottom.

Resources

  • ../../references/hook-formulas.md - all 10 Facebook formula skeletons (FB1-FB7 short, FB8-FB10 story)
  • ../../references/algorithm-heuristics.md - 2026 Facebook Page ranking rules (signals, the under-80 boost, timing, limits)
  • references/short-post-checklist.md - the per-post scrub and the under-80 fit check

Optional illustration

Offer a generated image when a visual would lift reach. Draft a prompt and call lib.illustrate(prompt, kind="wide"), pulling brand handle/color from Voice & Brand Profile section 6 for a pixel-exact overlay. Show the returned url + cost, then attach on publish via media_urls=[url]. Full workflow (incl. quote-cards): ../fb-humanizer/sub-skills/illustration.md. No Pixfaro key -> it drafts the prompt for you to generate manually.

Related skills

  • fb-humanizer - aggressive AI-tell scrubber, plus --mode audit for review
  • fb-hook-extractor - reverse-engineer a hook from a Page post you admire
  • fb-content-planner - plan a week of these posts
  • fb-engagement-drafter - reply to the comments your post earns

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.