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:
- recent original X posts and threads
- articles, essays, memos, launch notes, or newsletters
- real outbound emails or DMs that worked
- product docs, changelogs, README framing, and site copy
Do not use generic platform exemplars as source material.
Collection Workflow
- Gather 5 to 20 representative samples when available.
- Prefer recent material over old material unless the user says the older writing is more canonical.
- Separate "public launch voice" from "private working voice" if the source set clearly splits.
- If live X access is available, use
x-api to pull recent original posts before drafting.
- 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.
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-enginecrosspostlead-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.
1---2name: brand-voice3description: Build a source-derived writing style profile from real posts, essays, launch notes, docs, or site copy, then reuse that profile across content, outreach, and social workflows. Use when the user wants voice consistency without generic AI writing tropes.4---56# Brand Voice78Build 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.910## When to Activate1112- the user wants content or outreach in a specific voice13- writing for X, LinkedIn, email, launch posts, threads, or product updates14- adapting a known author's tone across channels15- the existing content lane needs a reusable style system instead of one-off mimicry1617## Source Priority1819Use the strongest real source set available, in this order:20211. recent original X posts and threads222. articles, essays, memos, launch notes, or newsletters233. real outbound emails or DMs that worked244. product docs, changelogs, README framing, and site copy2526Do not use generic platform exemplars as source material.2728## Collection Workflow29301. Gather 5 to 20 representative samples when available.312. Prefer recent material over old material unless the user says the older writing is more canonical.323. Separate "public launch voice" from "private working voice" if the source set clearly splits.334. If live X access is available, use `x-api` to pull recent original posts before drafting.345. If site copy matters, include the current ECC landing page and repo/plugin framing.3536## What to Extract3738- rhythm and sentence length39- compression vs explanation40- capitalization norms41- parenthetical use42- question frequency and purpose43- how sharply claims are made44- how often numbers, mechanisms, or receipts show up45- how transitions work46- what the author never does4748## Output Contract4950Produce 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).5152Keep the profile structured and short enough to reuse in session context. The point is not literary criticism. The point is operational reuse.5354## Affaan / ECC Defaults5556If the user wants Affaan / ECC voice and live sources are thin, start here unless newer source material overrides it:5758- direct, compressed, concrete59- specifics, mechanisms, receipts, and numbers beat adjectives60- parentheticals are for qualification, narrowing, or over-clarification61- capitalization is conventional unless there is a real reason to break it62- questions are rare and should not be used as bait63- tone can be sharp, blunt, skeptical, or dry64- transitions should feel earned, not smoothed over6566## Hard Bans6768Delete and rewrite any of these:6970- fake curiosity hooks71- "not X, just Y"72- "no fluff"73- forced lowercase74- LinkedIn thought-leader cadence75- bait questions76- "Excited to share"77- generic founder-journey filler78- corny parentheticals7980## Persistence Rules8182- Reuse the latest confirmed `VOICE PROFILE` across related tasks in the same session.83- If the user asks for a durable artifact, save the profile in the requested workspace location or memory surface.84- Do not create repo-tracked files that store personal voice fingerprints unless the user explicitly asks for that.8586## Downstream Use8788Use this skill before or inside:8990- `content-engine`91- `crosspost`92- `lead-intelligence`93- article or launch writing94- cold or warm outbound across X, LinkedIn, and email9596If another skill already has a partial voice capture section, this skill is the canonical source of truth.
Anantha-236