voice-dna-creator
- Repo stars 36
- Author updated Live
- Author repo ai-co-writing-claude-skills
- Domain
- Documentation
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @az9713 · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: voice-dna-creator
description: Analyze writing samples to create a comprehensive voice DNA profile. Use when the user wants to…
category: documentation
runtime: no special runtime
---
# voice-dna-creator output preview
## PART A: Task fit
- Use case: Analyze writing samples to create a comprehensive voice DNA profile. Use when the user wants to capture their unique writing voice, needs to create a voice profile for AI content, or is setting up a new writing system..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “When to Use This Skill / Requirements / Analysis Process” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Analyze writing samples to create a comprehensive voice DNA profile. Use when the user wants to capture their unique writing voice, needs to create a voice profile for AI content, or is setting up a new writing system.”.
- **02** When the source has headings, the agent prioritizes “When to Use This Skill / Requirements / Analysis Process” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source mentions slash commands such as `/context`; use them first when your agent supports command triggers.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “When to Use This Skill / Requirements / Analysis Process”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: voice-dna-creator
description: Analyze writing samples to create a comprehensive voice DNA profile. Use when the user wants to…
category: documentation
source: az9713/ai-co-writing-claude-skills
---
# voice-dna-creator
## When to use
- Analyze writing samples to create a comprehensive voice DNA profile. Use when the user wants to capture their unique w…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “When to Use This Skill / Requirements / Analysis Process” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "voice-dna-creator" {
input -> user goal + target files + boundaries + acceptance criteria
context -> When to Use This Skill / Requirements / Analysis Process
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} Voice DNA Creator
Analyze writing samples to extract and codify a unique voice profile that AI can use to replicate your authentic writing style.
When to Use This Skill
- Setting up a new writing system
- Creating voice profiles for clients (ghostwriting)
- Updating voice profiles after style evolution
- Onboarding into content creation workflow
Requirements
The user must provide:
- Minimum: 3 writing samples (500+ words each)
- Ideal: 5-10 samples across different content types
- Best: Mix of casual (social posts) and formal (articles) content
Analysis Process
Step 1: Collect Samples
Ask: "Please share 3-10 writing samples that represent your authentic voice. These can be:
- Newsletter issues
- Blog posts
- Social media posts
- Emails you've written
- Any content where you feel 'this sounds like me'
Paste them here or point me to files in the knowledge folder."
Step 2: Analyze Core Elements
For each sample, analyze:
Personality Markers
- What personality traits come through?
- What's the energy level?
- How does the writer relate to the reader?
Emotional Range
- What emotions are expressed?
- How intense are they?
- What's the dominant emotional tone?
Communication Style
- Formality level (casual to professional)
- Sentence length patterns
- Paragraph structure
- Use of questions, commands, statements
Language Patterns
- Signature phrases that repeat
- Power words used frequently
- Transition phrases
- Opening and closing patterns
What They Avoid
- Words or phrases never used
- Tones never taken
- Approaches avoided
Formatting Habits
- Emoji usage
- List usage
- Header styles
- Bold/italic patterns
Step 3: Synthesize Findings
Combine analysis across all samples to identify:
- Consistent patterns (appear in most samples)
- Contextual variations (change based on content type)
- Core voice elements (never change)
Step 4: Generate Voice DNA
Create the profile following this structure:
{
"voice_dna": {
"version": "1.0",
"last_updated": "YYYY-MM-DD",
"core_essence": {
"identity": "",
"primary_role": "",
"unique_angle": ""
},
"personality_traits": {
"primary": [],
"how_it_shows": {}
},
"emotional_palette": {
"dominant_emotions": [],
"emotional_range": {},
"energy_level": ""
},
"communication_style": {
"formality": "",
"complexity": "",
"sentence_structure": {},
"paragraph_style": ""
},
"language_patterns": {
"signature_phrases": [],
"power_words": [],
"words_to_avoid": [],
"transitions": []
},
"never_say": {
"phrases": [],
"tones": [],
"approaches": []
},
"formatting_preferences": {},
"content_philosophy": {},
"voice_examples": {
"opening_lines": [],
"closing_lines": [],
"transitional_phrases": []
}
}
}
Output Instructions
After analysis, present key findings in a summary
Generate the complete JSON voice profile
Save to
/context/voice-dna.jsonProvide 3 example sentences written in the captured voice for validation
Ask: "Does this capture your voice? What would you adjust?"
Best Practices
- Focus on TONE and PERSONALITY, not just word choice
- Avoid creating a profile that just repeats phrases
- Capture the "feeling" of the writing, not just patterns
- Include what NOT to do (equally important)
- Make the profile actionable for content generation
Validation Test
After creating the profile, write a short paragraph on any topic using ONLY the voice DNA as guidance. Ask the user: "Does this sound like you?"
If not, iterate on the profile based on feedback.
Common Pitfalls to Avoid
- Don't just list frequently used words
- Don't create a parody of the voice (too exaggerated)
- Don't ignore context (social posts ≠ articles)
- Don't miss the underlying personality
- Don't forget emotional elements
Decide Fit First
Design Intent
How To Use It
Boundaries And Review