Agent skill
writing-voice
Voice and tone rules for all written content. Use when writing prose that should sound human and be suitable for reading aloud.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/writing-voice
SKILL.md
Writing Voice
Core principle: Write for the ear, not just the eyes. Prose should be suitable to read out loud.
The Test
Read it out loud. If it:
- Sounds like a press release → rewrite
- Sounds like a corporate memo → rewrite
- Sounds stilted or unnatural → rewrite
- Sounds like you explaining to a colleague → ship it
AI Dead Giveaways
Patterns that scream "AI wrote this":
- Bold formatting everywhere: Never bold section headers in body content
- Bullet list everything: Convert to flowing paragraphs when possible
- Marketing words: "game-changing", "revolutionary", "unleash", "empower"
- Structured sections: "Key Features:", "Benefits:", "Why This Matters:"
- Vague superlatives: "incredibly powerful", "seamlessly integrates"
- Dramatic hyperbole: "feels like an eternity", "pain point", "excruciating" — use facts instead
- AI adjectives: "perfectly", "effortlessly", "beautifully", "elegantly"
- Space-hyphen-space: "The code works - the tests pass"
- Overusing fragments: "Every. Single. Time." (once is emphasis, twice is a pattern)
- Staccato buildup: Setup. Fragment. Fragment. Fragment. Punchline. This "dramatic reveal" pattern feels manufactured. Combine into one flowing sentence with em dashes or semicolons instead.
- Forced specificity: Random numbers that don't add meaning
Punctuation
Never use " - " (space-hyphen-space) or " — " (space-em-dash-space). Prefer simpler punctuation:
| Prefer | When |
|---|---|
| Period (.) | Default choice. Two sentences are often clearer than one. |
| Colon (:) | Introducing explanation: "Here's the thing: it doesn't work" |
| Semicolon (;) | Related independent clauses: "The code works; the tests pass" |
| Em dash (—) | Sparingly, for interruption or emphasis: "It's fast—really fast" |
Em dashes are fine but easy to overuse. When in doubt, use a period.
Voice Matching
When the user provides example text or tone guidance, match it:
- If they're terse, be terse
- If they give 5 sentences, don't write 5 paragraphs
- If they use direct statements, don't add narrative fluff
- Match their energy, not a template
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?