agentleFS
tang-vutang-vu/social-posting-skills/.agents/skills/content-writing/SKILL.md

content-writing

Skill9 starsChanged 2 months agoMITView on GitHub

Turn the campaign content graph into genuinely platform-native drafts — voice, hooks, structure per platform culture

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 2

    Distinctive

    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. Distinctive:

    No engagement bait, no "link in bio" games, no algorithm superstition stated as fact.

    line 17
  2. Distinctive:

    Never: fake urgency, "you're doing X wrong" clickbait, bait questions.

    line 45
  3. Very specific:

    When the publish path is agent-browser, content must survive automated typing: emoji and some unicode may not type in real browsers.

    line 56

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “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

Content Writing (Campaign Layer)

You adapt the canonical content graph into platform-native drafts. The CLI gives you structural scaffolds (campaign adapt); your job is the creative pass that makes each worth reading — while keeping ONE fact layer.

Non-negotiables

  • Facts come only from the graph/source/factBase. If a number isn't there, it doesn't exist. No invented metrics, no superlatives without evidence.
  • Different tone per platform: YES. Different facts: NEVER.
  • No engagement bait, no "link in bio" games, no algorithm superstition stated as fact. Label strategy advice as heuristic when it is one.
  • Disclosures stay honest: "I built this", "Open source", "Sponsored".

Platform-native ≠ shorter

PlatformShapeVoice
Xhook → thread (1 idea/post) → CTApunchy, direct
Threadsconversational chainwarm, casual
Blueskysincere short postsearly-adopter, human
LinkedInoutcome-led narrative, bulletsprofessional, first-person
Redditstory + substance + feedback asktransparent, humble
Hacker Newsplain factual title + tryable linktechnical, zero marketing
Dev.totutorial/case study with codehelpful teacher
Product Hunttagline + features + maker storyconfident, personal
Facebookcommunity question + short bodyfriendly, plain
IndieHackersmilestone + real numberstransparent, tactical
Substackissue with a pointpersonal essay
Mediumpolished longformessayistic

Hook formulas (use honestly)

  • Specific outcome: "Verify any AI model's reasoning — v1.0 is out."
  • Story: "I spent 3 months on proof chains. Here's what I learned."
  • Useful: "How to verify model outputs with Merkle proofs (OSS)."
  • Contrarian-lite: "Most AI evals are vibes. Receipts are better." — only if you can back it.
  • Never: fake urgency, "you're doing X wrong" clickbait, bait questions.

Structure patterns

Thread (X/Threads/Bluesky): hook → one node per post → CTA last. Article (Dev.to/Medium/Substack): lede → what/how → try it → next. Milestone (IH/LinkedIn): claim → context → numbers → lessons → ask. Show HN: "Show HN: Name — what it does" + usable link + honest text.

Automation typing note

When the publish path is agent-browser, content must survive automated typing: emoji and some unicode may not type in real browsers. Keep emoji out of automated posts (or confirm typing works); manual drafts can keep them. The validator flags risks — believe it.

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.