affaan-m/ecc

brand-voice

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.

View source

See it in action

Usage example

Brand voice: reusable source-backed profile template

Complete canonical VOICE PROFILE schema referenced by the accepted Skill, covering source set, rhythm, claims, banned moves and channel notes. Author, Goal, Confidence and sample-source fields intentionally remain blank. Fill them from actual authorized writing samples; this is not a captured person’s voice or a finished campaign.

Example input

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:
License

Complete original source code blocks or author-defined blank templates are preserved, including imports, comments, example names, placeholders and omitted project definitions. Multiple blocks are assembled with editorial headings/fences only. Titles and summaries state dependencies and scope. These are author usage patterns or templates, not site-executed code, observed test results, measured performance or filled private-project reports. No upstream Skill instructions, installers, model/API calls, databases, browsers, accounts, mail or source tests were executed.

MIT License

Copyright (c) 2026 Affaan Mustafa

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/affaan-m/ecc --skill brand-voice

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

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.

Related by task

from this repository

More skills

All skills
affaan-m
Community

rust-testing

Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology. Use when writing Rust tests — unit, integration, async, property-based, or coverage.

24h installs
489
GitHub stars
308.2K
Updated
Nov 20
affaan-m
Community

search-first

Research-before-coding workflow: search npm/PyPI, MCP servers, skills, and GitHub for existing tools before writing custom code, then adopt, extend, or build. Launches the researcher agent for non-trivial needs. Use when starting a feature, adding a dependency or integration, or about to write a utility that may already exist.

1h installs
5
GitHub stars
308.2K
Updated
Nov 20
affaan-m
Community

browser-qa

Run automated post-deploy UI verification with a browser automation MCP (claude-in-chrome, Playwright, or Puppeteer): console-error and Core Web Vitals smoke checks, form and auth-flow interaction tests, screenshot visual regression across three breakpoints, and axe-core accessibility audits ending in a SHIP / DO-NOT-SHIP verdict. Use when testing a deployed feature on staging or preview, before shipping frontend changes, reviewing a frontend PR, or checking responsive layout and accessibility.

1h installs
2
GitHub stars
307.9K
Updated
Nov 20
affaan-m
Community

docker-patterns

Docker and Docker Compose patterns for local development, hardened CLI installer harnesses, container security, networking, volumes, and multi-service orchestration. Use when creating or reviewing Dockerfiles and Compose services, testing installers across Linux distributions, or planning accurate native macOS and Windows validation.

1h installs
2
GitHub stars
307.9K
Updated
Nov 20