Brand Voice
- 1.5k installs
- 238k repo stars
- Updated August 5, 2026
- affaan-m/ecc
This is a copy of brand-voice by affaan-m - installs and ranking accrue to the original listing.
brand-voice is an ECC agent skill that builds a source-derived writing style profile from real posts and docs for developers and technical teams who need consistent on-brand content across channels.
About
brand-voice is an ECC-origin skill from affaan-m/ecc that constructs a durable voice profile from real source material—posts, essays, launch notes, documentation, or site copy—then reapplies that profile across content workflows. Instead of re-deriving tone each session or defaulting to generic AI phrasing, the skill captures diction, rhythm, and framing from authenticated examples. Developers and technical founders reach for it when writing for X, LinkedIn, email, launch posts, threads, or product updates in a recognizable voice. Activation triggers include requests for voice consistency, channel-specific outreach, or adapting a known author's tone. The output is a reusable style profile engineers can attach to downstream content, outreach, and social generation tasks inside agent sessions.
- Builds durable voice profile from real source material instead of re-deriving style each time
- Follows explicit 4-tier source priority: recent X posts first, then essays, emails, and product docs
- Distinguishes public launch voice from private working voice when sources differ
- Integrates live x-api pull for newest original posts before drafting
- Prevents defaulting to generic AI writing tropes across all channels
Brand Voice by the numbers
- 1,517 all-time installs (skills.sh)
- +99 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/affaan-m/ecc --skill brand-voiceAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.5k |
|---|---|
| repo stars | ★ 238k |
| Last updated | August 5, 2026 |
| Repository | affaan-m/ecc ↗ |
How do you keep AI-generated copy on brand?
Extract a reusable, source-derived writing style profile from their own past posts, essays, and docs so every piece of content, outreach, and social copy stays on-brand
Who is it for?
Developers and technical teams publishing recurring content who want voice consistency derived from their own writing samples.
Skip if: Pure code refactoring tasks, API documentation lookup, or teams without existing source copy to analyze for style extraction.
When should I use this skill?
The user wants content or outreach in a specific voice, or asks to adapt tone across X, LinkedIn, email, or launch posts.
What you get
Source-derived brand voice profile reusable across social posts, email outreach, launch notes, and product updates.
- reusable voice profile
- channel-adapted copy drafts
By the numbers
- ECC-origin skill metadata labeled origin: ECC
Files
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.
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 PROFILEacross 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.
Voice Profile Schema
Use this exact structure when building a reusable voice profile:
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 situational
Parentheticals
- how they are used and how they are not used
Question Use
- rare, frequent, rhetorical, direct, or mostly absent
Claim Style
- how claims are framed, supported, and sharpened
Preferred Moves
- concrete moves the author does use
Banned Moves
- specific patterns the author does not use
CTA Rules
- how, when, or whether to close with asks
Channel Notes
- X:
- LinkedIn:
- Email:Guidelines:
- Keep the profile concrete and source-backed.
- Use short bullets, not essay paragraphs.
- Every banned move should be observable in the source set or explicitly requested by the user.
- If the source set conflicts, call out the split instead of averaging it into mush.
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493kHow it compares
Use brand-voice for style extraction from your own writing; pick documentation skills when you need library API references instead of messaging tone.
FAQ
What source material does brand-voice analyze?
brand-voice builds profiles from real posts, essays, launch notes, documentation, and site copy. The skill captures diction and framing from those sources instead of inventing a generic AI tone.
Which channels does brand-voice support?
brand-voice reuses extracted profiles across X, LinkedIn, email, launch posts, threads, and product updates so technical teams keep a consistent voice across growth and outreach content.