
Article Writing
- 1.6k installs
- 238k repo stars
- Updated August 5, 2026
- affaan-m/ecc
This is a copy of article-writing by affaan-m - installs and ranking accrue to the original listing.
article-writing is a Claude Code skill that turns raw notes, transcripts, or research into polished long-form articles, guides, and newsletters in a consistent brand or founder voice.
About
article-writing is a long-form content skill for developers and technical founders publishing blog posts, essays, guides, tutorials, and newsletter issues. It activates when output must exceed a paragraph and voice consistency, structure, and credibility matter. The skill transforms notes, transcripts, or research into polished drafts that match supplied examples or brand guidance instead of generic LLM tone. Developers reach for article-writing when documenting launches, explaining architecture decisions publicly, or converting internal research into SEO-friendly technical articles without sounding like auto-generated paste.
- Writes long-form content (blog posts, guides, tutorials, newsletters, launch posts) that sounds like a real person with
- Derives and consistently applies a distinctive voice from supplied examples or brand guidance
- Follows 5 core rules: lead with concrete artifacts first, explain after, tight sentences, proof over adjectives, never i
- Runs brand-voice skill first when a specific voice profile is required
- Tightens structure, pacing, and evidence in existing drafts
Article Writing by the numbers
- 1,608 all-time installs (skills.sh)
- +122 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/affaan-m/ecc --skill article-writingAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.6k |
|---|---|
| repo stars | ★ 238k |
| Security audit | 3 / 3 scanners passed |
| Last updated | August 5, 2026 |
| Repository | affaan-m/ecc ↗ |
How do you turn notes into technical blog posts?
Turn raw notes, transcripts, or research into polished long-form articles, blog posts, guides, and newsletters that match a distinctive brand or founder voice.
Who is it for?
Developers and technical founders publishing long-form content who supply voice examples or brand guidance for consistency.
Skip if: Tasks needing code generation, API design, or short Slack replies where long-form structure and voice matching add no value.
When should I use this skill?
The user wants blog posts, guides, tutorials, newsletter issues, or articles longer than a paragraph with a distinctive voice.
What you get
Polished long-form articles, blog posts, guides, tutorials, or newsletter drafts with consistent voice and structure.
- Blog posts
- Guides
- Newsletter drafts
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
1. Lead with the concrete thing: artifact, example, output, anecdote, number, screenshot, or code. 2. Explain after the example, not before. 3. Keep sentences tight unless the source voice is intentionally expansive. 4. Use proof instead of adjectives. 5. 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
1. Clarify the audience and purpose. 2. Build a hard outline with one job per section. 3. Start sections with proof, artifact, conflict, or example. 4. Expand only where the next sentence earns space. 5. 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
interface:
display_name: "Article Writing"
short_description: "Long-form content in a supplied voice"
brand_color: "#B45309"
default_prompt: "Use $article-writing to draft polished long-form content in the supplied voice."
policy:
allow_implicit_invocation: true
Related skills
FAQ
What content types does article-writing produce?
article-writing produces blog posts, essays, launch posts, guides, tutorials, and newsletter issues longer than a paragraph, shaped from notes, transcripts, or research with consistent voice.
When should a developer invoke article-writing?
Developers invoke article-writing when polished long-form content needs a distinctive founder or brand voice, especially when transforming raw notes or transcripts into structured, credible articles.
Is Article Writing safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.