Source profileQuality 71/100

affaan-m/ECC/skills/brand-voice/SKILL.md

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. Use when the user wants voice consistency without generic AI writing tropes.

Source repository stars
234,327
Declared platforms
0
Static risk flags
1
Last source update
2026-07-27
Source checked
2026-07-28
DecisionCompatibilityInstallWorkflowPermissionsEvidenceSource

Decision brief

What it does—and where it fits

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.

Best for

  • Use when the user wants voice consistency without generic AI writing tropes.

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/affaan-m/ECC --skill "skills/brand-voice"
Safe inspection promptEditorial

Inspect the Agent Skill "brand-voice" from https://github.com/affaan-m/ECC/blob/4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38/skills/brand-voice/SKILL.md at commit 4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    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…

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

    When to Activate

    the user wants content or outreach in a specific voice

    the user wants content or outreach in a specific voicewriting for X, LinkedIn, email, launch posts, threads, or product updatesadapting a known author's tone across channels
  3. 03

    Source Priority

    Use the strongest real source set available, in this order:

    recent original X posts and threadsarticles, essays, memos, launch notes, or newslettersreal outbound emails or DMs that worked
  4. 04

    What to Extract

    rhythm and sentence length

    rhythm and sentence lengthcompression vs explanationcapitalization norms

Permission review

Static risk signals and limitations

Writes files

medium · line 79

The documentation asks the agent to create, modify, or delete local files.

Do not create repo-tracked files that store personal voice fingerprints unless the user explicitly asks for that.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score71/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars234,327SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
affaan-m/ECC
Skill path
skills/brand-voice/SKILL.md
Commit
4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38
License
MIT
Collected
2026-07-28
Default branch
main
View the original SKILL.md

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.

Alternatives

Compare before choosing

Computed 9438,313

wshobson/agents

brand-landingpage

Brand-first landing page designer — runs a brand-identity interview (colors, typography, shape language), then generates and iterates on a polished landing page via Stitch with deployment-ready HTML. Use when the user asks to create, design, or build a landing page, homepage, or marketing page and has no established visual direction. Skip when they have a design mockup, need a dashboard or app UI, are working at component level, building a multi-page app, or restyling with known design tokens —

2026-07-220 platforms
Computed 9142,015

coreyhaines31/marketingskills

sales-enablement

When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps.' Use this for any document or asset that helps a sales team close deals. Fo

2026-07-270 platforms
Computed 8327

MoizIbnYousaf/marketing-cli

brand-voice

Define or extract a consistent brand voice that other skills can use. Three modes: Extract (analyze existing content), Build (interview-based), Auto-Scrape (from URL). Use when copy sounds generic, when starting any new project, when voice feels inconsistent across channels, when onboarding a new brand, or when any skill needs voice-profile.md but it doesn't exist yet. This is always the first skill to run for a new project. Make sure to use this skill whenever the user mentions tone of voice, b

2026-07-280 platforms
Computed 7682,073

nexu-io/open-design

web-prototype

General-purpose desktop web prototype. Single self-contained HTML file built by copying the seed `assets/template.html` and pasting section layouts from `references/layouts.md`. Default for any landing / marketing / docs / SaaS page when no more specific skill matches.

2026-07-280 platforms