content-writing
Skill31 starsChanged 19 days agoMITView on GitHub
Use when writing or reviewing blog posts, long-form articles, website copy, headlines, ledes, persuasive content, readability, or scannable editorial structure; use ux-content-strategy for interface microcopy and product states.
5 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- peterbamuhigire/business-plan-skillsedited, first seen Nov 15, 2026
- its-ash/skillstheir own version, first seen Nov 1, 2026
- xiaoshuai1024/skillstheir own version, first seen Oct 13, 2026
- tang-vu/social-posting-skillstheir own version, first seen Sep 18, 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 · 1
- peterbamuhigire/business-plan-skills★ 412% same
Wrote their own version · 4
- tang-vu/social-posting-skills★ 9same 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 repository172 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- 00-meta-initializationSkill
- chwezi-dev-engineSkill
- ai-agent-commercial-operationsSkill
- ai-agent-compliance-controlsSkill
- ai-agent-governance-and-limitsSkill
- ai-agent-multi-agent-coordinationSkill
- ai-agent-observability-evaluationSkill
- ai-agent-runtime-architectureSkill
- ai-agent-safety-and-red-teamSkill
- ai-agent-tooling-and-hitlSkill
- ai-analyticsSkill
- ai-app-architectureSkill
- ai-cost-and-meteringSkill
- ai-economic-value-engineSkill
- ai-evaluationSkill
- ai-feature-rollout-and-experimentationSkill
- ai-feature-specSkill
- ai-incident-responseSkill
- ai-llm-integrationSkill
- ai-model-gatewaySkill
- ai-observability-and-debuggingSkill
- ai-opportunity-canvasSkill
- ai-prompt-engineeringSkill
- ai-rag-patternsSkill
- ai-securitySkill
- ai-web-appsSkill
- coding-agent-optimizationSkill
- openai-agents-sdkSkill
- android-developmentSkill
- api-design-firstSkill
- distributed-systems-patternsSkill
- ecommerce-platform-audit-requirementsSkill
- graphql-patternsSkill
- microservices-architectureSkill
- system-architecture-designSkill
- validation-contractSkill
- database-design-engineeringSkill
- database-reliabilitySkill
- mysql-engineeringSkill
- postgresql-engineeringSkill
- cicd-pipelinesSkill
- cloud-architectureSkill
- deployment-release-engineeringSkill
- docker-developmentSkill
- infrastructure-as-codeSkill
- kubernetes-platformSkill
- observability-monitoringSkill
- reliability-engineeringSkill
- execution-plan-scriptsSkill
- accounting-engineSkill
- accounting-finance-controllerSkill
- electronic-fiscal-taxingSkill
- multicurrency-and-fxSkill
- avalonia-desktop-developmentSkill
- frontend-architectureSkill
- frontend-performanceSkill
- image-compressionSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 9 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
9
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 25
Default to read-only analysis and drafting.
- Distinctive: line 29
If evidence, stakeholder decisions, specialist tooling, or authoritative commercial data are unavailable, deliver a labelled draft, …
- Very specific: line 67
Use the references/ directory for deep detail after reading the core workflow below.
- Distinctive: line 75
Every word exists for the reader, not the writer.
- Distinctive: line 78
Why: should they care? What benefit do they gain?
- Distinctive: line 80
What action: should a qualified buyer take next?
- Distinctive: line 82
Write for the reader all the time.
- Distinctive: line 97
Write the headline AFTER the content: Only then do you know the full scope and best angle.
- Distinctive: line 112
ALL CAPS for entire headlines (harder to read)
- Distinctive: line 121
Use that deep dive for:
“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 Skill
Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178.
Required Inputs
| Input | Required | Use |
| Decision, audience, and deliverable | yes | Bound the business outcome |
| Source evidence, constraints, and owner | yes | Ground recommendations and accountability |
| Approved budget, customer data, or production artefacts | conditional | Support high-impact execution |
Capability and permission contract
Default to read-only analysis and drafting. Do not publish, send, price, promise, alter customer records, commit budget, or modify production artefacts without explicit authority and a named approver. Minimise confidential data, preserve provenance, and keep reversible copies.
Degraded mode
If evidence, stakeholder decisions, specialist tooling, or authoritative commercial data are unavailable, deliver a labelled draft, checklist, or decision memo. State what was not verified and do not claim approval, publication, financial accuracy, or customer acceptance.
Decision rules
| Condition | Action | Stop condition |
| Output creates a commercial, customer, or delivery commitment | Obtain named approval before release | Authority or terms are unclear |
| Evidence supports a reversible draft | Produce it with assumptions and owner | Required evidence conflicts |
| Tooling or data is incomplete | Specify validation | A final executable artefact is expected |
Domain Anti-Patterns
- Inventing customer evidence, prices, benchmarks, or approvals. Fix: cite the source or mark the gap.
- Publishing or sending a draft without authority. Fix: retain draft status and name the approver.
- Hiding assumptions inside polished prose. Fix: expose them beside each affected decision.
- Polishing presentation while the decision remains unclear. Fix: resolve audience, owner, and acceptance criteria.
- Treating unavailable tooling as passed validation. Fix: record the unassessed check.
<!-- dual-compat-start -->Use When
- Copywriting and content creation standards for website pages, blog posts, and all written copy. Covers headlines, ledes, readability, niche vocabulary, scannable formatting, and persuasive structure. Cross-cutting skill — apply whenever...
Workflow
- For premium products, websites, proposals, or sales assets, write content that proves authority, qualifies buyers, supports SEO/GEO and digital PR, explains value in business terms, and leads to a concrete next action.
Evidence Produced
| Category | Artifact | Format | Example |
| UX quality | Page copy review | Markdown doc covering headline, lede, body, and CTA per page against the content-writing standard | docs/content/page-copy-review-checkout.md |
References
- English output standard for collocation, register, precise vocabulary, idiom restraint, and anti-slop revision.
- Use the
references/directory for deep detail after reading the core workflow below. - Explore, shape, and beat writing
- Pair with
premium-software-product-executionwhen copy must support premium pricing, buyer trust, service packaging, sales follow-up, or website-as-marketing-asset requirements.
<!-- dual-compat-end -->Professional copywriting standards for website copy, blog posts, articles, and all written content. This is a cross-cutting skill — apply these principles whenever creating or editing text for any page.
The Reader-First Rule
Every word exists for the reader, not the writer. Before writing anything, answer:
- Who is the reader? What do they already know?
- What are they looking for? What problem brought them here?
- Why should they care? What benefit do they gain?
- What proof would make them believe us?
- What action should a qualified buyer take next?
Write for the reader all the time. That is what separates content that converts from content that gets ignored.
Headlines & Titles
The headline is the most important element. Five times as many people read the headline as read the body. If the headline fails, everything below it is wasted.
Headline Rules
- Promise a benefit. Headlines that promise benefits outperform those that don't.
- Give news. Readers seek new information — new products, new methods, new insights.
- Select your reader. Flag down the people you want. If writing for banana farmers, put "banana farmers" in the headline.
- Be specific. "How to Increase Banana Yield by 40%" beats "Tips for Better Farming."
- Long headlines that say something outpull short headlines that say nothing. Never sacrifice clarity for brevity.
- Write the headline AFTER the content. Only then do you know the full scope and best angle.
- Telegraph in simple language. Readers do not stop to decipher obscure headlines.
Headline Formulas That Work
- How to [achieve desired result]: "How to Store Bananas for Maximum Shelf Life"
- [Number] Ways/Reasons/Steps: "7 Steps to Higher-Quality Matooke Flour"
- Question that mirrors the reader's problem: "Is Your Banana Crop Vulnerable to Fusarium Wilt?"
- News/announcement: "New Banana Cultivar Resists Black Sigatoka Disease"
- Direct benefit: "Reduce Post-Harvest Losses by Half with These Storage Methods"
What to Avoid in Headlines
- Clever wordplay the reader won't get
- Headlines that could apply to any topic (too generic)
- ALL CAPS for entire headlines (harder to read)
- Clickbait that the content cannot deliver on
Additional Guidance
Extended guidance for content-writing was moved to references/skill-deep-dive.md to keep this entrypoint compact and fast to load.
Use that deep dive for:
The Lede (Opening)ReadabilityNiche Vocabulary (Thematic Depth)Scannable FormattingThe "So What?" TestAttribution as AuthorityUnique Value PropositionFeatures vs BenefitsStructure TemplatesKeeping Eyes MovingWriting StylesTakeaways- Additional deep-dive sections continue in the reference file.
Quality Standards
Copy must be accurate, audience-specific, readable aloud, supported by named proof, and free of claims the source material cannot substantiate.
Outputs
| Artefact | Consumer | Acceptance condition |
| Reader-ready copy or copy review | Page owner, editor, or campaign team | The headline names a credible benefit, the body supplies proof, and the CTA states the next action without inventing claims |
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.

