Voice Analysis

This is a structured framework for capturing and documenting someone's writing voice so you can reproduce it authentically. It walks through eight phases: collecting writing samples (including "peak voice" and "off voice" examples), analyzing sentence patterns and punctuation signatures, mapping word choices and metaphor preferences, identifying emotional texture, and synthesizing everything into a reusable voice guide. The approach is thorough, maybe more thorough than most use cases need, but if you're ghost writing, maintaining voice across a team, or training models on specific author styles, the lexical fingerprinting and conceptual DNA sections give you concrete tracking tables instead of vague impressions. The litmus test framing (makes the source say "yes, that's me" not "I guess that's accurate") keeps you honest about whether you're actually capturing spirit or just mechanically copying surface patterns.

skills.sh installs: 451
GitHub stars: 182
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add jwynia/agent-skills --skill voice-analysis --agent claude-code

Installs into .claude/skills of the current project.

Files

Voice & Tone Analysis

Purpose

Extract and document a writer's distinctive voice patterns for consistent reproduction. Creates a "voice guide" that enables authentic writing that sounds like the source, not a generic approximation.

Core Principle

Capture spirit, not just mechanics. The goal is writing that makes the source say "yes, that's me" not "I guess that's accurate."

Phase 1: Sample Collection

Gather 5-10 Examples from Each Category

Peak Voice - Writing they identify as "most them"

Off-Voice - Writing that doesn't represent them well

Different Contexts:

Technical/instructional content
Persuasive/argumentative pieces
Narrative/storytelling
Casual communication (emails, messages)
Formal communication
Emotional/vulnerable content

Self-Report Prompts

Rewrite Exercise: Ask: "Rewrite this neutral paragraph in your voice:"

"The new policy will be implemented next month. It includes several changes to current procedures. Employees should review documentation and submit questions by the deadline."

Rule Breaking: "What writing 'rules' do you consistently ignore? Why?"

SKILL.md on GitHub