Agent skill · Security

brand-voice

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 trigger

RampStack477★ · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add rampstackco/claude-skills --skill brand-voice --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 8 KB
Bundled scripts: none
Path: skills/brand-voice/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 515
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Brand Voice 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. --- ## When to use - Defining brand voice for the first time - Auditing existing copy for voice consistency - Training a team, freelancer, or AI assistant on the brand voice - Refining a voice that exists but is inconsistent across applications - Adapting voice when a brand evolves (new audience, new positioning) ## When NOT to use - Writing specific copy (use `content-and-copy`) - Brand visual identity work (use `brand-identity`) - Documenting a complete brand system (use `brand-style-guide`, which incorporates voice) - Initial brand exploration (use `brand-ideation`) --- ## Required inputs - The brand and its positioning - The audience and what they need to hear - 5 to 10 examples of existing brand writing (if any) - 3 to 5 reference brands whose voice resonates with where this brand should go - Any voice attributes already specified in the brief --- ## The framework: 4 layers Voice has four layers, stacked. Each layer

What's inside
Steps it walks through
  1. When to use
  2. When NOT to use
  3. Required inputs
  4. The framework: 4 layers
  5. Layer 1: Voice attributes
  6. Layer 2: Tone shifts
  7. Layer 3: Vocabulary and grammar
  8. Layer 4: Examples and patterns
  9. Workflow
  10. Failure patterns
  11. Output format
  12. Reference files
Ships with 2 files
  • references/voice-document-template.md
  • references/voice-frameworks.md
More from claude-skills
All skills →
About this skill
What does the brand-voice skill do?

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 trigger

How do I install it?

Run `npx skills add rampstackco/claude-skills --skill brand-voice --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From rampstackco/claude-skills, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going