plugins/scribe/skills/voice-extract/SKILL.md
Extracts a user's writing voice from text samples via SICO comparative analysis. Use when building a voice profile for consistent generation.
npx skillsauth add athola/claude-night-market voice-extractInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Extract a user's writing voice through SICO comparative analysis.
Rather than measuring surface metrics, this skill uses SICO Phase 1: feed the model user writing samples alongside its own default output on the same topics. The model describes what the user does differently. This produces voice descriptions that encode implicit structural patterns no metrics can capture.
Anonymize samples: Label as "Sample 1", "Sample 2", etc. Context labels cause the extractor to anchor on content rather than reading a unified voice.
Variety over volume: 10 samples across different topics beats 20 on the same subject. The extraction needs to see what stays constant when everything else changes.
Casual writing is distinctive: Reddit comments, slack messages, quick emails. Polished pieces have rough edges edited away, and those edges are where voice lives.
Pressure test for specificity: If extraction output sounds generic ("uses varied sentence lengths"), run pass 2 and force specificity. Good output reads like followable instructions, not a book report.
Use Opus for extraction: More nuanced feature descriptions, especially for registers where subtle tonal shifts matter.
voice-extract:samples-collected - Writing samples gatheredvoice-extract:samples-anonymized - Labels stripped, numberedvoice-extract:baseline-generated - Claude's default output on same topicsvoice-extract:extraction-pass-1 - Broad comparative featuresvoice-extract:extraction-pass-2 - Pressure test for specificityvoice-extract:profile-written - extraction.md createdLoad: @modules/sample-intake
# Scan for samples
PROFILE_DIR="$HOME/.claude/voice-profiles/{name}"
mkdir -p "$PROFILE_DIR/samples"
# Copy samples from user-provided directory
# Rename to Sample-01.md, Sample-02.md, etc.
Present the user with:
Paste your writing sample below (minimum 200 words).
Type END on a new line when done.
Repeat until user says "done collecting" or reaches 10+ samples.
Create manifest.json:
{
"profile_name": "{name}",
"created": "YYYY-MM-DD",
"samples": [
{
"id": "sample-01",
"original_source": "anonymized",
"word_count": 450,
"date_added": "YYYY-MM-DD"
}
],
"extraction_model": "opus",
"extraction_date": null,
"registers": ["default"]
}
For each sample's topic/context, generate Claude's default output on the same subject. This creates the comparison pair.
Prompt for baseline:
Write a short piece about [topic extracted from sample].
Use your natural default style. Do not try to match any
particular voice or style. Just write naturally about this
subject in approximately [word_count] words.
Store baselines alongside samples for comparison.
Load: @modules/sico-extraction
The core comparative prompt:
I'm going to show you pairs of text. In each pair:
- Text A is written by a specific person
- Text B is your default output on the same topic
Your task: describe what the writer of Text A does
differently from your default style. Focus on:
- Structural patterns (paragraph shapes, section architecture)
- Rhetorical moves (how they build arguments, make transitions)
- Tonal devices (hedging patterns, commitment patterns)
- Sentence-level techniques (clause structure, rhythm)
- Vocabulary tendencies (physical vs abstract language,
technical vs conversational)
- Distinctive habits (parentheticals, fragments, questions)
Do NOT describe surface metrics (average sentence length,
word count). Describe the voice in terms a writer could
follow. Be specific enough that someone could use your
description to imitate this voice.
[Pairs follow]
If the extraction output contains any of these generic phrases, reject and re-run with higher specificity demand:
Review your feature description. For each characteristic
you identified, answer:
1. Could this describe 50% of writers? If yes, be more
specific or remove it.
2. Can someone follow this as a concrete instruction?
If not, add an example from the samples.
3. Are there patterns you noticed but didn't name?
Writers often have unnamed habits. Look for:
- How they use parentheticals
- Where they commit vs hedge
- Physical language for abstract concepts
- Rhythm of building caution then dropping unhedged claims
- How they anticipate reader objections
Revise your description to be more specific and followable.
Write the extraction to ~/.claude/voice-profiles/{name}/extraction.md:
# Voice Extraction: {name}
## Feature Description
[SICO extraction output here]
## Craft Rules (Detection-Neutral)
These techniques improve writing without increasing
AI detectability:
- Concrete-first: Lead with specific, physical details
- Naming: Label patterns and dynamics explicitly
- Opening moves: Start mid-thought or with a specific moment
- Human-moment anchoring: Ground abstractions in lived experience
- Aphoristic destinations: Write sentences worth repeating alone
## Banned Phrases
[Standard AI vocabulary list + user additions]
## Notes
- Extraction model: {model}
- Extraction date: {date}
- Sample count: {n}
- Total word count: {words}
Create default register at registers/default.md from the
extraction output.
tools
Detect friction signals; graduate patterns into rules. Use for session retrospectives.
testing
Use when you need a diff-derived test plan for an MR — reads the diff, groups changes by area, runs targeted verifications, and proves revert-tests are genuine guards, not dead assertions.
development
Curate the web-capture index. Use when the capture backlog grows, captures sit unprocessed at seedling/pending, or to surface stored research during work.
testing
Probe memory/summary clarity via dual anchor questions: task progress, info gaps. Use when verifying session state or summary before handoff or compression.