← Back to list
🛠️
voice-dossier-builder ✓ Security reviewed
Use when the user asks to "codify how our founder sounds", "build a founder voice dossier", or "s…
🛠️ Developer Tools By aaron-he-zhu Version v1.0.0 Updated 2026-09-03
7.3Overall rating

Installation

🤖 Install via AI

Copy the prompt below and send it to your AI assistant (e.g. Claude Code) — it will follow the instructions and install automatically.

Install the "voice-dossier-builder" skill by following the instructions at https://skill123.me/install/voice-dossier-builder.
⌨️ Command line install

Run in your terminal — downloads and installs to ~/.claude/skills/.

curl -fsSL https://skill123.me/install/voice-dossier-builder.sh | bash
📦 Download ZIP

Download the zip and extract it into your skills directory (e.g. ~/.claude/skills/), then restart your session.

⬇ Download v1.0.0 · 5 KB

About this skill

Overview

Use when the user asks to "codify how our founder sounds", "build a founder voice dossier", or "set our content pillars"; runs an 80%-extraction interview over the user''s OWN posts, emails, and decks (never competitor scraping, never an invented persona) and produces the versioned voice record — a per-platform register map (incl. 小红书/微信公众号), banned phrases, per-context disclosure lines (the ECHO C2 upstream), a few-shot bank built exclusively from own posts, and 3-5 content pillars with Estimated %-allocations — submitted via memory/events/channels.ndjson for channel-registry to store as voice-dossier.md, the record every Craft-phase skill reads first. Not for the brand-level voice canon — use brand-language-codifier; not for audience/persona research — use audience-mapper. 声音档案/品牌语气/创始人语气/内容支柱/披露声明

Source

  • Repo: https://github.com/aaron-he-zhu/aaron-marketing-skills
  • Path: social/explore/voice-dossier-builder

Evaluation

AI-evaluated 2026-09-03: Solid 80/20 extraction methodology with per-platform register maps, few-shot bank from own posts only, banned phrases, and versioned records. Codifying brand voice is a real need but the skill depends on the registry pipeline and corpus thresholds; own-material-only sourcing and untrusted-input handling are well done.

Score breakdown

Quality
8.0
Usability
6.0
Security
8.0
Popularity
7.0