Skip to content

sergebulaev/facebook-skills / .codex-marketplace/facebook-skills/skills/fb-post-writer

fb-post-writer

Verified

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).

FileKindSize
SKILL.mdskill md7.6 KB
references/short-post-checklist.mdmarkdown3.0 KB

references/short-post-checklist.md

View on GitHub
# Short-Post Checklist (Facebook Page)

Run every Page-post draft through this before showing the approval card.

## The under-80 sweet spot

- [ ] Did you try to land the whole point under 80 characters? That is the
      highest-engagement shape on a Page (~66% lift, reported).
- [ ] If the post is over 80 chars: is the extra length earning its place (a real
      story, a launch, a spotlight)? If not, tighten it.
- [ ] First line carries the post on its own (everything above the "See more"
      fold on mobile).

## Voice scrub

- [ ] Em dashes (`—`) at or under about one per 100 words (a short post rarely
      needs one; at most one). Replace only the excess, with a comma, colon or
      parentheses, never a period. No en dashes (`–`) between clauses, no
      double dashes (`--`).
- [ ] No cluster of 2026 AI vocab (3+ markers in one paragraph = rewrite it;
      one is fine): significant, crucial, notably, comprehensive, insights,
      robust, leverage, foster, landscape, nuanced, streamline, elevate,
      empower, fundamentally, essentially, ultimately; plus "-ing" clause
      openers and "the X-tion of" nominalisations.
- [ ] No "We are thrilled / excited / delighted to announce" opener.
- [ ] No reveal bridge ("The result?", "Here's what", "Stop X, start Y") and
      no "It's not X, it's Y".
- [ ] No sincerity announcement ("we'll be honest with you", "real talk") and
      no hedge the author did not write.
- [ ] No staccato stack ("Short. Punchy. Done.", "No X. No Y. Just Z."), no
      one-word line for drama. A short post is one line; never chop it.
- [ ] At most one natural rule-of-three with concrete items; no stacked or
      hollow triads.
- [ ] Names capitalized (Stripe, Canva, Shopify).

## Substance

- [ ] One idea only. Two ideas means two posts.
- [ ] At least one specific number or named entity where the claim allows it.
- [ ] A clear primary goal: shares, comments, or reactions. Not all three.
- [ ] Designed for a share or a comment, not just a passive Like.

## Format

- [ ] 0-2 hashtags. They barely help discovery on a Page; skip unless one is a
      genuine campaign tag.
- [ ] 0-2 emoji, and only where each earns its place. None on a serious take.
- [ ] If there is a link: framing text above it, and the user knows link posts
      reach fewer people organically than a native text/photo/video post.
- [ ] Line breaks used as beats, not decoration.

## Close

- [ ] Ends on a landing or a specific question, never "What do you think?".
- [ ] No engagement bait ("LIKE and SHARE", "comment YES").

## Char-count quick reference

| Element | Value |
|---|---|
| Engagement sweet spot | under 80 chars (~66% more engagement, reported) |
| Native post limit | 63,206 chars |
| Story-post guidance | keep under ~500 chars of real substance |
| Hashtags | 0-2 |
| Emoji | 0-2 |

Lead short. The 63,206-char ceiling is a limit, not a target. Reach for the
under-80 line first, and only write long when a story, launch, or spotlight
genuinely needs the room.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall