Agent skill

brand-voice-enforcement

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

Stars 10,807
Forks 1,224

Install this agent skill to your Project

npx add-skill https://github.com/anthropics/knowledge-work-plugins/tree/main/partner-built/brand-voice/skills/brand-voice-enforcement

SKILL.md

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

Expand your agent's capabilities with these related and highly-rated skills.

anthropics/knowledge-work-plugins

view-pdf

Interactive PDF viewer. Use when the user wants to open, show, or view a PDF and collaborate on it visually — annotate, highlight, stamp, fill form fields, place signature/initials, or review markup together. Not for summarization or text extraction (use native Read instead).

10,807 1,224
Explore
anthropics/knowledge-work-plugins

signature-request

Prepare and route a document for e-signature — run a pre-signature checklist, configure signing order, and send for execution. Use when a contract is finalized and ready to sign, when verifying entity names, exhibits, and signature blocks before sending, or when setting up an envelope with sequential or parallel signers.

10,807 1,224
Explore
anthropics/knowledge-work-plugins

brief

Generate contextual briefings for legal work — daily summary, topic research, or incident response. Use when starting your day and need a scan of legal-relevant items across email, calendar, and contracts, when researching a specific legal question across internal sources, or when a developing situation (data breach, litigation threat, regulatory inquiry) needs rapid context.

10,807 1,224
Explore
anthropics/knowledge-work-plugins

legal-risk-assessment

Assess and classify legal risks using a severity-by-likelihood framework with escalation criteria. Use when evaluating contract risk, assessing deal exposure, classifying issues by severity, or determining whether a matter needs senior counsel or outside legal review.

10,807 1,224
Explore
anthropics/knowledge-work-plugins

triage-nda

Rapidly triage an incoming NDA and classify it as GREEN (standard approval), YELLOW (counsel review), or RED (full legal review). Use when a new NDA arrives from sales or business development, when screening for embedded non-solicits, non-competes, or missing carveouts, or when deciding whether an NDA can be signed under standard delegation.

10,807 1,224
Explore
anthropics/knowledge-work-plugins

compliance-check

Run a compliance check on a proposed action, product feature, or business initiative, surfacing applicable regulations, required approvals, and risk areas. Use when launching a feature that touches personal data, when marketing or product proposes something with regulatory implications, or when you need to know which approvals and jurisdictional requirements apply before proceeding.

10,807 1,224
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results