Skip to content
Content
Skill

/writing-dna-discovery

Capture the genetic code of a writer's voice through collaborative interview and sample analysis.

From plugin
robertguss-claude-code-toolkit
11329 skills7 agents4 commands
Install
$ npx -y skills add robertguss/claude-code-toolkit --skill writing-dna-discovery --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/writing-dna-discovery

Context preview

The summary Claude sees to decide when to auto-load this skill.

Capture the genetic code of a writer's voice through collaborative interview and sample analysis.

SKILL.md

writing-dna-discovery.SKILL.md
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

Read more
Ships withrobertguss-claude-code-toolkit

Extend Claude Code with specialized workflows, automatic formatting, and better defaults. Skills give Claude domain expertise—brainstorming methods, documentation generation, book writing pipelines.

Get the whole plugin