fb-story
Skill1 starsChanged 16 days agoMITView on GitHub
Plan the daily Facebook Story sequence - frames, which sticker does which job, and the Messenger reply that starts a conversation. Use when the user asks for Facebook Stories, "what should I post on my story", a story sequence for a launch or event, or wants stories that drive messages.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 32
If the account cross-posts Instagram stories to Facebook, check stickers: not every sticker carries over.
≈ “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-story
Stories are for the people who already follow you. They're 24-hour, low production, and the best way to start private conversations, because a reply to a story lands in Messenger.
The daily shape (3-7 frames)
1 OPEN what's happening today, in one line and one real image/video
2-4 BODY behind the scenes, process, a customer moment, a tip
5 INTERACT one sticker: poll, question, or a direct "reply with X"
6 ASK the one action: message us, see the post, bookRules of thumb:
- One frame, one idea, readable in ~2 seconds. 6-10 words of text max.
- Real over polished. Phone video and natural light outperform designed graphics here.
- Text inside the safe zone: away from the top ~250px and bottom ~340px of 1080x1920, where the name and reply bar sit.
- If the account cross-posts Instagram stories to Facebook, check stickers: not every sticker carries over. Plan the Facebook version explicitly.
Which sticker does which job
| sticker / tool | job |
| Poll | low-effort first interaction; teaches people to tap |
| Question | collects objections and FAQ for future posts |
| Link | sends traffic; use sparingly, one per day |
| "Reply with WORD" (text) | starts a Messenger conversation, the real goal |
| Music / location | context; location helps local discovery |
The Messenger funnel
A story reply opens a conversation the user can answer. Plan the reply:
- Story frame: "Reply MENU and I'll send this week's prices."
- The reply they send back, written now in the user's voice (short, human,
no link-dump in the first message). Use
/fb-dm. - A follow-up question that moves toward the action.
Automated replies are only allowed through Meta's own tools (Business Suite automations) or approved partners, and only after the person messages first.
Output
A frame-by-frame table: frame, visual, on-screen text, sticker, and the
prepared Messenger reply. Run text through /fb-human. Nothing is posted.
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.