article-writing
Verifiedby affaan-m · Updated Apr 16, 2026
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
See It In Action
I'll start by exploring the project files to understand what content is available.
Got it. I have the full picture — release notes, five beta interviews, the brief, and the voice guide. Let me write this now.
I have all the source material loaded. Let me write the blog post now.
Blog post written to blog-post.md. Here's what I did:
Structure: Opens with Priya's 45-min-to-4-min story, then walks through the four big features (trace replay, snapshot diff, collaborative sharing, auto-instrumentation) with real beta quotes backing each one.
What's in there:
- All five beta users quoted, attributed, used to support specific features
- Marcus's "beta was rough" feedback owned directly, not hidden
- Tomás's breaking change pain point acknowledged with a pointer to the updated migration guide
- Getting-started code snippet appears twice (in-context and at the end)
- Dana's MTTR numbers (2 hours to 35 minutes) cited as team-tracked data, not our claim
- "What's Still Missing" section covering trace-to-code mapping, link expiry, Koa/Hono gaps
- No banned phrases, no invented metrics, no fluff
~1,500 words — within the 1,200–1,800 range.
Take a look and let me know if anything needs adjusting — tone, structure, which quotes to keep or cut.
SKILL.md
Article Writing
Write long-form content that sounds like an actual person with a point of view, not an LLM smoothing itself into paste.
When to Activate
- drafting blog posts, essays, launch posts, guides, tutorials, or newsletter issues
- turning notes, transcripts, or research into polished articles
- matching an existing founder, operator, or brand voice from examples
- tightening structure, pacing, and evidence in already-written long-form copy
Core Rules
- Lead with the concrete thing: artifact, example, output, anecdote, number, screenshot, or code.
- Explain after the example, not before.
- Keep sentences tight unless the source voice is intentionally expansive.
- Use proof instead of adjectives.
- Never invent facts, credibility, or customer evidence.
Voice Handling
If the user wants a specific voice, run brand-voice first and reuse its VOICE PROFILE.
Do not duplicate a second style-analysis pass here unless the user explicitly asks for one.
If no voice references are given, default to a sharp operator voice: concrete, unsentimental, useful.
Banned Patterns
Delete and rewrite any of these:
- "In today's rapidly evolving landscape"
- "game-changer", "cutting-edge", "revolutionary"
- "here's why this matters" as a standalone bridge
- fake vulnerability arcs
- a closing question added only to juice engagement
- biography padding that does not move the argument
- generic AI throat-clearing that delays the point
Writing Process
- Clarify the audience and purpose.
- Build a hard outline with one job per section.
- Start sections with proof, artifact, conflict, or example.
- Expand only where the next sentence earns space.
- Cut anything that sounds templated, overexplained, or self-congratulatory.
Structure Guidance
Technical Guides
- open with what the reader gets
- use code, commands, screenshots, or concrete output in major sections
- end with actionable takeaways, not a soft recap
Essays / Opinion
- start with tension, contradiction, or a specific observation
- keep one argument thread per section
- make opinions answer to evidence
Newsletters
- keep the first screen doing real work
- do not front-load diary filler
- use section labels only when they improve scanability
Quality Gate
Before delivering:
- factual claims are backed by provided sources
- generic AI transitions are gone
- the voice matches the supplied examples or the agreed
VOICE PROFILE - every section adds something new
- formatting matches the intended medium
FAQ
What does article-writing do?
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
When should I use article-writing?
Use it when you need a repeatable workflow that produces text report.
What does article-writing output?
In the evaluated run it produced text report.
How do I install or invoke article-writing?
npx skills add https://github.com/affaan-m/everything-claude-code --skill article-writing
Which agents does article-writing support?
Claude Code
What tools, channels, or permissions does article-writing need?
It uses no extra tools; channels commonly include text; permissions include no explicit permission scopes.
Is article-writing safe to install?
Static analysis marked this skill as low risk; review side effects and permissions before enabling it.
How is article-writing different from an MCP or plugin?
A skill packages instructions and workflow conventions; tools, MCP servers, and plugins are dependencies the skill may call during execution.
Does article-writing outperform not using a skill?
About article-writing
When to use article-writing
You need a polished blog post, guide, essay, or newsletter from notes or rough material. You want long-form content to match a specific brand or personal voice. You need structural editing to make an existing draft clearer, sharper, and more evidence-driven.
When article-writing is not the right choice
You only need a short reply, caption, or one-paragraph summary. You need factual research or source gathering beyond the materials already provided.
What it produces
Produces text report.
Install
npx skills add https://github.com/affaan-m/everything-claude-code --skill article-writingInvoke: Ask Claude Code to use article-writing for the task.