/writing-dna-discovery
Capture the genetic code of a writer's voice through collaborative interview and sample analysis.
Claude Code
$ npx -y skills add robertguss/claude-code-toolkit --skill writing-dna-discovery --agent claude-code
Codex
$ npx skills add robertguss/claude-code-toolkit --skill writing-dna-discovery -a codex -y
Cursor
$ npx skills add robertguss/claude-code-toolkit --skill writing-dna-discovery -a cursor -y
Gemini CLI
$ npx skills add robertguss/claude-code-toolkit --skill writing-dna-discovery -a gemini-cli -y
GitHub Copilot
$ npx skills add robertguss/claude-code-toolkit --skill writing-dna-discovery -a github-copilot -y
OpenCode
$ npx skills add robertguss/claude-code-toolkit --skill writing-dna-discovery -a opencode -y
Windsurf
$ npx skills add robertguss/claude-code-toolkit --skill writing-dna-discovery -a windsurf -y
SKILL.md
writing-dna-discovery.SKILL.mdname: writing-dna-discovery
license: Proprietary
metadata:
author: robertguss
version: "1.0"
description:
Capture a writer's voice DNA through collaborative interview and sample
analysis. Use when someone wants to document their writing voice for use with
a ghost writer skill. Produces a Voice DNA Document with patterns,
anti-patterns, and actionable guidance. Handles one register/mode per session,
supports refinement over time.
Writing DNA Discovery
Capture the genetic code of a writer's voice through collaborative interview and sample analysis.
Core Philosophy
This is genuine intellectual partnership, not interrogation or extraction:
- **Contribute substance** — Offer observations, pattern recognition, and
insights proactively. Don't just ask questions; bring analysis to the table.
- **Push back with reasoning** — Challenge vague answers, but always explain
WHY. "That description could apply to many writers—what makes YOUR voice specifically recognizable?"
- **One question at a time** — Never overwhelm with multiple questions. One
focused question per response.
- **The human is the expert** — They know their voice better than any analysis
can capture. Your job is to help them articulate and document it.
- **Surface problems early** — If something contradicts or doesn't fit, say so.
A flawed DNA document produces flawed ghost writing.
What This Skill Does
- Analyzes writing samples for distinctive patterns
- Conducts collaborative interview to surface choices and preferences
- Documents voice dimensions with examples
- Produces actionable Voice DNA Document for ghost writer skill
- Supports refinement and evolution over time
Key Design Principles
**One Register Per Session** Focus on a single mode: fiction prose, blog posts, technical writing, etc. Each register may have different voice characteristics. The user can create multiple DNA documents for different registers.
**80% Approximation Goal** The DNA document enables a ghost writer to produce first drafts at ~80% accuracy. The human adds the remaining 20%—the creative spark, situational judgment, and final polish. We're not replacing the writer; we're giving them a strong starting point.
**Living Document** The Voice DNA Document grows richer over time. Initial sessions capture the foundation; return sessions deepen, refine, and adapt as the writer's voice evolves.
**Comprehensive Capability, Intelligent Application** This skill has a full arsenal of voice dimensions but deploys them thoughtfully. Don't march through every dimension mechanically. Focus on what's most distinctive and relevant for this writer and register.
Session Types
| Type | Signal | Approach | | ---------------------------- | -------------------------------------- | -------------------------------------------------- | | **Initial Discovery** | New user, no existing DNA doc | Full discovery flow | | **Sample Addition** | New samples + existing DNA doc | Analyze new samples, compare to profile, integrate | | **Dimension Deep-Dive** | "I want to go deeper on X" | Focus on specific dimension | | **Refinement from Feedback** | "The ghost writer keeps doing X wrong" | Convert feedback to anti-patterns | | **Evolution Update** | "My writing has changed" | Compare old vs. new, update profile | | **New Register** | "I want to add my fiction voice" | New discovery for different mode |
Discovery Methodology
When User Provides Samples
**1. Initial Scan** Read the sample(s). Identify the 3-5 most distinctive patterns that jump out. What makes this writing recognizably theirs?
**2. Share Observations** Present your findings: "Here's what I'm noticing about your writing..." Be specific. Give examples from their text.
**3. Dialogue & Refinement** The user confirms, adjusts, or adds context. "Actually, that's unusual for me—this piece was different because..." This dialogue refines your understanding.
**4. Probe Deeper** Ask targeted questions based on what emerged. If their sentence rhythm is distinctive, dig into that. If their tone is unusual, explore why.
**5. Synthesize** Update the DNA document at meaningful milestones, not constantly. Capture patterns, examples, and the reasoning behind choices.
Discovery Techniques
Beyond standard Q&A, use these to surface voice:
**Comparative Choices**
> "Would you write 'He walked into the room' or 'He stepped into the room' or > something else?"
**Contrastive Examples**
> "This reads more Hemingway than David Foster Wallace. Where do you see > yourself on that spectrum?"
**Elimination Exercises**
> "Which of these words would you NEVER use: utilize, leverage, facilitate, > synergize?"
**Completion Prompts** Give a sentence starter; see how they naturally finish it.
> "The problem with most writing advice is..."
**Rewrite Exercises** Show generic AI-sounding text; ask them to rewrite it in their voice.
> "Transform this: 'This methodology provides a comprehensive framework for > understanding the complex dynamics at play.'"
When User Has No/Few Samples
- Use interview-driven discovery
- Provide generative prompts to surface their voice
- Ask them to write brief responses to questions
- Build DNA document from their responses
- Note lower confidence until samples confirm patterns
Voice Dimension Framework
Core Dimensions (Always Explore)
These should be addressed in every discovery session:
| Dimension | What It Captures | | --------------------------- | -------------------------------------------------------------------------- | | **Sentence Rhythm** | Length v
Read more
name: writing-dna-discovery license: Proprietary metadata: author: robertguss version: "1.0" description: Capture a writer's voice DNA through collaborative interview and sample analysis. Use when someone wants to document their writing voice for use with a ghost writer skill. Produces a Voice DNA Document with patterns, anti-patterns, and actionable guidance. Handles one register/mode per session, supports refinement over time.
Writing DNA Discovery
Capture the genetic code of a writer's voice through collaborative interview and sample analysis.
Core Philosophy
This is genuine intellectual partnership, not interrogation or extraction:
- **Contribute substance** — Offer observations, pattern recognition, and
insights proactively. Don't just ask questions; bring analysis to the table.
- **Push back with reasoning** — Challenge vague answers, but always explain
WHY. "That description could apply to many writers—what makes YOUR voice specifically recognizable?"
- **One question at a time** — Never overwhelm with multiple questions. One
focused question per response.
- **The human is the expert** — They know their voice better than any analysis
can capture. Your job is to help them articulate and document it.
- **Surface problems early** — If something contradicts or doesn't fit, say so.
A flawed DNA document produces flawed ghost writing.
What This Skill Does
- Analyzes writing samples for distinctive patterns
- Conducts collaborative interview to surface choices and preferences
- Documents voice dimensions with examples
- Produces actionable Voice DNA Document for ghost writer skill
- Supports refinement and evolution over time
Key Design Principles
**One Register Per Session** Focus on a single mode: fiction prose, blog posts, technical writing, etc. Each register may have different voice characteristics. The user can create multiple DNA documents for different registers.
**80% Approximation Goal** The DNA document enables a ghost writer to produce first drafts at ~80% accuracy. The human adds the remaining 20%—the creative spark, situational judgment, and final polish. We're not replacing the writer; we're giving them a strong starting point.
**Living Document** The Voice DNA Document grows richer over time. Initial sessions capture the foundation; return sessions deepen, refine, and adapt as the writer's voice evolves.
**Comprehensive Capability, Intelligent Application** This skill has a full arsenal of voice dimensions but deploys them thoughtfully. Don't march through every dimension mechanically. Focus on what's most distinctive and relevant for this writer and register.
Session Types
| Type | Signal | Approach | | ---------------------------- | -------------------------------------- | -------------------------------------------------- | | **Initial Discovery** | New user, no existing DNA doc | Full discovery flow | | **Sample Addition** | New samples + existing DNA doc | Analyze new samples, compare to profile, integrate | | **Dimension Deep-Dive** | "I want to go deeper on X" | Focus on specific dimension | | **Refinement from Feedback** | "The ghost writer keeps doing X wrong" | Convert feedback to anti-patterns | | **Evolution Update** | "My writing has changed" | Compare old vs. new, update profile | | **New Register** | "I want to add my fiction voice" | New discovery for different mode |
Discovery Methodology
When User Provides Samples
**1. Initial Scan** Read the sample(s). Identify the 3-5 most distinctive patterns that jump out. What makes this writing recognizably theirs?
**2. Share Observations** Present your findings: "Here's what I'm noticing about your writing..." Be specific. Give examples from their text.
**3. Dialogue & Refinement** The user confirms, adjusts, or adds context. "Actually, that's unusual for me—this piece was different because..." This dialogue refines your understanding.
**4. Probe Deeper** Ask targeted questions based on what emerged. If their sentence rhythm is distinctive, dig into that. If their tone is unusual, explore why.
**5. Synthesize** Update the DNA document at meaningful milestones, not constantly. Capture patterns, examples, and the reasoning behind choices.
Discovery Techniques
Beyond standard Q&A, use these to surface voice:
**Comparative Choices**
> "Would you write 'He walked into the room' or 'He stepped into the room' or > something else?"
**Contrastive Examples**
> "This reads more Hemingway than David Foster Wallace. Where do you see > yourself on that spectrum?"
**Elimination Exercises**
> "Which of these words would you NEVER use: utilize, leverage, facilitate, > synergize?"
**Completion Prompts** Give a sentence starter; see how they naturally finish it.
> "The problem with most writing advice is..."
**Rewrite Exercises** Show generic AI-sounding text; ask them to rewrite it in their voice.
> "Transform this: 'This methodology provides a comprehensive framework for > understanding the complex dynamics at play.'"
When User Has No/Few Samples
- Use interview-driven discovery
- Provide generative prompts to surface their voice
- Ask them to write brief responses to questions
- Build DNA document from their responses
- Note lower confidence until samples confirm patterns
Voice Dimension Framework
Core Dimensions (Always Explore)
These should be addressed in every discovery session:
| Dimension | What It Captures | | --------------------------- | -------------------------------------------------------------------------- | | **Sentence Rhythm** | Length v
Extend Claude Code with specialized workflows, automatic formatting, and better defaults. Skills give Claude domain expertise—brainstorming methods, leading a project with worker agents, project wikis, book writing pipelines.
Other skills on claude-code-toolkit.
dhh-writing
This skill should be used when writing in the distinctive style of David Heinemeier Hansson (DHH). It applies when creating blog…
every-style-editor
This skill should be used when reviewing or editing copy to ensure adherence to Every's style guide. It provides a systematic…
pragmatic-writing
This skill should be used when writing technical content in the style of Hunt/Thomas (The Pragmatic Programmer) and Joel Spolsky…
voice-capture
This skill should be used when extracting voice profiles from sample text, creating voice documentation, or matching a specific…
writing-orchestration
This skill should be used when orchestrating complex writing workflows with multiple phases. It provides two-agent orchestration…
More skills from other plugins.
prompt-lookup
Activates when the user asks about AI prompts, needs prompt templates, wants to search for prompts, or mentions prompts.chat. Use…
ppt-master
AI-driven presentation workflow for generating editable PPTX decks and slides, reconstructing page visuals, creating reusable…
morph-ppt
Use this skill when the user wants a .pptx with smooth cross-slide animation — PowerPoint Morph transitions, Keynote-style…
frontend-slides
Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to…
Questions about writing-dna-discovery.
- Which coding agents can use writing-dna-discovery?
- writing-dna-discovery installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

