fb-comment
Skill1 starsChanged 16 days agoMITView on GitHub
Write comments on other people's Facebook posts and Group threads that actually add something - picked by what the post is, never "Great post!" or "🔥🔥🔥". Use when the user wants to engage with other Pages, comment in Groups, warm up a prospect, or asks "what should I comment on this".
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 17
Ask for the post text (or read it in the user's browser), who posted it, and the top comments.
- Distinctive: line 35
Specific to this post: If it could go under any post, rewrite it.
- Distinctive: line 37
Disclose: when recommending your own business in a Group.
≈ “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-comment
A good comment on the right post is free reach to an audience that already trusts that poster. A generic one is noise with the user's name on it.
Read the post first
Ask for the post text (or read it in the user's browser), who posted it, and the top comments. Then pick a type by what the post is:
| the post is... | comment type | shape |
| a lesson / tip | Add a data point | "Same here: we saw {specific number/result} when..." |
| a question | Answer it | the direct answer first, then one line of why |
| a win | Specific congrats | name the exact thing that impressed you |
| an opinion | Respectful extension or disagreement | "Agree on X. Where I'd push back is Y, because..." |
| a struggle | Experience, not advice | "Had the same in 2024. What helped was..." |
| local news / event | Local detail | something only a local would add |
| a product / launch | Concrete question | a real buyer's question |
| a story | Your version | two lines of your own related moment |
| a Group request for recommendations | Honest recommendation | only if it's genuinely a fit; disclose if it's your business |
Rules
- 1-3 sentences. Facebook comments are read on phones.
- Specific to this post. If it could go under any post, rewrite it.
- No links unless asked. No "check out my page". No DM-me fishing.
- Disclose when recommending your own business in a Group.
- No emoji-only comments, no "Great post!", no "So true!", no AI-sounding "What a fantastic insight!".
- Better comments signal quality to Facebook's ranking: ones with an opinion, a question, or that spark replies.
Output
Two or three options of different types, each run through /fb-human, with a
one-line note on why each fits this post. The user picks and posts. Never
automate commenting; it breaks Meta's Terms and gets accounts blocked.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.