Develop a consistent writing voice and adjust tone to the context without sounding generic or robotic. Use when writing needs personality, a brand voice, or a register matched to the situation.
Scanned 9/5/2026
Install to Claude Code
npx -y skills add Amey-Thakur/AI-SKILLS --skill voice-and-tone --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Voice And Tone?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/amey-thakur-voice-and-tone)More formats (shields.io, HTML) on the badges page.
---
name: voice-and-tone
description: Develop a consistent writing voice and adjust tone to the context without sounding generic or robotic. Use when writing needs personality, a brand voice, or a register matched to the situation.
---
# Voice and tone
Voice is who you sound like consistently; tone is how you adjust that
voice for the moment (warm for a welcome, serious for an incident). Most
writing fails not by being wrong but by being generic: nobody in
particular, saying nothing memorable. Voice is the cure.
## Method
1. **Distinguish voice from tone.** Voice is stable (your or the brand's
personality across everything); tone flexes by context. A brand can be
consistently plain-spoken and confident (voice) while being celebratory
in a launch and sober in an outage note (tone). Get the voice fixed,
flex the tone.
2. **Define voice with concrete traits and their opposites.** "Direct, not
blunt; warm, not saccharine; expert, not academic." Traits alone are
vague; the "not" clarifies the line. A few traits, applied
consistently, beat a long adjective list nobody can act on (see
design-systems' token thinking, for words).
3. **Write like a specific person talks.** Read a draft aloud: does it
sound like a human you would want to hear from, or like a press release
generator? Contractions, real word choices, and the occasional short
punchy sentence signal a person. Corporate throat-clearing ("We are
pleased to announce") signals nobody.
4. **Match tone to the reader's emotional state.** A user hitting an error
wants calm reassurance, not jokes; someone celebrating wants you to
share it. Read the moment and meet it. Tone-deaf writing (breezy during
a crisis, cold during a welcome) breaks trust faster than any typo (see
empty-and-error-states, ux-writing).
5. **Cut the tics that flatten voice.** Hedge words ("kind of", "just",
"I think"), buzzword filler, and over-formality drain personality. So
does trying too hard (forced slang, exclamation points, manufactured
enthusiasm). Confidence and restraint read as voice; both extremes read
as insecurity.
6. **Keep it consistent, especially across a team or product.** One voice
across a product, a doc set, or a brand needs a short written guide and
shared examples (this sounds like us; this does not), so many writers
land in the same place (see style-guides).
## Boundaries
- Voice serves the content and audience; a strong voice in the wrong place
(personality in a legal notice, jokes in an API reference) is a
misjudgment. Some genres want near-invisible voice (see
technical-writing).
- Authenticity beats performance: a voice manufactured to seem edgy or
quirky reads as trying too hard. The best voice is a real one,
refined.
- Clarity is not negotiable for voice; if a stylistic choice obscures
meaning, meaning wins (see clear-writing).
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!