Article Writing

This one writes blog posts, guides, and newsletters that don't sound like they came from an LLM. It enforces a sharp structure: lead with the concrete thing first, explain after, cut the throat-clearing. It can match a specific founder or brand voice if you give it examples, or default to a tight operator style if you don't. The banned patterns list alone is worth reading. It kills "in today's rapidly evolving landscape," fake vulnerability arcs, and closing questions added just for engagement. Use it when you need long-form content that has to carry credibility and voice consistency, not just fill space.

skills.sh installs: 6.3K
GitHub stars: 229.1K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/everything-claude-code --skill article-writing --agent claude-code

Installs into .claude/skills of the current project.

Files

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.