content-writer
Skill0 starsChanged 45 days agoMITView on GitHub
Create content in the user's voice — LinkedIn posts, emails, blog posts, proposals, or ad copy. Use when user says "write a post about X", "draft an email to X", "create content about X", or "write copy for X".
13 other projects use a version of this.
Adopted by
Most recently taken up by
- kashaziz/claude-skillstheir own version, first seen Nov 16, 2026
- nowork-studio/notfair-plugintheir own version, first seen Nov 11, 2026
- thescottking/b2b-pmm-skillstheir own version, first seen Oct 25, 2026
- UXLana/design-skills-packtheir own version, first seen Oct 25, 2026
- thiennq/skillstheir own version, first seen Oct 13, 2026
- chrispangg/deepagentsdktheir own version, first seen Oct 9, 2026
Used with
Projects with it also use content-planner, google-ads-audit and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
bradautomatesSkillcontent-planner
Orchestrate comprehensive content research across X, Instagram, YouTube, and TikTok platforms. Runs all research skills in parallel via subagents, then aggregates findings into actionable content plans and platform-specific intelligence playbooks.
Also in 3 projects that use this
itallstartedwithaideaSkillgoogle-ads-audit
Structured Google Ads account audit across 7 dimensions. Activate when the user asks to "audit my account", "check for problems", "find issues", "review my campaigns", or requests a comprehensive account health assessment. Delivers findings with severity ratings and prioritized action items.
Also in 3 projects that use this
indranilbanerjeeSkillkeyword-research
Research keywords via the connected data source: intent, gaps. Grouping → keyword-cluster. \"what keywords should we target\"
Also in 3 projects that use this
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- nowork-studio/toprank★ 4.2ksame name
- nowork-studio/notfair-plugin★ 4.2ksame name
- EvovexAI/EvoFlow★ 612same name
- chrispangg/deepagentsdk★ 128same name
- sociilabs/claude-content-writer★ 50same name
- ariadoss/superskills★ 12same name
- UXLana/design-skills-pack★ 8same name
- Xipher-Labs/walter-os★ 8same name
- rami-maalouf/skills★ 2same name
- thiennq/skills★ 1same name
3 more not listed
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 repository24 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- analystSkill
- build-appSkill
- build-websiteSkill
- business-setupSkill
- content-pipelineSkill
- email-assistantSkill
- email-digestSkill
- ksuite-setupSkill
- meeting-prepSkill
- memorySkill
- odooSkill
- plugin-builderSkill
- qfieldcloudSkill
- qgisSkill
- quarto-slidesSkill
- research-leadSkill
- researchSkill
- r-sessionSkill
- schedulerSkill
- scrum-masterSkill
- skill-creatorSkill
- task-managerSkill
- weekly-reviewSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 13 edited versions we read keep these.
5
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 10
Create content that sounds like the user, not like AI.
- Very specific: line 19
If context/my-voice.md is a placeholder, tell the user to run the business-setup wizard first.
- Distinctive: line 36
Use line breaks for readability
- Distinctive: line 77
Never write without reading the voice guide first
- Distinctive: line 78
Never present first drafts as final — always do the voice check
- Distinctive: line 79
If the user doesn't like the output, ask what specifically doesn't sound like them and update the voice guide
“Common” is measured: kept by at least 6 in 10 of the 13 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 Writer
Create content that sounds like the user, not like AI.
Before Writing Anything
Mandatory reads:
context/my-voice.md— How the user communicatescontext/my-business.md— Business context for relevanceconfig/preferences.yaml— Platform preference, post length
If context/my-voice.md is a placeholder, tell the user to run the business-setup wizard first.
Process
- Understand intent — What type of content? What's the goal? Who's the audience?
- Read context files — Voice guide and business context (mandatory)
- Draft — Write content matching the user's voice
- Voice check — Review against voice guide. Does this sound like them or like AI?
- Refine — Fix any generic AI patterns (see anti-patterns below)
- Present — Show the content ready to use
Content Types
LinkedIn Posts
- Short: ~300 characters (quick thought)
- Medium: ~600 characters (insight + example)
- Long: ~1200 characters (story + lesson + CTA)
- Use line breaks for readability
- Hook in the first line
- End with engagement prompt or CTA
Emails
- Subject line + body
- Match user's email tone (usually different from social tone)
- Professional but not stiff (unless that's their style)
Blog Posts
- Structured with headers
- User's voice throughout
- Practical, not theoretical (unless requested)
Proposals
- Professional, persuasive
- Reference business context for credibility
- Clear pricing/scope sections
AI Anti-Patterns (Never Use)
- "In today's fast-paced world..."
- "Let's dive in..."
- "Here's the thing..."
- "Game-changer"
- "Leverage", "synergy", "ecosystem" (unless user actually uses these)
- Starting every sentence with "I"
- Generic motivational conclusions
- Overusing em-dashes and semicolons
Input Sources
Content can be created from:
- A topic ("write about lead generation")
- A transcript ("turn this video into a post")
- Notes ("here are my thoughts, clean them up")
- A brief ("LinkedIn post, targeting CTOs, about AI automation")
- An existing piece ("rewrite this in my voice")
Rules
- Never write without reading the voice guide first
- Never present first drafts as final — always do the voice check
- If the user doesn't like the output, ask what specifically doesn't sound like them and update the voice guide
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.

