Brand Voice Enforcement
AnthropicOfficialCreated by Tribe AIDistributed by Anthropic
- Skill
- Content generator
- Business and productivity
- MIT
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
Brand Voice Enforcement acts as a quality control layer for content creation. It ensures that every piece of writing—from cold emails to executive proposals—aligns with your established brand personality. By utilizing a 'voice constant, tone flexes' model, the skill maintains your core identity while adapting formality, energy, and technical depth to suit specific audiences and content types. It integrates with your existing guidelines to provide consistent, on-brand messaging while offering explanations for its stylistic choices.
What it does
- Loads brand guidelines from session context or local project files.
- Applies 'We Are / We Are Not' personality attributes to ensure consistency.
- Adjusts tone dimensions (formality, energy, technical depth) based on content type.
- Validates content against approved terminology and messaging frameworks.
- Provides clear explanations for brand-aligned editorial decisions.
- Handles conflicts by recommending adaptations or providing alternative options.
When to use it
- When drafting sales emails, pitch decks, or marketing copy.
- When you need to ensure content sounds like your brand identity.
- When you want to refine existing drafts to better match your established tone.
- When you need to resolve conflicts between a specific request and brand standards.
Advantages
- Maintains a unified brand personality across all communication channels.
- Reduces the time spent manually editing content for tone and style.
- Provides data-driven and context-aware adjustments rather than generic rewriting.
- Offers transparency by explaining why specific brand choices were made.
Usage examples
- “Write a cold outreach email to a VP of Sales using our brand voice.”
- The agent generates an email that leads with a bold, data-driven claim, uses high-energy active verbs, and maintains a professional yet direct tone consistent with your brand guidelines.
- “Rewrite this LinkedIn post to be more on-brand.”
- The agent analyzes the post, identifies where it deviates from your 'We Are' attributes, and revises it to be more confident and approachable while removing prohibited terminology.
- “Does this proposal sound like us?”
- The agent reviews the proposal against your guidelines, highlights specific sections that align or conflict with your voice, and suggests edits to better reflect your brand's personality.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/anthropics/brand-voice-enforcement/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip brand-voice-enforcement.zip -d .agents/skills
Documentation by Tribe AI
Brand Voice Enforcement
Apply existing brand guidelines to all sales and marketing content generation. Load the user's brand guidelines, apply voice constants and tone flexes to the content request, validate output, and explain brand choices.
Loading Brand Guidelines
Find the user's brand guidelines using this sequence. Stop as soon as you find them:
Session context — Check if brand guidelines were generated earlier in this session (via
/brand-voice:generate-guidelines). If so, they are already in the conversation. Use them directly. Session-generated guidelines are the freshest and reflect the user's most recent intent.Local guidelines file — Check for
.claude/brand-voice-guidelines.mdinside the user's working folder. Do NOT use a relative path from the agent's current working directory — in Cowork, the agent runs from a plugin cache directory, not the user's project. Resolve the path relative to the user's working folder. If no working folder is set, skip this step.Ask the user — If none of the above found guidelines, tell the user: "I couldn't find your brand guidelines. You can:
Run
/brand-voice:discover-brandto find brand materials across your platformsRun
/brand-voice:generate-guidelinesto create guidelines from documents or transcriptsPaste guidelines directly into this chat or point me to a file"
Wait for the user to provide guidelines before proceeding.
Also read .claude/brand-voice.local.md for enforcement settings (even if guidelines came from another source):
strictness: strict | balanced | flexiblealways-explain: whether to always explain brand choices
Enforcement Workflow
1. Analyze the Content Request
Before writing, identify:
Content type: email, presentation, proposal, social post, message, etc.
Target audience: role, seniority, industry, company stage
Key messages needed: which message pillars apply
Specific requirements: length, format, tone overrides
2. Apply Voice Constants
Voice is the brand's personality — it stays constant across all content:
Apply "We Are / We Are Not" attributes from guidelines
Use brand personality consistently
Incorporate approved terminology; reject prohibited terms
Follow messaging framework and value propositions
Refer to references/voice-constant-tone-flexes.md for the "voice constant, tone flexes" model.
3. Flex Tone for Context
Tone adapts by content type and audience. Use the tone-by-context matrix from guidelines to set:
Formality: How formal or casual should this be?
Energy: How much urgency or enthusiasm?
Technical depth: How detailed or accessible?
4. Generate Content
Create content that:
Matches brand voice attributes throughout
Follows tone guidelines for this specific content type
Incorporates key messages naturally (not forced)
Uses preferred terminology
Mirrors the quality and style of guideline examples
For complex or long-form content, delegate to the content-generation agent (defined in agents/content-generation.md).
For high-stakes content, delegate to the quality-assurance agent (defined in agents/quality-assurance.md) for validation.
5. Validate and Explain
After generating content:
Briefly highlight which brand guidelines were applied
Explain key voice and tone decisions
Note any areas where guidelines were adapted for context
Offer to refine based on feedback
When always-explain is true in settings, include brand application notes with every response.
Handling Conflicts
When the user's request conflicts with brand guidelines:
Explain the conflict clearly
Provide a recommendation
Offer options: follow guidelines strictly, adapt for context, or override
Default to adapting guidelines with an explanation of the tradeoff.
Open Questions Awareness
Open questions are unresolved brand positioning decisions flagged during guideline generation, stored in the guidelines under an "Open Questions" section. When generating content, check if the brand guidelines contain open questions:
If content touches an unresolved open question, note it
Apply the agent's recommendation from the open question unless the user specifies otherwise
Suggest resolving the question if it significantly impacts the content
Reference Files
references/voice-constant-tone-flexes.md— The "voice constant, tone flexes" mental model, "We Are / We Are Not" table structure, and tone-by-context matrix explanationreferences/before-after-examples.md— Before/after content examples per content type showing enforcement in practice
Files
- ATTRIBUTION.mdAdded by AutoGineer1.1 KiB
- LICENSELicence file added by AutoGineer1.0 KiB
- SKILL.md5.3 KiB
- references/before-after-examples.md7.3 KiB
- references/voice-constant-tone-flexes.md5.7 KiB
references/voice-constant-tone-flexes.md
Voice Constant, Tone Flexes
The core mental model for brand voice enforcement: voice is constant, tone flexes by context.
The Distinction
Voice is WHO the brand is — personality, values, identity. It never changes regardless of channel, audience, or content type. Think of it as the brand's character.
Tone is HOW the brand speaks in a given moment — formality, energy, technical depth. It adapts to context the way a person adjusts their tone when speaking to a friend vs. a CEO vs. a large audience.
Voice Constants: "We Are / We Are Not"
The "We Are / We Are Not" table is the anchor of brand voice. It defines the brand's personality in paired attributes — what the brand IS and the boundary it should never cross.
Structure
The table below is an illustrative example. During enforcement, use the "We Are / We Are Not" table from the user's own brand guidelines.
| We Are | We Are Not |
|---|---|
| Confident — we know our product and stand behind it | Arrogant — we never talk down to prospects or dismiss alternatives |
| Approachable — we make complex topics feel manageable | Casual or sloppy — approachable doesn't mean unprofessional |
| Direct — we get to the point quickly and clearly | Blunt or aggressive — directness includes empathy |
| Data-driven — we support claims with evidence | Dry or academic — data tells stories, not lectures |
| Innovative — we push boundaries and challenge status quo | Hype-driven — innovation is real, not buzzwords |
How to Use During Enforcement
For every piece of content:
Check each "We Are" attribute — does the content reflect this?
Check each "We Are Not" boundary — does the content avoid crossing it?
If a boundary is crossed, revise the specific passage
If an attribute is missing, find a natural place to express it
Not every attribute needs to appear in every piece of content. Prioritize the 2-3 most relevant attributes for the content type and audience.
Tone Flexes: The Three Dimensions
Tone adjusts along three independent dimensions:
1. Formality
How formal or casual the language is.
| Level | Signals | When |
|---|---|---|
| High | Complete sentences, industry terminology, structured format | Proposals, RFPs, enterprise comms |
| Medium | Clear and professional but conversational | Most emails, presentations, blog posts |
| Low | Casual language, contractions, personality shows through | Social media, internal comms, Slack |
2. Energy
How much enthusiasm, urgency, or dynamism the content conveys.
| Level | Signals | When |
|---|---|---|
| High | Active verbs, short sentences, exclamation-worthy excitement | Product launches, cold outreach hooks, social media |
| Medium | Steady pace, balanced between informative and engaging | Discovery content, follow-ups, case studies |
| Warm | Empathetic, supportive, understanding | Customer success, objection handling, bad news |
| Low | Measured, thoughtful, deliberate | Legal language, policy docs, sensitive topics |
3. Technical Depth
How much domain expertise or technical detail is included.
| Level | Signals | When |
|---|---|---|
| High | Technical terminology, architecture details, specs | Technical audience, implementation proposals, API docs |
| Medium | Industry terms explained when needed, features described clearly | Mixed audience, product demos, mid-funnel content |
| Low | Outcome-focused, benefits over features, no jargon | Executive audience, cold outreach, social media |
Tone-by-Context Matrix
Combine the three dimensions for each content type:
| Context | Formality | Energy | Technical Depth | Key Principle |
|---|---|---|---|---|
| Cold outreach | Medium | High | Low | Hook fast, earn attention |
| Discovery calls | Medium | Medium-High | Medium | Ask more than tell |
| Demo / presentation | Medium-High | High | High | Show, don't just describe |
| Enterprise proposal | High | Medium | High | ROI and precision |
| Follow-up email | Medium | Medium | Low-Medium | Add new value each touch |
| Social media | Low-Medium | High | Low | Brevity and personality |
| Customer success | Medium | Warm | Medium | Empathy and competence |
| Internal comms | Low | Medium | Varies | Authentic, less polished |
Applying Voice + Tone Together
Example: Cold outreach email
Voice constants active:
Confident — lead with a strong value claim
Direct — get to the point in sentence one
Approachable — don't sound like a robot
Tone settings:
Formality: Medium (professional but not stiff)
Energy: High (earn attention quickly)
Technical Depth: Low (outcomes, not features)
Example: Enterprise proposal
Voice constants active:
Data-driven — every claim has supporting evidence
Confident — strong positioning without hedging
Innovative — show forward-thinking approach
Tone settings:
Formality: High (structured, complete sentences)
Energy: Medium (measured, not breathless)
Technical Depth: High (detailed implementation, specs)
Common Enforcement Mistakes
Applying all voice attributes at maximum intensity — Not every attribute needs to shine in every sentence. Let 2-3 lead for the content type.
Confusing voice with tone — If the user asks for "casual" content, adjust TONE (lower formality, higher energy). Don't change VOICE (the brand's personality stays the same).
Rigid enforcement over natural flow — Guidelines are principles, not a checklist. Content should feel natural, not mechanically assembled.
Ignoring the audience — The same voice can sound very different to a CTO vs. a VP of Sales. Tone flexes handle this.
Requirements and compatibility
Written for: Claude Code, Claude apps
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- Tribe AI
- Publisher
- Anthropic (Official)
- Distributed by
- Anthropic
- Source
- anthropics/knowledge-work-plugins · partner-built/brand-voice/skills/brand-voice-enforcement · commit e050c2e
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from partner-built/brand-voice/LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Tribe AI or Anthropic.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download brand-voice-enforcement.zip