From editorial-forge
This skill should be used when the user asks to "build a voice profile," "extract [person]'s voice," "create a voice file," "how does [person] write," "do the voice interview," "voice architect for [name]," "import a voice profile," or any request to capture an author's authentic writing voice through structured interview. Also trigger when the editorial-forge skill reaches Phase 3 (voice extraction). This skill works for ANY author — it extracts voice from the human through interview, never applies a preset voice. The resulting voice profile is per-project but can be imported into other projects via drag-and-drop.
How this skill is triggered — by the user, by Claude, or both
Slash command
/editorial-forge:voice-architectThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Build an author's voice profile through structured interview. The profile captures how they argue, their sentence rhythm, vocabulary, emotional patterns, and what they'd never say — everything needed to generate prose that sounds like THEM, not like AI.
Build an author's voice profile through structured interview. The profile captures how they argue, their sentence rhythm, vocabulary, emotional patterns, and what they'd never say — everything needed to generate prose that sounds like THEM, not like AI.
Voice is not style. Style is mechanics (sentence length, punctuation, word choice). Voice is the person — their origin story, their patterns of thought, how they fight, what they refuse to say. This interview extracts both.
Ask ONE question at a time. Wait for the full answer before proceeding. These questions may take hours or days to answer — save state after each.
"How did you come to this work? Not your resume — the moment you knew this was your thing."
What to extract: The emotional entry point. Where conviction comes from. Whether they lead with stories or credentials.
"What do you see that others miss? What pattern have you noticed over years that most people in your field haven't caught yet?"
What to extract: Intellectual signature. How they synthesize. Whether they think in systems, narratives, or data.
"When you're making a case to someone who disagrees, how do you do it? Stories first? Data first? Do you get loud or get quiet?"
What to extract: Argument structure. Rhetorical instincts. Whether they're deductive, narrative, Socratic, or confrontational.
"What's the thing in your field that makes you genuinely angry? The practice, the phrase, the mindset that you'd burn if you could?"
What to extract: Emotional triggers. Where conviction turns to heat. The forbidden territory they patrol.
"Pick something complex in your domain. Explain it to me like I'm smart but from a different field."
What to extract: Teaching style. Metaphor preferences. How they simplify without dumbing down. Technical vocabulary comfort.
"When you picture someone reading your work and thinking 'they get it' — who is that person and what specifically did you say that landed?"
What to extract: Who they write FOR. What "landing" feels like to them. Their theory of impact.
"What's the popular advice in your space that you refuse to give? Why?"
What to extract: Intellectual boundaries. Where they diverge from consensus. The contrarian positions they hold with conviction.
"Do you write like you talk? More formal? Less? What's the closest published thing to how you actually sound?"
What to extract: Self-awareness about register. The gap (or lack of gap) between spoken and written voice. Reference points for calibration.
After all 8 answers are collected, analyze for:
Generate the voice profile document:
# Voice Profile: [Author Name]
## Created: [date]
## Last validated: [date]
## Project: [project name]
### How They Argue
[Analysis of argument style with examples from interview answers]
### Sentence Rhythm
[Observed patterns: length, variation, fragment usage, paragraph style]
### Vocabulary & Register
[Technical depth, jargon comfort, metaphor preferences, words they use vs. avoid]
### Emotional Patterns
[Where they get heated, where they pull back, what triggers conviction]
### Teaching Mode
[How they explain complex things, metaphor style, simplification approach]
### Forbidden Patterns
[Phrases, structures, or tones that would never come from this author]
[Include specific examples: "This author would never say 'It's worth noting that...'"]
### "Sounds Like Me" Samples
[3-5 short passages the author confirmed as authentic to their voice]
[Drawn from interview answers — the parts where they were most themselves]
### Anti-Detection Markers
[Specific checklist items calibrated to THIS author's natural style]
- [ ] Contraction rate: [X]% (based on observed patterns)
- [ ] Sentence length range: [X]-[Y] words typical
- [ ] Fragment usage: [frequency and purpose]
- [ ] Paragraph length: [typical range]
- [ ] Technical vocabulary depth: [level]
- [ ] Emotional vocabulary: [patterns]
- [ ] Conjunction starters: [frequency]
- [ ] Metaphor density: [low/medium/high]
Present the voice profile to the author: "Does this sound like you? What's wrong? What's missing?"
Iterate until the author confirms. Log each iteration in the authorship record.
When a voice profile file is found in a project's voice-profiles/ directory that wasn't created during this project's interview:
voice_interview_answer decisions in the authorship record)voice_profile_imported decision in the authorship recordAfter each interview answer:
voice-profiles/[author-name]-raw-qa.mdvoice_interview_answer decision in the authorship recordpending_question with the next question and contextprogress.voice_profile to in_progressAfter profile generation and validation:
voice-profiles/[author-name].mdvoice_profile_generated and voice_profile_validatedprogress.voice_profile to completepending_questionnpx claudepluginhub moxywolfllc/moxywolf-plugins --plugin editorial-forgeBlocks Edit/Write/Bash actions until Claude investigates importers, data schemas, and user instructions. Improves output quality by forcing concrete facts before edits.