Voice capture
Skill bg-szy/TOP-SKILLS/skills/claude-code-toolkit/voice-capture
This skill should be used when extracting voice profiles from sample text, creating voice documentation, or matching a specific writing style. It applies when users provide sample text and want to capture the voice for future use.From its SKILL.md
npx -y skills add bg-szy/TOP-SKILLS --skill voice-captureAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
6.6 KB, ~1.5k tokens by cl100k_base, as published. Nobody here has run it
Voice Capture Skill
Extract and encode writing voice from sample text into reusable voice profiles. This skill transforms examples of writing you like into documented patterns that can guide future writing.
When to Use This Skill
This skill applies when:
- A user provides sample text and asks "write like this"
- Creating a voice profile from existing content
- Documenting a brand voice for consistency
- Capturing an author's style for future reference
- Analyzing differences between two writing styles
Core Philosophy
Voice isn't just word choice. It's sentence rhythm, paragraph structure, emotional register, and a thousand small decisions that create a distinctive sound.
This skill captures those decisions systematically so they can be applied to new content.
Voice Profile Structure
A complete voice profile has three layers. See voice-profile-template.yaml for the full template.
Layer 1: Immutable Traits
Core characteristics that define the voice:
traits:
- direct # vs. indirect, circumspect
- conversational # vs. formal, academic
- technically-informed # level of assumed expertise
register: informal # formal / semiformal / informal
prohibited:
- "synergy"
- passive voice in openings
- exclamation marks (except in quotes)
Layer 2: Channel Guidance
How the voice adapts by medium:
channels:
blog:
length: "1000-2000 words"
personality: "full"
storytelling: "encouraged"
newsletter:
length: "300-500 words"
personality: "high - direct address okay"
storytelling: "personal anecdotes"
social:
length: "280 chars or thread"
personality: "punchy, hooks required"
storytelling: "minimal - punchlines only"
documentation:
length: "as needed"
personality: "minimal"
storytelling: "none - clarity first"
Layer 3: Example Library
Exemplars that demonstrate the voice:
exemplars:
- path: "samples/great-opening.md"
why: "Concrete example first, theory second"
demonstrates: ["hook", "pacing"]
- path: "samples/transition.md"
why: "Invisible transition technique"
demonstrates: ["flow", "structure"]
- path: "samples/closing.md"
why: "Strong CTA without being salesy"
demonstrates: ["conclusion", "call-to-action"]
Extraction Process
Step 1: Collect Samples
Minimum: 3 samples (ideally 5-10) Total words: At least 2,000 words Variety: Different topics, same author/brand
Step 2: Analyze Dimensions
Reference analysis-dimensions.md for the full framework.
Vocabulary Analysis
- Complexity: Simple ↔ Complex
- Formality: Casual ↔ Formal
- Jargon: Technical ↔ Accessible
- Signature words: Frequently used phrases
Sentence Analysis
- Length: Average words per sentence
- Variety: Standard deviation of sentence length
- Structure: Simple vs. compound vs. complex ratio
- Fragments: Used for emphasis? How often?
Paragraph Analysis
- Length: Average sentences per paragraph
- Opening patterns: How do paragraphs typically start?
- Closing patterns: How do paragraphs typically end?
Rhythm Analysis
- Pacing: Quick (short sentences) vs. measured (longer)
- Punctuation style: Dashes, semicolons, parentheses
- White space: Dense vs. airy paragraphs
Emotional Analysis
- Tone: Optimistic, skeptical, neutral, passionate
- Distance: Intimate (I, you) vs. distant (one, they)
- Stakes: High urgency vs. calm reflection
Step 3: Document Patterns
For each dimension, document:
- The observed pattern
- A concrete example
- A counter-example (what this voice avoids)
Step 4: Create Profile
Use extraction-templates.md to structure your findings.
Output: .claude/voice-profiles/[name].yaml
Using Voice Profiles
In Writing Commands
# In /writing:draft
style:
voice_profile: "kieran-blog"
# OR
voice_profile: ".claude/voice-profiles/client-name.yaml"
For Voice Guardian
The voice-guardian agent uses profiles to:
- Score voice consistency (0-100)
- Identify drift points
- Suggest specific fixes
Target score: 85+
For New Writers
When onboarding writers to match an existing voice:
- Share the voice profile
- Share the exemplars
- Run voice-guardian on their drafts
Quick Extraction Workflow
For rapid voice capture (when you need a profile fast):
## Quick Profile: [Name]
**Based on**: [X] samples totaling [Y] words
### Core Traits
- [Trait 1]
- [Trait 2]
- [Trait 3]
### Sentence Patterns
Average length: [X] words
Common patterns:
- [Pattern 1]
- [Pattern 2]
### Vocabulary Markers
**Signature words**: [list]
**Avoided words**: [list]
### Tone
[Brief description]
### Quick Examples
Good: "[example that nails the voice]"
Bad: "[example that would violate it]"
Common Extraction Challenges
Challenge: Too Few Samples
Problem: Can't identify patterns from 1-2 samples. Solution: Ask for more content or analyze published work from the same source.
Challenge: Inconsistent Source
Problem: The sample voice varies significantly. Solution: Either document the variation (multiple profiles) or focus on the most recent/best examples.
Challenge: Style vs. Voice
Problem: Confusing topic-specific style with core voice. Solution: Analyze samples on different topics. What stays constant? That's the voice.
Challenge: Unconscious Patterns
Problem: Author doesn't know what makes their voice distinctive. Solution: Compare to other writers. What's different? That's often the key.
Quality Checklist
A voice profile is complete when:
- All three layers are populated
- At least 3 exemplars are documented
- Prohibited patterns are explicit
- Channel variations are noted
- A test passage can be evaluated against it
- Someone unfamiliar with the voice could use it
References
- extraction-templates.md - Templates for structured extraction
- analysis-dimensions.md - All dimensions to analyze
- example-profiles.md - Sample voice profiles for reference
- voice-profile-template.yaml - The YAML template
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most docs writing skills give in ~1.5k tokens
Counted across 1,637 of the 3,044 authors here whose files we hold, read 2026-08-07
- Announce the skill at startin 54 of 1637, across 26 files
- Convert legacy doc files before editingin 45 of 1637, across 7 files
- Predict questions readers might askin 42 of 1637, across 4 files
- Generate clarifying questions for initial contextin 42 of 1637, across 3 files
- Create document scaffold with placeholder textin 42 of 1637, across 3 files
- Brainstorm content options for each sectionin 42 of 1637, across 3 files
- Test the document with a fresh context-less instancein 42 of 1637, across 3 files
- Include exact file paths in every taskin 42 of 1637, across 15 files
- Ask interview questions one at a timein 42 of 1637, across 27 files
- Apply surgical edits during refinementin 41 of 1637, across 2 files
- Offer structured workflow or freeformin 40 of 1637, across 1 file
- Ask for document meta-contextin 40 of 1637, across 2 files
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.