fb-post
Skill1 starsChanged 16 days agoMITView on GitHub
Write a Facebook post or Reel caption - the line that survives the "See more" cut on mobile, the body, the single ask, links handled properly, no engagement bait - and lint it before it goes out. Use when the user says "write a Facebook post", "caption this for Facebook", "post this on my Page", "announce X on Facebook", or has a video or photo ready and needs the text.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- tonydzi/second-brain-starter-kittheir own version, first seen Sep 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- tonydzi/second-brain-starter-kit★ 6same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 74
Local words: If the user serves a place, name it.
- Very specific: line 82
Run /fb-human on it.
- Very specific: line 83
Run post.py with the user's search terms.
≈ “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.
Files
fb-post
One tool lives here and it runs:
python3 post.py post.txt
python3 post.py post.txt --keywords "home bakery,birthday cakes"
python3 post.py caption.txt --reel # shorter length budget for video captionsIt prints the post the way a phone prints it: about the first 150 characters in a box, everything else behind See more. Desktop shows about 477. Read the box before you read anything else you wrote.
First, decide which job this post has
Job A: the media already hooked them. A Reel or a strong photo carries the hook. The text's job is context, the ask, and the words people search. Keep it short; 40-150 characters often wins.
Job B: the text is the content. A text post, a story, an opinion, a Group post. Line one is the hook and works like a Reel hook: concrete, short, cut at a cliff rather than mid-clause. This is where Facebook still rewards longer writing, if each paragraph earns the next.
Say which job you're writing.
The shape
Line 1 fits the ~150-char mobile window. Job A: context + ask.
Job B: the hook. Never a greeting, a hashtag or "We are pleased".
Body short paragraphs, one blank line between each.
The ask one. A question only you could ask, a message, a booking. One.
Hashtags 0-3, or none. They label; they do not distribute on Facebook.Links, honestly
- Link posts usually reach fewer people than native posts, because they send people off Facebook.
- Since December 2025 Meta has been testing a limit of two link posts a month for some Pages and professional-mode profiles without Meta Verified. Links in comments, affiliate links and links to Meta's own apps were exempt in that test. Check whether your Page is in it before you plan a link-heavy week.
- So by default: the post stands alone and is worth reading without clicking, and the link goes in the first comment. Write that comment separately and say so in the receipt.
Engagement bait - the one that gets posts demoted
Meta's content distribution guidelines demote posts that trade engagement:
react-bait ("like if"), vote-bait ("react ❤️ for A, 😮 for B"), share-bait
("share before it's deleted"), tag-bait ("tag a friend"), and comment-bait
("type YES"). post.py fails all five. Asking a real question about the
specific thing in the post is not bait. Asking for a reaction as a trade is.
Rules
- Original. Meta reduces reach for accounts that mostly repost others' content. Commentary on a share is the minimum; your own post is better.
- One ask.
post.pycounts them. - Emoji as punctuation, not bullets. Emoji bullet lists read as a template.
- Local words. If the user serves a place, name it. Facebook search and Groups are heavily local.
- Alt text for photos: write it. Screen readers and Facebook both read it.
The loop
- Decide Job A or B and say which.
- Draft it in the user's voice (
~/.claude/facebook/voice.md). - Run
/fb-humanon it. - Run
post.pywith the user's search terms. Fix every FAIL. Decide every WARN out loud. - Print the copy-ready block (and the first comment if there's a link), then:
POST READY
job: B - the text is the content
visible: 132 of ~150 characters before See more
ask: one, "message us BOOK"
links: none in body; first comment has the menu link
hashtags: 1
bait: none
linter: READYNothing is posted. The user pastes it.
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
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.

