Brand Voice
Derive a reusable writing voice from real posts and docs so launch and growth content stops sounding like generic AI copy.
Overview
Brand Voice is an agent skill most often used in Grow (also Launch) that builds a source-derived writing style profile from real posts and docs for reuse across channels.
Install
npx skills add https://github.com/affaan-m/everything-claude-code --skill brand-voiceWhat is this skill?
- Source priority ladder: X posts, essays, emails, then product docs and site copy
- Collection workflow targeting 5–20 representative samples
- Separates public launch voice from private working voice when sources diverge
- Optional x-api pull for recent original posts before drafting
- Explicit ban on generic platform exemplars as faux source material
- 5–20 representative source samples in collection workflow
- 4-tier source priority order
Adoption & trust: 3.4k installs on skills.sh; 210k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
Every new draft sounds like default AI marketing because you have no portable profile of how you actually write.
Who is it for?
Indie builders with existing posts, newsletters, or docs who publish across multiple channels and hate repetitive tone drift.
Skip if: Founders with zero source writing who want the skill to invent a persona from thin air or trademarked celebrity mimicry.
When should I use this skill?
User wants voice consistency for X, LinkedIn, email, launch posts, or threads without generic AI writing tropes.
What do I get? / Deliverables
You get a durable voice spec grounded in 5–20 real samples you can attach to content, outreach, and social workflows going forward.
- Reusable voice profile document
- Channel adaptation notes
- Source sample index
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Voice systems compound in grow/content but are first needed when you start shipping outward-facing copy at scale. Content subphase is where style profiles pay off across channels—threads, email, changelogs—not one-off prompts.
Where it fits
Profile your last 15 X threads before batching a month of posts in the same cadence.
Align launch announcement copy with essays and changelogs you already shipped.
Tune landing hero and founder story to match memos you sent early testers.
Reuse outbound email tone that previously got replies in onboarding sequences.
How it compares
A reusable style system from your corpus—not a one-shot 'write like X' prompt or a full SEO keyword research skill.
Common Questions / FAQ
Who is brand-voice for?
Solo builders and small teams who ship product updates, threads, and email and need one consistent voice pulled from their own material.
When should I use brand-voice?
Before a launch post series, when adapting tone to LinkedIn vs X, or when your content skill keeps sounding generic despite good ideas.
Is brand-voice safe to install?
It may call x-api or web tools to read your public posts—review the Security Audits panel on this Prism page and limit connected accounts.
SKILL.md
READMESKILL.md - Brand Voice
# Brand Voice Build a durable voice profile from real source material, then use that profile everywhere instead of re-deriving style from scratch or defaulting to generic AI copy. ## When to Activate - the user wants content or outreach in a specific voice - writing for X, LinkedIn, email, launch posts, threads, or product updates - adapting a known author's tone across channels - the existing content lane needs a reusable style system instead of one-off mimicry ## Source Priority Use the strongest real source set available, in this order: 1. recent original X posts and threads 2. articles, essays, memos, launch notes, or newsletters 3. real outbound emails or DMs that worked 4. product docs, changelogs, README framing, and site copy Do not use generic platform exemplars as source material. ## Collection Workflow 1. Gather 5 to 20 representative samples when available. 2. Prefer recent material over old material unless the user says the older writing is more canonical. 3. Separate "public launch voice" from "private working voice" if the source set clearly splits. 4. If live X access is available, use `x-api` to pull recent original posts before drafting. 5. If site copy matters, include the current ECC landing page and repo/plugin framing. ## What to Extract - rhythm and sentence length - compression vs explanation - capitalization norms - parenthetical use - question frequency and purpose - how sharply claims are made - how often numbers, mechanisms, or receipts show up - how transitions work - what the author never does ## Output Contract Produce a reusable `VOICE PROFILE` block that downstream skills can consume directly. Use the schema in [references/voice-profile-schema.md](references/voice-profile-schema.md). Keep the profile structured and short enough to reuse in session context. The point is not literary criticism. The point is operational reuse. ## Affaan / ECC Defaults If the user wants Affaan / ECC voice and live sources are thin, start here unless newer source material overrides it: - direct, compressed, concrete - specifics, mechanisms, receipts, and numbers beat adjectives - parentheticals are for qualification, narrowing, or over-clarification - capitalization is conventional unless there is a real reason to break it - questions are rare and should not be used as bait - tone can be sharp, blunt, skeptical, or dry - transitions should feel earned, not smoothed over ## Hard Bans Delete and rewrite any of these: - fake curiosity hooks - "not X, just Y" - "no fluff" - forced lowercase - LinkedIn thought-leader cadence - bait questions - "Excited to share" - generic founder-journey filler - corny parentheticals ## Persistence Rules - Reuse the latest confirmed `VOICE PROFILE` across related tasks in the same session. - If the user asks for a durable artifact, save the profile in the requested workspace location or memory surface. - Do not create repo-tracked files that store personal voice fingerprints unless the user explicitly asks for that. ## Downstream Use Use this skill before or inside: - `content-engine` - `crosspost` - `lead-intelligence` - article or launch writing - cold or warm outbound across X, LinkedIn, and email If another skill already has a partial voice capture section, this skill is the canonical source of truth. # Voice Profile Schema Use this exact structure when building a reusable voice profile: ```text VOICE PROFILE ============= Author: Goal: Confidence: Source Set - source 1 - source 2 - source 3 Rhythm - short note on sentence length, pacing, and fragmentation Compression - how dense or explanatory the writing is Capitalization - conventional, mixed, or s