voice-matching-wizard

A guided tool for studying writing samples and turning their recurring patterns into a reusable voice profile. The result is a voice skill file that other skills can use.

In plain words
What is it for?
Use it with representative samples, such as several newsletters or blog posts, to create a custom writing-voice skill.
Why use it?
It reduces the need to describe a writing style manually and helps keep generated writing consistent with the selected samples.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/cdeistopened/skill-stack/voice-matching-wizard
Any agent
npx skills add cdeistopened/skill-stack --skill voice-matching-wizard
Clone the repo
git clone --depth 1 https://github.com/cdeistopened/skill-stack

Made for: Claude Code, Codex.

Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,764 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00039 $0.02764
Opus 5 $0.00019 $0.01382
Sonnet 5 $0.00008 $0.00553
Haiku 4.5 $0.00004 $0.00276

Measured 2d ago against content hash 9366dbdf3361, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

voice-matching-wizard scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/voice-matching-wizard/SKILL.md · 393 lines

How it starts

The opening of the file, as written. The whole thing — 393 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Voice Matching Wizard

Create a voice skill that captures the patterns, rhythms, and sensibilities of any writing style.

What This Does

Voice matching is the art of identifying what makes writing recognizable. Not just the obvious markers—vocabulary, sentence length—but the deeper patterns: how ideas unfold, where the writer pauses, what they leave unsaid.

This wizard walks you through the process of:

  1. Gathering representative samples
  2. Extracting patterns across multiple dimensions
  3. Synthesizing a usable voice profile
  4. Generating a working skill file

The output is a voice-[name].skill.md you can use alongside other skills (like anti-ai-writing) for consistent, authentic content.


Before You Begin

What makes a good sample:

  • At least 500 words
  • Writing you're proud of (or writing you want to emulate)
  • Representative of the voice you want to capture
  • From the same medium (all newsletters, all blog posts, etc.)

What to avoid:

  • Heavily edited committee writing
  • Content written under constraints
  • Mixed formats (tweets + longform together)
  • Very old work that doesn't reflect current voice

How many samples:

  • 2-3 samples: Basic patterns
  • 4-5 samples: Good coverage
  • 10+: Comprehensive capture

Three Paths Through This Wizard

Path A: "I have samples of my own writing"

You want to codify your existing voice so AI can match it consistently. → Skip to Phase 1: Gather Your Samples

Path B: "I want to write like [someone I admire]"

You want to emulate an author, publication, or brand voice. → If the writer is well-known (major author, publication), you may be able to use their name directly in prompts. For custom or lesser-known voices, you'll still need samples. → Proceed to Phase 1: Gather Your Samples

Path C: "I'm not sure what my voice is yet"

You want to discover and develop your voice through this process. → Start with Phase 0: Voice Discovery (below)


Phase 0: Voice Discovery (Optional)

Read the full file on GitHub · 393 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 393 lines · 39 tokens per session scan A 9366dbdf3361

Subscribe to this mod's changes

voice-matching-wizard is a skill published in the GitHub repository cdeistopened/skill-stack (27 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 2,764 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens