Mmcp.market

brand-voice skill

by affaan-m·affaan-m/ECC·269k stars·MIT

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.

A100/100content scan

Is the brand-voice skill safe?

Clean: nothing in its files matched our rules. We read 3 files in the folder on 2026-09-28.

No findings.

Install the brand-voice skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description. 

git clone --depth 1 https://github.com/affaan-m/ECC.git /tmp/ECC
mkdir -p ~/.claude/skills
cp -r /tmp/ECC/.agents/skills/brand-voice ~/.claude/skills/brand-voice
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

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.

More skills from affaan-m/ECC

  • AaccessibilityWCAG 2.2 レベル AA 標準を用いてインクルーシブなデジタルプロダクトを設計・実装・監査します。Web 用のセマンティック ARIA および Web・ネイティブプラットフォーム（iOS/Android）のアクセシビリティトレイトを生成するために使用します。
  • Aagent-architecture-auditエージェントおよび LLM アプリケーション向けのフルスタック診断。12 層のエージェントスタックにおけるラッパーリグレッション、メモリ汚染、ツール規律の失敗、隠れた修復ループ、レンダリング破損を監査します。重要度順の発見事項とコードファーストの修正を生成します。エージェントアプリケーション、自律ループ、または LLM を活用した機能を構築する開発者に必須です。
  • Aagent-evalカスタムタスクでコーディングエージェント（Claude Code、Aider、Codex など）をヘッドツーヘッドで比較し、合格率、コスト、時間、一貫性のメトリクスを測定します
  • Aagent-harness-constructionAI エージェントのアクション空間、ツール定義、観測フォーマットを設計・最適化して完了率を向上させます。
  • Aagent-introspection-debuggingStructured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports. Use when an agent run fails and you need a reproducible diagnosis instead of a retry.
  • Aagent-introspection-debuggingキャプチャ、診断、封じ込め回復、内省レポートを使用した AI エージェント障害のための構造化された自己デバッグワークフロー。
  • Aagent-payment-x402タスクごとのバジェット、支出コントロール、ノンカストディアルウォレットを備えた x402 決済実行を AI エージェントに追加します。agentwallet-sdk を通じて Base をサポートし、OKX Payments / OKX エージェント決済プロトコルを通じて X Layer をサポートします。
  • Aagent-sortBuild an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.
  • Aagent-sort並行リポジトリ対応のレビューパスを使用して、スキル、コマンド、ルール、フック、エクストラを DAILY と LIBRARY のバケットに分類することで、特定のリポジトリ向けのエビデンスに基づいた ECC インストール計画を構築します。プロジェクトが完全なバンドルをロードする代わりに実際に必要なものに ECC をトリミングする必要がある場合に使用します。
  • Aagentic-engineeringOperate as an agentic engineer using eval-first execution, decomposition, and cost-aware model routing. Use when AI agents perform most implementation work and humans enforce quality and risk controls.
  • Aagentic-engineering評価ファースト実行、分解、コスト対応モデルルーティングを使用してエージェニックエンジニアとして動作します。
  • Aagentic-osClaude Code 上に永続的なマルチエージェントオペレーティングシステムを構築します。カーネルアーキテクチャ、スペシャリストエージェント、スラッシュコマンド、ファイルベースのメモリ、スケジュールされた自動化、外部データベースなしの状態管理をカバーします。

All agent skills → · MCP servers