AGENT SKILLBY AFFAAN-M
Brand voice
AT A GLANCE
Brand voice is a brand agent skill from affaan-m. 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. It is published in the affaan-m/ecc GitHub repository (243K stars) under the MIT license. Install it with: npx skills add affaan-m/ecc --skill brand-voice
- SOURCE REPOSITORY
- affaan-m/ecc (opens GitHub in a new tab)
- REPO STARS
- SOURCE REPOSITORY
- LICENSE
- MIT
- CATEGORIES
- SKILL.MD SIZE
- 4.4 KB152 LINES
QUICK ANSWER
- WHAT IT IS01
- 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. What sets it apart is how it narrows brand and messaging into one specific workflow rather than a broad, generic prompt.
- INPUTS02
- Context for brand and messaging: your goals, audience, constraints, and any source material the skill asks for.
- OUTPUT03
- A ready-to-use result for brand and messaging: the analysis, copy, or recommendations the agent produces.
INSTALL
One command adds this skill from its source repository.
npx skills add affaan-m/ecc --skill brand-voiceREAD THE SKILL.MD BELOW BEFORE YOU RUN IT. SKILLS INSTRUCT YOUR AGENT.
SKILL.MD
The full file, as published in the source repository. Copy it, download it or open it on GitHub.
ON THIS PAGE · 12
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-apito 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 (opens in a new tab).
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.
Supporting file: references/voice-profile-schema.md#
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.
FAQ
07 QUESTIONS
01What is the Brand voice agent skill?
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. It is listed under brand in the 100xLab agent skills directory.
02How do I install Brand voice in Cursor, Claude Code, or Codex?
Run npx skills add affaan-m/ecc --skill brand-voice in the project where you want it, then ask your agent for the skill by name. The --skill flag installs only Brand voice, not every skill in the repository.
03What does the Brand voice SKILL.md cover?
The SKILL.md includes sections on When to Activate, Source Priority, Collection Workflow, What to Extract, Output Contract and Affaan / ECC Defaults. Read the full text on this page or in plain markdown at /resources/agent-skills/affaan-m-ecc--brand-voice--1oljb2i/raw.
04Which agents can use Brand voice?
Brand voice installs with the cross-agent skills installer (npx skills add), which sets it up for agents such as Claude Code, Cursor and Codex. Each agent loads the SKILL.md when you ask for the skill by name.
05What license is Brand voice under?
The affaan-m/ecc repository declares the MIT license. Read the license file in the repository before you copy or redistribute the skill.
06Is Brand voice free to use?
Reading, copying and installing Brand voice costs nothing: it is published in a public GitHub repository under the MIT license. Reuse and redistribution follow that license.
07Where is the source of Brand voice?
Brand voice comes from https://github.com/affaan-m/ecc, which has 243K GitHub stars. The SKILL.md is at https://github.com/affaan-m/ecc/blob/HEAD/skills/brand-voice/SKILL.md. The author is affaan-m.
Need an agent workflow built around your stack?
Tell us the workflow you want automated. We reply within 4 working hours (IST).
ATTRIBUTION
Brand voice was written by its original authors and is published in affaan-m/ecc (opens GitHub in a new tab) under the MIT license. All rights stay with the original authors.
100xLab did not write, maintain or endorse this skill. This page lists it for discovery. Repo stars belong to the source repository, not to the skill. Review any skill before you install it.