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.
Source: affaan-m/ECC → skills/brand-voice/SKILL.md
Also appears in: affaan-m/ECC/.agents/skills/brand-voice/SKILL.md, hashgraph-online/awesome-codex-plugins/plugins/Colin4k1024/tsp/skills/brand-voice/SKILL.md
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---5# Brand Voice
6
7Build 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.
8
9## When to Activate
10
11- the user wants content or outreach in a specific voice
12- writing for X, LinkedIn, email, launch posts, threads, or product updates
13- adapting a known author's tone across channels
14- the existing content lane needs a reusable style system instead of one-off mimicry
15
16## Source Priority
17
18Use the strongest real source set available, in this order:
19
201. recent original X posts and threads
212. articles, essays, memos, launch notes, or newsletters
223. real outbound emails or DMs that worked
234. product docs, changelogs, README framing, and site copy
24
25Do not use generic platform exemplars as source material.
26
27## Collection Workflow
28
291. Gather 5 to 20 representative samples when available.
302. Prefer recent material over old material unless the user says the older writing is more canonical.
313. Separate "public launch voice" from "private working voice" if the source set clearly splits.
324. If live X access is available, use `x-api` to pull recent original posts before drafting.
335. If site copy matters, include the current ECC landing page and repo/plugin framing.
34
35## What to Extract
36
37- rhythm and sentence length
38- compression vs explanation
39- capitalization norms
40- parenthetical use
41- question frequency and purpose
42- how sharply claims are made
43- how often numbers, mechanisms, or receipts show up
44- how transitions work
45- what the author never does
46
47## Output Contract
48
49Produce 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).
50
51Keep the profile structured and short enough to reuse in session context. The point is not literary criticism. The point is operational reuse.
52
53## Affaan / ECC Defaults
54
55If the user wants Affaan / ECC voice and live sources are thin, start here unless newer source material overrides it:
56
57- direct, compressed, concrete
58- specifics, mechanisms, receipts, and numbers beat adjectives
59- parentheticals are for qualification, narrowing, or over-clarification
60- capitalization is conventional unless there is a real reason to break it
61- questions are rare and should not be used as bait
62- tone can be sharp, blunt, skeptical, or dry
63- transitions should feel earned, not smoothed over
64
65## Hard Bans
66
67Delete and rewrite any of these:
68
69- fake curiosity hooks
70- "not X, just Y"
71- "no fluff"
72- forced lowercase
73- LinkedIn thought-leader cadence
74- bait questions
75- "Excited to share"
76- generic founder-journey filler
77- corny parentheticals
78
79## Persistence Rules
80
81- Reuse the latest confirmed `VOICE PROFILE` across related tasks in the same session.
82- If the user asks for a durable artifact, save the profile in the requested workspace location or memory surface.
83- Do not create repo-tracked files that store personal voice fingerprints unless the user explicitly asks for that.
84
85## Downstream Use
86
87Use this skill before or inside:
88
89- `content-engine`
90- `crosspost`
91- `lead-intelligence`
92- article or launch writing
93- cold or warm outbound across X, LinkedIn, and email
94
95If another skill already has a partial voice capture section, this skill is the canonical source of truth.
96
97---
98
99**Source:** [`affaan-m/ECC`](https://github.com/affaan-m/ECC) → `skills/brand-voice/SKILL.md`
100
101**Also appears in:** `affaan-m/ECC/.agents/skills/brand-voice/SKILL.md`, `hashgraph-online/awesome-codex-plugins/plugins/Colin4k1024/tsp/skills/brand-voice/SKILL.md`
thedixitjain