Best for
- Someone pastes in posts, articles, or tweets they admire
- "Make me sound like this person"
- "Steal this voice"
MoizIbnYousaf/marketing-cli/skills/voice-extraction/SKILL.md
Reverse-engineer any person's writing voice from their content. Paste in posts, articles, tweets, or essays and this skill launches 10 parallel Sonnet subagents to analyze every dimension of the voice, then synthesizes into a voice file. Use when someone says 'match this voice,' 'analyze this writing,' 'extract their voice,' 'make me sound like this,' 'study this person's writing,' or pastes in content they want to learn from.
Decision brief
Paste content. Get a complete voice architecture. 10 Sonnet subagents rip apart every dimension in parallel.
Compatibility matrix
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/MoizIbnYousaf/marketing-cli --skill "skills/voice-extraction"Inspect the Agent Skill "voice-extraction" from https://github.com/MoizIbnYousaf/marketing-cli/blob/f12fbcbe4929584697b309b9096c9427b0cfce8e/skills/voice-extraction/SKILL.md at commit f12fbcbe4929584697b309b9096c9427b0cfce8e. 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
CRITICAL: Use model: "sonnet" for all 10 agents. Not opus. These run in parallel and sonnet is the right tool for focused analytical work.
Once all 10 agents report back, synthesize their findings into a single voice file. The file should be structured as:
After the voice file is written:
Someone pastes in posts, articles, or tweets they admire
1. Confirm you have raw content to analyze. The user must paste or point to actual writing (posts, articles, tweets, essays). Minimum: 1 substantial post or 5+ tweets. More is better.
Permission review
The documentation asks the agent to read local files, directories, or repositories.
Offer to update `/cmo` or other skills to read this file instead of (or in addition to) the default `voice-profile.md`Evidence record
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 84/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 27 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Paste content. Get a complete voice architecture. 10 Sonnet subagents rip apart every dimension in parallel.
This is not a summary. This is a structural teardown of how someone writes, thinks, teaches, and earns trust. The output is a voice file that any other skill can read to produce content in that voice.
Confirm you have raw content to analyze. The user must paste or point to actual writing (posts, articles, tweets, essays). Minimum: 1 substantial post or 5+ tweets. More is better.
If the content is thin: "I need more material to extract a real voice. One post gives me patterns. Five posts give me a system. Can you paste more?"
If the content is rich enough: proceed immediately. Don't ask unnecessary questions. The content IS the input.
CRITICAL: Use model: "sonnet" for all 10 agents. Not opus. These run in parallel and sonnet is the right tool for focused analytical work.
Launch ALL 10 in a SINGLE message using the Agent tool. Each agent gets the full pasted content plus a specific analytical lens.
Agent 1: Sentence Structure & Rhythm Analyze sentence length patterns, paragraph openers, idea sequencing within paragraphs, transitions between sections, use of questions vs statements. Look for: short-short-long triplets, myth-pivot openers, colon embeds, imperative staccato closers. Give specific examples from the content.
Agent 2: Vocabulary & Word Choice Analyze verbs they reach for, adjectives they use, words they avoid, jargon level, how they handle technical terms, signature phrases, casual vs formal balance. Identify: blacklist words (what they never say), signature vocabulary, crossover vocabulary from other domains.
Agent 3: Teaching Methodology Analyze how they introduce ideas, use examples, structure explanations, handle complexity, guide the reader. Look for: iteration-as-pedagogy (attempt #1, #2, #3), analogy-before-abstraction, wrong-way-first patterns, complexity escalation, "develop your intuition" closes.
Agent 4: Emotional Register Map the emotional spectrum: when they show enthusiasm, when cautious, how they handle warnings, relationship to reader, confidence level, humor style. Identify: default emotional temperature, how warmth is rationed, how confidence appears, what emotions are absent.
Agent 5: Content Structure Patterns Analyze macro structure of pieces: opening patterns, section organization, how arguments build, how pieces close. Identify: the meta-pattern across all pieces, theory-to-example ratio, what goes first, what gets omitted.
Agent 6: Authority & Credibility Signals Analyze how they establish credibility without arrogance. Look for: "we tried/I tried" patterns, I/we splitting, epistemic framing, credentialing through specificity vs titles, how they credit others.
Agent 7: Tweet-Length Writing Analyze short-form specifically: sentence structure in tweets, claim posture, compression mechanism, how they tease long-form, what makes it feel like a person vs a content machine. Identify: the thesis extraction pattern, audience selection through vocabulary.
Agent 8: Use of Concrete Examples Analyze naming patterns, specificity levels, when real names vs templates, how examples serve arguments. Look for: mechanism-level vs outcome-level specificity, friction terms that signal lived experience, examples doing double duty (illustrating AND arguing).
Agent 9: Anti-Patterns (What They Don't Do) Analyze what's systematically absent: hype words, corporate speak, self-promotion patterns, talking down, clickbait, empty enthusiasm, excessive hedging, summary conclusions, rhetorical questions as transitions. Evidence of absence is as important as evidence of presence.
Agent 10: Adaptation for Target Voice Given all the above, how should this voice be adapted for the user's product/brand? What transfers directly? What needs modification? What should the user's unique voice add that the source doesn't do? Include example tweets/posts in the adapted voice.
Each agent gets:
You are analyzing the writing voice of [PERSON] to reverse-engineer their complete voice architecture. Focus ONLY on [DIMENSION].
Here is their content:
[FULL PASTED CONTENT]
Additional context: [USER'S PRODUCT/BRAND if relevant]
Output a structured analysis with specific patterns and examples from the actual content. No fluff. Be specific enough that someone could replicate this voice from your analysis alone.
Once all 10 agents report back, synthesize their findings into a single voice file. The file should be structured as:
# [Name] Voice Guide
> Built from deep analysis of [source description]. [One sentence on what this voice is for.]
## 1. Core Identity
[Who this voice is. The guiding sentence.]
## 2. Sentence Architecture
[Patterns from Agent 1, distilled into rules with examples]
## 3. Vocabulary
[Reach for / Avoid lists from Agent 2]
## 4. Emotional Register
[Temperature map from Agent 4]
## 5. Authority & Credibility
[Patterns from Agent 6]
## 6. Teaching Style
[Patterns from Agent 3]
## 7. Tweet Voice
[Short-form patterns from Agent 7]
## 8. Content Structure
[Macro patterns from Agent 5]
## 9. What We Never Do
[Anti-patterns table from Agent 9]
## 10. The [Brand] Delta
[Adaptation from Agent 10]
## 11. Example Tweets in This Voice
[3-5 examples from Agent 10's adaptation]
This skill extracts a specific person's voice (founder, competitor,
inspiration) — it does NOT overwrite the project's canonical
brand/voice-profile.md. Each extracted voice lives in its own file
so multiple subjects can coexist and be referenced independently.
brand/: save to brand/voices/[name].md
(create the brand/voices/ subdirectory if it doesn't exist)./voices/[name].md relative to the current
working directoryNever write to brand/voice-profile.md from this skill — that path is
owned by /brand-voice and represents the single canonical project
voice. Use the voices subdirectory for per-subject extractions.
After the voice file is written:
/cmo or other skills to read this file instead of (or in addition to) the default voice-profile.md| Anti-pattern | Why it fails | Instead |
|---|---|---|
| Summarizing the person's content | A summary is not a voice analysis | Analyze HOW they write, not WHAT they write about |
| Using fewer than 10 agents | Each dimension needs focused attention; combining them produces shallow analysis | Always launch all 10, always in parallel |
| Using opus for the subagents | Expensive and unnecessary; sonnet is sharp enough for focused analytical work | Always use model: "sonnet" |
| Launching agents sequentially | Wastes time; these are independent analyses | Launch all 10 in a SINGLE message |
| Skipping the adaptation agent (#10) | The raw analysis is academic without adaptation to the user's context | Agent 10 is what makes this actionable |
| Writing a generic "be authentic" voice guide | Useless; every voice guide says this | Every rule must have a specific pattern with a specific example |
| Analyzing without enough source material | Patterns need repetition to be patterns | Ask for more content if < 1 substantial post |
Alternatives
MoizIbnYousaf/marketing-cli
Backlink + distribution checklist that expands a site's KD ceiling beyond what on-page work alone can earn. Use when the user mentions 'backlinks', 'off-page SEO', 'directory submissions', 'guest posts', 'outreach targets', 'link building', 'submit to directories', 'get listed in listicles', 'Product Hunt launch backlinks', or asks 'how do I get more domain authority'. Generates a prioritized, researched target list across directories, listicles, and guest-post candidates — does NOT submit anyth
github/awesome-copilot
Use this skill when the user asks to analyze, tear down, or reverse-engineer a competitor's paid ads. Trigger for prompts like "what ads is [competitor] running", "tear down their ad strategy", "competitor ad analysis", "find ad angles we haven't tried", or "reverse-engineer their paid funnel". Do not trigger for organic/SEO competitor research or website positioning analysis.
MoizIbnYousaf/marketing-cli
Build an organic-traffic operating system for any site or app: a multi-phase, resumable engine that ships programmatic landing pages (alternatives, comparisons, use-cases, playbooks) on top of real keyword research. Use when the user says 'SEO machine', 'build organic traffic', 'rank on Google', 'we need traffic', 'alternatives pages', 'comparison pages', '/for/ pages', 'programmatic SEO', or 'build an SEO engine'. Distinct from `seo-audit` (one-off diagnostic) and `seo-content` (single-article
coreyhaines31/marketingskills
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