Article Writing

This one writes blog posts, tutorials, and long-form content that actually sounds like a person instead of committee-approved marketing paste. It enforces concrete examples before explanation, bans the usual AI slop phrases like "rapidly evolving landscape," and pushes you to lead with proof instead of adjectives. If you feed it voice samples, it'll match tone and structure. If not, it defaults to a tight operator voice. The banned patterns list alone makes it worth using. Built for anyone who needs to ship polished writing that doesn't read like it came from a template, especially when you're turning messy notes or transcripts into something publishable.

skills.sh installs: 6.3K
GitHub stars: 300.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/ecc --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.