Generated banner for Brand Voice Enforcement
Generated logo for Brand Voice Enforcement

Brand Voice Enforcement

AnthropicOfficialCreated by Tribe AIDistributed by Anthropic

  • Skill
  • Content generator
  • Business and productivity
  • MIT
  • No issues found

From the author

This skill applies brand guidelines to content creation. It should be used when the user asks to "write an email", "draft a proposal", "create a pitch deck", "write a LinkedIn post", "draft a presentation", "write a Slack message", "draft sales content", or any content creation request where brand voice should be applied. Also triggers on "on-brand", "brand voice", "enforce voice", "apply brand guidelines", "brand-aligned content", "write in our voice", "use our brand tone", "make this sound like us", "rewrite this in our tone", or "this doesn't sound on-brand". Not for generating guidelines from scratch (use guideline-generation) or discovering brand materials (use discover-brand).
— the description by Tribe AI

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

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/anthropics/brand-voice-enforcement/download
  2. Unzip 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:

  1. 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.

  2. Local guidelines file — Check for .claude/brand-voice-guidelines.md inside 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.

  3. 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-brand to find brand materials across your platforms

    • Run /brand-voice:generate-guidelines to create guidelines from documents or transcripts

    • Paste 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 | flexible

  • always-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:

  1. Explain the conflict clearly

  2. Provide a recommendation

  3. 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 explanation

  • references/before-after-examples.md — Before/after content examples per content type showing enforcement in practice

Files

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 AreWe Are Not
Confident — we know our product and stand behind itArrogant — we never talk down to prospects or dismiss alternatives
Approachable — we make complex topics feel manageableCasual or sloppy — approachable doesn't mean unprofessional
Direct — we get to the point quickly and clearlyBlunt or aggressive — directness includes empathy
Data-driven — we support claims with evidenceDry or academic — data tells stories, not lectures
Innovative — we push boundaries and challenge status quoHype-driven — innovation is real, not buzzwords
How to Use During Enforcement

For every piece of content:

  1. Check each "We Are" attribute — does the content reflect this?

  2. Check each "We Are Not" boundary — does the content avoid crossing it?

  3. If a boundary is crossed, revise the specific passage

  4. 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.

LevelSignalsWhen
HighComplete sentences, industry terminology, structured formatProposals, RFPs, enterprise comms
MediumClear and professional but conversationalMost emails, presentations, blog posts
LowCasual language, contractions, personality shows throughSocial media, internal comms, Slack
2. Energy

How much enthusiasm, urgency, or dynamism the content conveys.

LevelSignalsWhen
HighActive verbs, short sentences, exclamation-worthy excitementProduct launches, cold outreach hooks, social media
MediumSteady pace, balanced between informative and engagingDiscovery content, follow-ups, case studies
WarmEmpathetic, supportive, understandingCustomer success, objection handling, bad news
LowMeasured, thoughtful, deliberateLegal language, policy docs, sensitive topics
3. Technical Depth

How much domain expertise or technical detail is included.

LevelSignalsWhen
HighTechnical terminology, architecture details, specsTechnical audience, implementation proposals, API docs
MediumIndustry terms explained when needed, features described clearlyMixed audience, product demos, mid-funnel content
LowOutcome-focused, benefits over features, no jargonExecutive audience, cold outreach, social media

Tone-by-Context Matrix

Combine the three dimensions for each content type:

ContextFormalityEnergyTechnical DepthKey Principle
Cold outreachMediumHighLowHook fast, earn attention
Discovery callsMediumMedium-HighMediumAsk more than tell
Demo / presentationMedium-HighHighHighShow, don't just describe
Enterprise proposalHighMediumHighROI and precision
Follow-up emailMediumMediumLow-MediumAdd new value each touch
Social mediaLow-MediumHighLowBrevity and personality
Customer successMediumWarmMediumEmpathy and competence
Internal commsLowMediumVariesAuthentic, 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

  1. Applying all voice attributes at maximum intensity — Not every attribute needs to shine in every sentence. Let 2-3 lead for the content type.

  2. 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).

  3. Rigid enforcement over natural flow — Guidelines are principles, not a checklist. Content should feel natural, not mechanically assembled.

  4. 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