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
- peterbamuhigire/chwezi-dev-enginetheir own version, first seen Nov 15, 2026
- peterbamuhigire/business-plan-skillstheir own version, first seen Nov 15, 2026
- its-ash/skillstheir own version, first seen Nov 1, 2026
- xiaoshuai1024/skillstheir own version, first seen Oct 13, 2026
- yan5236/skillstheir own version, first seen Jun 21, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- peterbamuhigire/chwezi-dev-engine★ 31same name
- peterbamuhigire/business-plan-skills★ 4same name
- xiaoshuai1024/skills★ 1same name
- yan5236/skills★ 1same name
- its-ash/skills★ 0same 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.
In this repository29 other files it gives its agents.
- content-writingSkill
- image-generationSkill
- post-blueskySkill
- post-devtoSkill
- post-facebookSkill
- post-hackernewsSkill
- post-indiehackersSkill
- post-linkedinSkill
- post-mediumSkill
- post-producthuntSkill
- post-redditSkill
- post-substackSkill
- post-threadsSkill
- post-xSkill
- social-campaignSkill
- image-generationSkill
- post-blueskySkill
- post-devtoSkill
- post-facebookSkill
- post-hackernewsSkill
- post-indiehackersSkill
- post-linkedinSkill
- post-mediumSkill
- post-producthuntSkill
- post-redditSkill
- post-substackSkill
- post-threadsSkill
- post-xSkill
- social-campaignSkill
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
- Distinctive: line 17
No engagement bait, no "link in bio" games, no algorithm superstition stated as fact.
- Distinctive: line 45
Never: fake urgency, "you're doing X wrong" clickbait, bait questions.
- Very specific: line 56
When the publish path is agent-browser, content must survive automated typing: emoji and some unicode may not type in real browsers.
“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.
Files
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
| Platform | Shape | Voice |
| X | hook → thread (1 idea/post) → CTA | punchy, direct |
| Threads | conversational chain | warm, casual |
| Bluesky | sincere short posts | early-adopter, human |
| outcome-led narrative, bullets | professional, first-person | |
| story + substance + feedback ask | transparent, humble | |
| Hacker News | plain factual title + tryable link | technical, zero marketing |
| Dev.to | tutorial/case study with code | helpful teacher |
| Product Hunt | tagline + features + maker story | confident, personal |
| community question + short body | friendly, plain | |
| IndieHackers | milestone + real numbers | transparent, tactical |
| Substack | issue with a point | personal essay |
| Medium | polished longform | essayistic |
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.
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.

