agentleFS
m-binimranm-binimran/creator-pack/skills/facebook-post/SKILL.md

facebook-post

Skill3 starsChanged 5 months agoMITView on GitHub

Write Facebook-native content - feed posts, longer-form storytelling, and Group posts - tuned for FB's audience and reach behavior. Use when posting to a Facebook Page or Group.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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. Very specific:

    No engagement bait ("share to win") - Meta demotes it (brand-safety-guard).

    line 22

≈ “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-post

Facebook rewards conversation and longer storytelling more than Instagram does. Write for it natively.

Process

  1. Pick the format: short punchy post, longer story/text post (FB tolerates length), link post, or a Group post (community tone).
  2. Hook in line one (FB also truncates). Then tell the story / make the point; FB audiences read more.
  3. Drive conversation: a genuine question that invites replies (not bait). Replies > likes for reach.
  4. Links: native context first; put the link with a reason to click. Avoid bare link-dumps.
  5. Groups: match the community's rules and tone; provide value before promotion.

Output

  • The post copy (hook + body + conversation prompt), and a note on Page vs. Group placement.

Guardrails

  • No engagement bait ("share to win") - Meta demotes it (brand-safety-guard); ask real questions instead.
  • Disclose sponsored content (#ad + Paid partnership); sourced claims; human voice.

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.