SkillHub

Skills affaan-m ecc

brand-voice

Use it when:
You want content or outreach for X, LinkedIn, email or launches to sound like a specific person, not generic AI copy.
It does:
Gathers 5-20 real samples, recent X posts first, and pulls out rhythm, density, capitalization, parentheticals, question use and claim style.
You get:
A structured VOICE PROFILE block, with preferred and banned moves and notes per channel, that other writing skills reuse.
Bans:
Fake curiosity hooks, "not X, just Y", "Excited to share", bait questions, thought-leader cadence and forced lowercase.
Keeps:
The profile in the session; it saves it only where you ask, and never in your repo unless you say so.

TL;DR

ECC's voice skill builds a profile once and reuses it, instead of guessing at style for every draft. It ranks source material: original X posts and threads first, then articles, essays and newsletters, outbound emails or DMs that worked, and last docs, changelogs and site copy, never generic platform examples. From 5 to 20 recent samples it notes sentence rhythm, how dense or explanatory the writing is, capitalization, parentheticals, how often questions appear, how sharply claims are made, how often numbers and mechanisms show up, transitions, and what the author never does, keeping a public launch voice apart from a private working voice when the samples split. The result follows a fixed VOICE PROFILE schema: author, goal, confidence, sources, those traits, preferred and banned moves, call-to-action rules and notes for X, LinkedIn and email. When live X access is available it pulls recent posts through ECC's x-api skill, which isn't on SkillHub. It also has default traits for the ECC author's own voice. Other ECC skills, such as content-engine and crosspost, take the profile as their source of truth.

Summarizes the skill at d2ef268.

npx skills add https://github.com/affaan-m/ecc --skill brand-voice

skills.sh pageSource on GitHubAll skills from affaan-m/ecc

Total Downloads
5,900 on skills.sh, Nov 9, 2026
Repo stars
299,776 affaan-m/ecc
First seen
May 19, 2026 on skills.sh
Weekly Downloads
473
+61% over the 8 weeks to Nov 9
Weekly values
Week toInstalls
Sep 21294
Sep 28178
Oct 5164
Oct 12268
Oct 19451
Oct 26431
Nov 2513
Nov 9473
Category
category:writingcategory:marketing

Articles, docs, internal comms, research write-ups and prose that doesn't read as generated.

SEO, copy, conversion, social media and e-commerce.
Type
type:workflow

A multi-step process the agent follows: interview, debug, run a TDD loop, review.
Effect
effect:none

Adds no side effects of its own. It shapes how the agent thinks, writes or reviews. Guidelines and routers are always effect:none, even when the task they support edits code.
Needs
needs:none

Instructions only. Works in any agent that supports skills.
Publisher
by:community

Everyone else. Unverified vendor claims default to community.
Topics
writingcopywritinganti-slopsocial-media
Stack
stack:x-twitterstack:linkedin

SKILL.md

From affaan-m/ecc at d2ef268. Checked daily, last changed Nov 6, 2026.

Frontmatter
name: brand-voice
description: 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.
metadata:
  origin: ECC

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 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.