Brand Voice Enforcement
Rewrite generic marketing copy into on-brand emails, posts, and landing snippets using before/after examples and guideline-driven annotations.
Overview
brand-voice-enforcement is an agent skill most often used in Grow (also Launch distribution and Validate landing) that rewrites generic marketing text into on-brand, annotated before/after copy.
Install
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill brand-voice-enforcementWhat is this skill?
- Before/after pairs with explicit voice annotations (e.g. confident, data-driven)
- Transforms generic outreach into metric-led, specific claims tied to buyer context
- Instructs replacing fictional SaaS placeholders with user brand guidelines and real data
- Works across cold email, web copy, and similar short-form B2B SaaS formats
- Emphasizes concrete numbers and customer proof instead of vague product pitches
- Includes annotated before/after cold outreach example with explicit voice change labels
Adoption & trust: 1.8k installs on skills.sh; 19.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your launch and lifecycle copy sounds generic and opinion-free, so prospects ignore it even when the underlying offer is strong.
Who is it for?
B2B SaaS solo builders enforcing a defined voice on emails, ads, and site copy without hiring a full-time editor.
Skip if: Builders with no brand guidelines or approved metrics yet, regulated claims needing legal sign-off only from templates, or deep technical API documentation.
When should I use this skill?
You have draft marketing or sales copy and documented brand voice rules and need structured before/after enforcement.
What do I get? / Deliverables
Drafts emerge as confident, data-anchored messaging with clear change rationales you can paste into campaigns after swapping in real brand facts.
- On-brand rewritten copy blocks
- Annotation list of voice and data changes from generic drafts
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Brand voice enforcement compounds after you have a product story; Grow/content is the canonical shelf because it optimizes ongoing messaging, not initial competitor research. The skill outputs polished prose for lifecycle and content channels — the primary artifact is enforced copy, not a prototype or deploy config.
Where it fits
Tighten hero and social-proof lines on a waitlist page before you turn on paid traffic.
Enforce confident, metric-led cold emails before a Product Hunt or outbound sprint.
Refresh lifecycle nurture sequences so every touch sounds like the same brand, not templated AI filler.
Align onboarding and upgrade emails with annotated voice rules from your guideline doc.
How it compares
Use this enforcement workflow instead of one-shot “make it sound professional” prompts that skip structured voice dimensions and proof requirements.
Common Questions / FAQ
Who is brand-voice-enforcement for?
Indie SaaS founders and small GTM teams who already have voice guidelines and need agents to consistently apply them across short-form copy.
When should I use brand-voice-enforcement?
In Grow/content for lifecycle emails, in Launch/distribution for outbound, and in Validate/landing when tightening hero and pricing copy before you ship pages.
Is brand-voice-enforcement safe to install?
Treat output as draft marketing copy; review the Security Audits panel on this page and verify all numbers and claims against your own data before sending.
SKILL.md
READMESKILL.md - Brand Voice Enforcement
# Before/After Content Examples Concrete examples showing how brand voice enforcement transforms generic content into on-brand output. Each example shows the generic version, the enforced version, and annotations explaining what changed and why. These examples use a fictional B2B SaaS company for illustration. During enforcement, replace all specifics (data points, product names, metrics) with data from the user's actual brand guidelines and context. ## Cold Outreach Email ### Before (Generic) ``` Subject: Quick question about your sales process Hi [Name], I wanted to reach out because I think our product could be a great fit for your team. We offer an AI-powered platform that helps sales teams be more productive. Would you be open to a quick 15-minute call to learn more? Best, [Sender] ``` ### After (Brand Voice Enforced) ``` Subject: [Company] is leaving pipeline on the table Hi [Name], Your team closed $12M last quarter — impressive. But our data shows mid-market SaaS teams like yours typically lose 23% of qualified pipeline to slow follow-ups. [Product] fixes that. We help sales teams respond to buying signals in real time, not hours later. [Customer X] saw their win rate jump 18% in the first quarter. Worth 15 minutes to see if the numbers apply to [Company]? [Sender] ``` ### What Changed - **Voice: Confident** — leads with a bold claim and specific data (not "I think our product could be") - **Voice: Data-driven** — concrete numbers (23%, 18%, $12M) replace vague "more productive" - **Voice: Direct** — gets to the point immediately, no "I wanted to reach out" - **Tone: Energy HIGH** — active language, short sentences, urgency - **Tone: Formality MEDIUM** — professional but conversational - **Tone: Technical depth LOW** — outcomes and impact, not feature descriptions - **Terminology**: "buying signals" and "pipeline" (industry-specific but accessible to VP Sales) ## Follow-Up Email ### Before (Generic) ``` Hi [Name], Just following up on my previous email. I'd love to schedule a call to discuss how we can help your team. Let me know if you're available this week. Thanks, [Sender] ``` ### After (Brand Voice Enforced) ``` Hi [Name], Quick update: we just published our Q4 benchmark report on enterprise sales velocity. Three insights jumped out that are relevant to [Company]: 1. Teams using real-time signals close 31% faster than the industry average 2. The #1 pipeline killer isn't competition — it's response time 3. Mid-market wins are trending 15% larger when reps personalize within 2 hours Happy to walk through how these benchmarks compare to your team's numbers. The report is attached if you'd rather dig in yourself first. [Sender] ``` ### What Changed - **Voice: Data-driven** — new value in every touch (benchmark data), not just "following up" - **Voice: Approachable** — offers two paths (call or self-serve) without pressure - **Voice: Confident** — shares proprietary insights, positions as expert - **Tone: Energy MEDIUM** — informative, not pushy - **Tone: Formality MEDIUM** — professional but not stiff - **Key principle applied**: "Add new value each touch" — no empty follow-ups ## Enterprise Proposal Executive Summary ### Before (Generic) ``` We are pleased to submit this proposal for your consideration. Our company offers a comprehensive AI solution that can help improve your sales team's performance. We believe our platform is the best choice for organizations looking to modernize their sales operations. ``` ### After (Brand Voice Enforced) ``` [Company] processes 2,400 leads per quarter with a 12-person sales team. Current pipeline-to-close conversion sits at 18% — below the 24% benchmark for enterprise SaaS at your ARR stage. This proposal outlines how [Product] closes that gap. Our platform analyzes buying signals across your existing tech stack and surfaces the 3-5 daily actions most likely to advance each deal. Typical results: +31% win rate, -40% time to close, 2.1x pipeline per r