# Article Writer Voice

> Shape the tone and formatting when writing or polishing prose — blog posts, tutorials, guides, release notes, READMEs, newsletter issues, project docs. Trigger on "write a post", "draft an article", or any prose longer than a paragraph where voice consistency matters.

- Skill: `cyberuni/article-writer-voice` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add cyberuni/article-writer-voice`
- Raw SKILL.md: https://api.skillmd.com/api/skills/cyberuni/article-writer-voice/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: cyberuni (https://skillmd.com/u/cyberuni)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/cyberuni/article-writer-voice

---


# Article Writer Voice

- **Second person, active voice.** "You update your imports", not "imports
  should be updated".
- **A stance carries its trade-off.** When you recommend or prefer, say what it
  costs and what makes it worth paying.
- **Every technical claim traces** to the repo, the user, or a cited source.
- **No hype.** Not "blazingly fast", "game-changer", "revolutionary". Earn the
  claim with evidence or drop it.
- **No filler.** Cut "so voila", "a boat load of", "basically", "just". If a
  word earns nothing, delete it.
- **Emphasis by italics, never caps or emoji.** Bold marks vocabulary, not
  emphasis. A single emoji at a personal sign-off is the one exception; never
  in docs.

Pick one, from what you are writing:

**Personal** — blog posts, opinion pieces, newsletter issues. Conversational,
peer-to-peer, a senior engineer talking to other engineers. Warm, opinionated,
honest about trade-offs.

**Docs** — project documentation, READMEs, reference. Declarative: state the
thing, don't narrate the approach to it. Sentence length follows the thought —
keep the subordination that carries a cause or a condition. Tables over
paragraphs. Bold the key term, then define it. No throat-clearing.