Develop or document a complete brand voice and tone system covering voice attributes, tone shifts by context, vocabulary preferences, grammar rules, and copy examples. Use this skill whenever the user wants to define how a brand sounds, write a voice and tone document, audit existing copy for voice consistency, train a team or AI assistant on brand voice, or refine the personality of brand writing. Triggers on brand voice, voice and tone, tone of voice, writing voice, brand personality, copy voice, voice document, voice guidelines, how should we write, voice training, voice audit. Also triggers when the user has copy that 'feels off' and the underlying issue is voice, even if not stated explicitly. On a voice consistency check, this skill owns defining and documenting the voice system; use `editorial-qa` when a specific draft needs checking against an existing system before it publishes.
72
89%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Define how a brand sounds in writing. Document it in a way that anyone (writer, designer, founder, AI assistant) can apply it consistently.
This skill produces a standalone voice document that can either live in the brand style guide or feed into it.
content-and-copy)brand-identity)brand-style-guide, which incorporates voice)brand-ideation)Voice has four layers, stacked. Each layer constrains the one below it.
The constants. The personality traits that define how the brand sounds across every context.
Pick 3 to 5 attributes. Pair each with what it is NOT (the failure mode if overdone).
Common attribute pairings (NOT a menu - generate your own):
The "not" half is what saves writers from overshooting. "Confident" alone produces swagger. "Confident, not arrogant" tells writers where the line is.
Voice is constant. Tone adapts to context.
Map the major contexts the brand writes in. For each, document how voice expresses differently.
Common contexts:
| Context | Tone shift |
|---|---|
| Onboarding | Warmer, more enthusiastic, slightly slower pace |
| Hero / marketing | Confident, signature voice fully on |
| Product copy / UX | Direct, helpful, brief |
| Error messages | Calm, matter-of-fact, no apology theater |
| Success states | Brief celebration, redirect to next action |
| Empty states | Helpful, slightly playful, suggest action |
| 404 / not found | Self-aware, light, points the way home |
| Account deletion / cancellation | Quiet, respectful, no jokes |
| Pricing | Direct, transparent, confidence-inspiring |
| Legal / TOS | Plain language version sits next to the legal version |
| Support / help center | Patient, thorough, no condescension |
| Crisis communication | Calm, factual, accountable |
| Product announcements | Excited but not breathless |
| Email subject lines | Specific, never click-bait |
Voice stays consistent across all of these. Tone is what shifts.
The granular dial settings.
Vocabulary preferences:
Grammar and style:
Voice is taught through examples, not rules. Build a library.
For each major content type, show:
Cover the content types listed in the paired examples library of references/voice-document-template.md. The template owns that list, so there is one list to maintain rather than two that drift apart.
The floor is 15 paired examples. One pair per type in the template clears it. Past 25 the library gets harder to scan than to use, so treat 25 as the practical ceiling, not a hard cap. This is the most-used part of the voice doc in practice.
references/voice-frameworks.md has a "Choosing a framework" section that decides this. A brand starting from zero begins with archetypes there, then dimensions, then attributes, and rejoins this workflow at step 2. Everything below assumes copy exists to audit.references/voice-frameworks.md: 1 to 5 against each attribute, and anything scoring below 3 on any attribute is off-voice. Below 3 means the doc is incomplete, not that the copy needs another pass.references/voice-document-template.md.Default output is a markdown document at voice.md in the brand folder. Sections:
This doc can stand alone or feed into brand-style-guide.
references/voice-document-template.md - Fillable template.references/voice-frameworks.md - Detailed walkthrough of the Nielsen Norman 4 dimensions, Jung archetypes, and the "we are X not Y" approach.0479242
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.