voice-editor
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
Chinese<objective>
Transform generic or AI-generated content into voice-matched writing using a VOICE.md profile.
Voice doesn't live in first drafts - it lives in editing choices. This skill guides the 6-pass editing process that turns AI's generic output into something distinctively yours.
</objective>
<quick_start>
Provide:
- Content to edit (paste or file path)
- VOICE.md location (default: or project's
~/.claude/voice/VOICE.md).claude/VOICE.md
The skill will:
- Run slop detection on the content
- Identify voice mismatches against your profile
- Perform multi-pass editing (Structure → Voice → Polish)
- Output edited content with change annotations
- Suggest VOICE.md updates based on patterns found </quick_start>
<the_editing_reality>
The 30-40% Rule:
Even with a perfect style guide, expect to edit 30-40% of AI output to make it distinctively yours. This isn't a problem—it's the feature.
30-40% editing effort is dramatically less than 100% writing-from-scratch effort, while producing work that sounds more like you than unguided AI ever could.
If you're editing more than 50%: Your style guide needs refinement, or your prompts need work.
If you're editing less than 20%: You might be accepting too much generic content.
</the_editing_reality>
<editing_workflow>
<pass number="1" name="Structure Check">
Focus: Does the organization serve the content?
Opening Mechanics (from craft-rules):
- Does opening create a SPECIFIC question? Not vague mystery - readers need enough context to form a particular question they want answered
- Does first paragraph contain change or threat of change? Brains notice disruption of status quo
- Is first paragraph under 50 words / 3 sentences?
- First line hits 3+ of: question, character, setting, tone, movement?
Questions to ask:
- Does the opening hook or just clear throat?
- Is there a clear progression of ideas?
- Does each section earn its place?
- Is anything redundant or missing?
- Does the conclusion land or just stop?
Scene/Section Structure:
- Does each section follow Goal → Conflict → Outcome?
- Are transitions connected by "because" not "and then"?
- Are characters/subjects in motion during slow passages?
Actions:
- Cut throat-clearing openings ("In this article, we'll explore...")
- Reorder sections for better flow
- Merge redundant sections
- Add missing transitions
- Strengthen weak conclusions
- Add change to opening if missing - start with what changed, not background
- Make question specific - "Why is the other side of the bed cold?" not "Something is happening" </pass>
Check against VOICE.md:
- Sentence length patterns (matching variance?)
- Vocabulary fingerprint (right formality level?)
- Tone markers (humor, directness, reader relationship?)
- Structural habits (lists vs prose, formatting?)
- Opinion expression (appropriate confidence level?)
Actions:
- Replace formal language with conversational equivalents
- Vary sentence lengths to match profile
- Add characteristic phrases from the voice profile
- Adjust opinion strength to match profile
- Fix paragraph rhythm </pass>
Scan for:
- Tier 1 phrases (remove immediately)
- Tier 2 patterns (check context)
- Tier 3 clusters (break up if grouped)
- Structural tells (uniformity, over-balance)
- Staccato fragment spam (3+ consecutive short declarative sentences)
- Comparator sentences ("This isn't X. It's Y." patterns)
Actions:
- Delete or replace all Tier 1 phrases
- Evaluate Tier 2 in context, remove if generic
- Redistribute Tier 3 to avoid clustering
- Vary sentence lengths if too uniform
- Rebalance sections if all equal weight
- Combine staccato fragments into flowing prose with commas, em-dashes, or conjunctions
- Rewrite comparators directly — just say what something IS, don't waste words on what it isn't </pass>
What to cut:
- Generic superlatives without claims ("game-changing," "revolutionary")
- Hedging that adds no value ("it might be argued that")
- Corporate platitudes ("leverage synergies")
- Anything that sounds like a press release
What to add:
- Your actual opinion (not the diplomatic version)
- Specific examples from your experience
- Honest acknowledgment of limitations
- Your characteristic quirks and phrases
- Conversational asides that show how you think </pass>
The read-aloud test:
- Read the piece aloud (or use text-to-speech)
- Mark every place you stumble
- Note where you'd naturally pause vs. where punctuation forces pauses
- Identify sentences that feel too long or choppy
Sentence Craft Checks (from craft-rules):
- Active verbs predominate? Search for "was [verb]ed" passive patterns
- Word order follows action sequence? Actor → Action → Recipient (filmic)
- Objects have ~3 specific qualities, not abstract adjectives?
- Sentence length varies deliberately? Short punch, then longer exploration
- No clichéd metaphors? (Fresh comparisons trigger more brain activity)
Hemingway Principles:
- Emphasize nouns
- Choose active verbs
- Adjectives: few but apt
- Short sentences by default
- Long sentences ONLY for: speeding action, describing flow, making short sentences pop
Actions:
- Break sentences where you ran out of breath
- Combine choppy sentences that flow together
- Add rhythm variation (short punch, longer exploration)
- Fix awkward transitions
- Smooth unnatural phrasing
- Convert passive to active - "The ball was thrown by John" → "John threw the ball"
- Reorder for transitive flow - "Jane gave a kitten to her Dad" beats "Jane gave her Dad a kitten"
- Replace abstract with specific - "terrible" → details that create terror </pass>
Ask yourself:
"Would someone who knows me recognize this as mine before seeing my name?"
If no:
- What's missing? Add it.
- What's wrong? Fix it.
- What's generic? Make it specific.
If yes:
- You're done. Ship it. </pass>
</editing_workflow>
<what_to_cut>
Always remove:
- Generic superlatives without specific claims
- Hedging language that softens everything
- Unnecessary qualification that adds no value
- Corporate platitudes that mean nothing
- Anything that sounds like a committee wrote it
- Motivational poster language
- Flattery sandwiches ("While X has merit, Y offers...")
Examples:
-
❌ "This groundbreaking approach revolutionizes..."
-
✅ "This cuts processing time from 4 hours to 15 minutes"
-
❌ "It's worth noting that in many cases..."
-
✅ [Just make the point directly]
-
❌ "Unlock your potential with powerful insights"
-
✅ "Stop wasting time on tasks AI handles in seconds" </what_to_cut>
<what_to_add>
Voice elements AI misses:
- Your actual opinion - Not the diplomatic version AI produces
- Specific examples - From your experience, not generic training data
- Honest limitations - Not fake confidence in uncertain claims
- Characteristic quirks - Phrases your style guide might have missed
- Conversational asides - How you actually think through problems
- Rough edges - The imperfections that make writing human
Examples:
- Add: "Three hours later (no hyperbole), I finally got it working"
- Add: "Here's where I screwed up the first time..."
- Add: "Look, I'm not sure this is right, but..."
- Add: [Your characteristic phrases from VOICE.md] </what_to_add>
<output_format>
For edited content, provide:
markdown
undefined<objective>
使用VOICE.md档案将通用或AI生成的内容转换为符合个人风格的写作。
个人风格并非存在于初稿中——而是体现在编辑的选择里。本Skill会引导你完成6轮编辑流程,将AI的通用输出转变为极具个人特色的内容。
</objective>
<quick_start>
请提供:
- 待编辑内容(粘贴文本或文件路径)
- VOICE.md位置(默认路径:或项目目录下的
~/.claude/voice/VOICE.md).claude/VOICE.md
本Skill将:
- 对内容进行AI冗余表达检测
- 识别内容与你的档案之间的风格不匹配之处
- 执行多轮编辑(结构调整→风格匹配→润色打磨)
- 输出带有修改标注的编辑后内容
- 根据发现的模式,提供VOICE.md的更新建议 </quick_start>
<the_editing_reality>
30-40%法则:
即便拥有完美的风格指南,你仍需要编辑AI输出内容的30-40%,才能使其极具个人特色。这并非问题——而是核心价值所在。
30-40%的编辑工作量相比从零开始写作的100%工作量大幅减少,同时产出的内容比未经引导的AI输出更贴合你的个人风格。
如果你的编辑量超过50%: 你的风格指南需要优化,或者你的提示词需要调整。
如果你的编辑量不足20%: 你可能接受了过多通用化内容。
</the_editing_reality>
<editing_workflow>
<pass number="1" name="Structure Check">
重点: 内容结构是否服务于表达需求?
开篇技巧(来自写作规则):
- 开篇是否提出了具体问题?不要模糊的悬念——读者需要足够的上下文来形成一个他们想要得到答案的具体问题
- 第一段是否包含变化或变化的威胁?大脑会注意到现状的被打破
- 第一段是否少于50词/3句话?
- 第一句话是否包含3个及以上元素:问题、人物、场景、语气、动态?
需要思考的问题:
- 开篇是引人入胜还是只是铺垫?
- 观点是否有清晰的递进逻辑?
- 每个章节是否有存在的必要?
- 是否有冗余或缺失的内容?
- 结尾是有力收尾还是仓促结束?
场景/章节结构:
- 每个章节是否遵循目标→冲突→结果的结构?
- 过渡是否用“因为”而非“然后”来衔接?
- 在节奏缓慢的段落中,人物/主题是否有动态?
行动项:
- 删除铺垫式的开篇(如“在本文中,我们将探讨……”)
- 重新调整章节顺序以提升流畅度
- 合并冗余章节
- 添加缺失的过渡内容
- 强化薄弱的结尾
- 如果开篇缺少变化元素,补充进去——从变化入手,而非背景介绍
- 让问题更具体——比如“为什么床的另一边是凉的?”而非“有事情发生了” </pass>
对照VOICE.md检查:
- 句子长度模式(是否匹配变化规律?)
- 词汇特征(正式程度是否合适?)
- 语气标记(幽默、直接性、与读者的关系?)
- 结构习惯(列表 vs 散文、格式?)
- 观点表达(自信程度是否恰当?)
行动项:
- 用口语化表达替换正式语言
- 调整句子长度以匹配档案风格
- 添加语音档案中的标志性短语
- 调整观点的语气强度以匹配档案
- 修正段落节奏 </pass>
需要扫描的内容:
- 一级短语(立即删除)
- 二级模式(结合上下文判断)
- 三级集群(如果集中出现则拆分)
- 结构特征(过于统一、平均分配权重)
- 断句碎片堆砌(3个及以上连续的简短陈述句)
- 对比句式(“这不是X,而是Y”的模式)
行动项:
- 删除或替换所有一级短语
- 结合上下文评估二级内容,若通用化则删除
- 分散三级内容以避免集中堆砌
- 若句子长度过于统一,则调整变化
- 若各章节权重均等,则重新平衡
- 将断句碎片合并为流畅的散文,使用逗号、破折号或连词
- 直接重写对比句式——直接说明事物是什么,不要浪费文字在它不是什么上 </pass>
需要删除的内容:
- 无具体支撑的通用最高级(如“改变游戏规则的”、“革命性的”)
- 无价值的模糊表述(如“有人可能会认为”)
- 企业套话(如“利用协同效应”)
- 任何听起来像新闻稿的内容
需要添加的内容:
- 你真实的观点(而非外交辞令式的版本)
- 来自你个人经验的具体例子
- 对局限性的坦诚承认
- 你特有的习惯用语和短语
- 能体现你思考方式的口语化旁白 </pass>
朗读测试:
- 大声朗读文章(或使用文本转语音工具)
- 标记所有你停顿的地方
- 注意你自然会停顿的位置 vs 标点强制你停顿的位置
- 识别过长或过于零碎的句子
句子写作检查(来自写作规则):
- 主动动词是否占主导?搜索“was [动词]ed”的被动句式
- 词序是否遵循动作顺序?主语→动作→宾语(电影式表达)
- 事物是否有3个左右的具体特质,而非抽象形容词?
- 句子长度是否有刻意变化?先用短句突出重点,再用长句展开
- 有无陈词滥调的比喻?(新颖的比喻会更能激发大脑活动)
海明威原则:
- 强调名词
- 选择主动动词
- 形容词:少而精
- 优先使用短句
- 长句仅用于:加速动作节奏、描述流程、衬托短句的冲击力
行动项:
- 在你喘不过气的地方拆分句子
- 将流畅衔接的零碎句子合并
- 添加节奏变化(短句突出重点,长句展开内容)
- 修正生硬的过渡
- 平滑不自然的措辞
- 将被动句转换为主动句——比如“球被约翰扔出去”→“约翰扔出了球”
- 调整语序以提升传递效率——比如“简把小猫给了她爸爸”不如“简给她爸爸一只小猫”
- 用具体内容替换抽象表述——比如“可怕的”→ 用细节来营造恐怖感 </pass>
问自己:
“认识我的人在看到名字之前,会认出这是我写的吗?”
如果答案是否:
- 缺少什么?补充进去。
- 哪里有问题?修正它。
- 哪些内容太通用?让它更具体。
如果答案是:
- 完成了。发布吧。 </pass>
</editing_workflow>
<what_to_cut>
务必删除的内容:
- 无具体支撑的通用最高级
- 弱化所有内容的模糊表述
- 无价值的不必要限定
- 无意义的企业套话
- 任何听起来像委员会写的内容
- 励志海报式语言
- 三明治式恭维(如“虽然X有优点,但Y提供……”)
示例:
-
❌ “这种开创性的方法彻底改变了……”
-
✅ “这将处理时间从4小时缩短到15分钟”
-
❌ “值得注意的是,在很多情况下……”
-
✅ [直接表达观点]
-
❌ “通过强大的见解释放你的潜力”
-
✅ “别再把时间浪费在AI几秒就能完成的任务上” </what_to_cut>
<what_to_add>
AI容易忽略的风格元素:
- 你真实的观点——不是AI生成的外交辞令式版本
- 具体例子——来自你的经验,而非通用训练数据
- 坦诚的局限性——对不确定的内容不要假装自信
- 特有的习惯——你的风格指南可能遗漏的短语
- 口语化旁白——你实际思考问题的方式
- 粗糙的边缘——让写作更具人情味的不完美之处
示例:
- 添加:“三个小时后(没有夸张),我终于让它正常工作了”
- 添加:“这是我第一次搞砸的地方……”
- 添加:“说实话,我不确定这是否正确,但是……”
- 添加:[来自VOICE.md的你的标志性短语] </what_to_add>
<output_format>
编辑后的内容请按以下格式提供:
markdown
undefinedEdited Content
Edited Content
[Full edited content here]
[完整的编辑后内容]
Edit Summary
Edit Summary
Passes completed: 6/6
Estimated edit percentage: [X]%
Voice match confidence: [Low/Medium/High]
完成的编辑轮次: 6/6
预估编辑比例: [X]%
风格匹配度: [低/中/高]
Major Changes
主要修改
- [Most significant change and why]
- [Second major change]
- [Third major change]
- [最重大的修改及原因]
- [第二大修改]
- [第三大修改]
Slop Removed
移除的冗余内容
- [List of AI patterns found and removed]
- [发现并移除的AI模式列表]
Voice Elements Added
添加的风格元素
- [List of voice-specific additions]
- [添加的特定风格内容列表]
Remaining Concerns
剩余问题
- [Any areas that still feel off]
- [Suggestions for further refinement]
- [仍然感觉不合适的地方]
- [进一步优化的建议]
VOICE.md Update Suggestions
VOICE.md更新建议
- [Patterns discovered that should be added to voice profile]
- [Phrases that worked well - consider adding to "use freely" list]
</output_format>
<editing_modes>
<mode name="light">
**Use when:** Content is close to voice, just needs polish
**Passes:** 3, 5, 6 (Slop Removal, Rhythm, Final Check)
**Expected edit:** 10-20%
**Time:** 5-10 minutes per 500 words
</mode>
<mode name="standard">
**Use when:** Typical AI output with style guide
**Passes:** All 6
**Expected edit:** 30-40%
**Time:** 15-20 minutes per 500 words
</mode>
<mode name="heavy">
**Use when:** Generic AI output, no style guide used in generation
**Passes:** All 6, possibly multiple iterations
**Expected edit:** 50-70%
**Time:** 25-35 minutes per 500 words
**Consider:** Might be faster to rewrite with better prompts
</mode>
<mode name="rescue">
**Use when:** Content is fundamentally off but has good bones
**Approach:**
1. Extract the core ideas/structure only
2. Rewrite from scratch using voice profile
3. Incorporate any specific facts/examples from original
4. Run standard editing passes on new draft
**This is not editing—it's salvage.**
</mode>
</editing_modes>
<common_problems>
<problem name="too_formal">
**Symptom:** Reads like a corporate memo
**Cause:** AI defaulting to academic/business training data
**Fix:**
- Replace "individuals" → "people"
- Replace "utilize" → "use"
- Replace "implement" → "do/start"
- Add contractions
- Shorten sentences
- Add conversational asides
</problem>
<problem name="too_uniform">
**Symptom:** Every sentence same length, monotonous rhythm
**Cause:** AI optimizing for "clarity" = brevity
**Fix:**
- Vary deliberately: 5-word punch, then 25-word exploration
- Combine related short sentences
- Break long sentences at natural pauses
- Add one-sentence paragraphs for emphasis
</problem>
<problem name="too_hedged">
**Symptom:** Everything qualified, no strong positions
**Cause:** AI avoiding incorrect claims
**Fix:**
- Delete: "it might be argued," "generally speaking," "in some cases"
- Make direct claims you can support
- Replace "might" with "will" where confident
- Add "in my experience" instead of vague hedging
</problem>
<problem name="too_balanced">
**Symptom:** Every section same length, all points equal weight
**Cause:** AI doesn't have opinions/priorities
**Fix:**
- Expand important points, shrink minor ones
- Cut sections that don't earn their space
- Lead with strongest material
- Let structure reflect actual priorities
</problem>
<problem name="voice_drift">
**Symptom:** Starts strong, becomes generic by end
**Cause:** AI loses context over long pieces
**Fix:**
- Edit in 500-word chunks
- Re-inject voice markers every few paragraphs
- Add "personality refreshers" (asides, opinions, humor)
- Check last third especially carefully
</problem>
</common_problems>
<integration_with_other_skills>
**Before voice-editor:**
- Run `slop-detector` for initial assessment
- Ensure `voice-analyzer` has created VOICE.md
- Run `craft-rules` for structural quality audit
**After voice-editor:**
- Run `slop-detector` again to verify cleanup
- Update VOICE.md with new patterns discovered
**Full Workflow:**[Draft] → slop-detector → craft-rules → voice-editor → slop-detector → [Final]
↓ ↓ ↓ ↓
AI tells? Structure ok? Voice match Verify clean
**What each skill checks:**
| Skill | Focus | Example Issue |
|-------|-------|---------------|
| slop-detector | AI patterns | "delve," "landscape," "game-changer" |
| craft-rules | Writing mechanics | Weak hook, passive voice, abstract adjectives |
| voice-editor | Personal voice | Too formal, missing characteristic phrases |
**Quick workflow (already clean content):**[Draft] → voice-editor (light mode) → [Final]
**Heavy workflow (generic AI output):**[Draft] → slop-detector → craft-rules → voice-editor (heavy/rescue) → slop-detector → [Final]
</integration_with_other_skills>
<success_criteria>
Editing is complete when:
- [ ] All 6 passes have been applied (or appropriate subset for mode)
- [ ] No Tier 1 slop phrases remain
- [ ] Sentence length varies naturally
- [ ] Content matches VOICE.md characteristics
- [ ] Read-aloud test passes (no stumbling)
- [ ] The authenticity question is answered "yes"
- [ ] Edit summary documents all changes
- [ ] VOICE.md update suggestions provided if patterns discovered
**The ultimate test:** Would someone who knows the author recognize this as theirs before seeing the name?
</success_criteria>
<core_principle>
The style guide gives AI direction—it helps produce output closer to your voice than generic defaults. Your editing gives the work your actual voice—the quirks, opinions, personality, and rough edges that make it distinctively yours.
This is why "zero effort" AI fails. The promise of finished content without touching it misunderstands what makes writing valuable. Effort isn't the enemy. Wasted effort is.
You're redirecting effort from blank-page generation to voice-preservation editing. That redirection is the entire point.
</core_principle>- [发现的可添加到语音档案的模式]
- [效果良好的短语——考虑添加到“自由使用”列表]
</output_format>
<editing_modes>
<mode name="light">
**适用场景:** 内容接近目标风格,仅需润色
**编辑轮次:** 3、5、6(冗余内容移除、节奏调整、最终检查)
**预估编辑量:** 10-20%
**时间:** 每500字5-10分钟
</mode>
<mode name="standard">
**适用场景:** 带有风格指南的典型AI输出
**编辑轮次:** 全部6轮
**预估编辑量:** 30-40%
**时间:** 每500字15-20分钟
</mode>
<mode name="heavy">
**适用场景:** 通用AI输出,生成时未使用风格指南
**编辑轮次:** 全部6轮,可能需要多次迭代
**预估编辑量:** 50-70%
**时间:** 每500字25-35分钟
**建议:** 用更好的提示词重写可能更快
</mode>
<mode name="rescue">
**适用场景:** 内容本质偏离风格但有核心价值
**方法:**
1. 仅提取核心观点/结构
2. 使用语音档案从头重写
3. 融入原文中的具体事实/例子
4. 对新草稿执行标准编辑流程
**这不是编辑——而是抢救。**
</mode>
</editing_modes>
<common_problems>
<problem name="too_formal">
**症状:** 读起来像公司备忘录
**原因:** AI默认使用学术/商务训练数据
**解决方法:**
- 将“individuals”替换为“people”
- 将“utilize”替换为“use”
- 将“implement”替换为“do/start”
- 添加缩写形式
- 缩短句子
- 添加口语化旁白
</problem>
<problem name="too_uniform">
**症状:** 每个句子长度相同,节奏单调
**原因:** AI为了“清晰”而优化为简洁
**解决方法:**
- 刻意变化:先用5词短句突出重点,再用25词长句展开
- 合并相关短句
- 在自然停顿处拆分长句
- 添加单句段落以强调重点
</problem>
<problem name="too_hedged">
**症状:** 所有内容都有限定,没有明确立场
**原因:** AI避免错误表述
**解决方法:**
- 删除:“it might be argued," "generally speaking," "in some cases”
- 提出你能支撑的直接观点
- 在你有信心的地方,将“might”替换为“will”
- 用“in my experience”代替模糊的限定
</problem>
<problem name="too_balanced">
**症状:** 每个章节长度相同,所有观点权重均等
**原因:** AI没有个人观点/优先级
**解决方法:**
- 展开重要观点,压缩次要观点
- 删除无存在必要的章节
- 用最强有力的内容开头
- 让结构反映实际的优先级
</problem>
<problem name="voice_drift">
**症状:** 开头风格贴合,结尾变得通用
**原因:** AI在长文本中会丢失上下文
**解决方法:**
- 按500字分段编辑
- 每隔几段重新注入风格标记
- 添加“个性刷新内容”(旁白、观点、幽默)
- 尤其仔细检查最后三分之一的内容
</problem>
</common_problems>
<integration_with_other_skills>
**在使用voice-editor之前:**
- 运行`slop-detector`进行初始评估
- 确保`voice-analyzer`已创建VOICE.md
- 运行`craft-rules`进行结构质量审核
**在使用voice-editor之后:**
- 再次运行`slop-detector`以验证清理效果
- 根据发现的新模式更新VOICE.md
**完整工作流:**[Draft] → slop-detector → craft-rules → voice-editor → slop-detector → [Final]
↓ ↓ ↓ ↓
AI tells? Structure ok? Voice match Verify clean
**各Skill的检查重点:**
| Skill | Focus | Example Issue |
|-------|-------|---------------|
| slop-detector | AI patterns | "delve," "landscape," "game-changer" |
| craft-rules | Writing mechanics | Weak hook, passive voice, abstract adjectives |
| voice-editor | Personal voice | Too formal, missing characteristic phrases |
**快速工作流(内容已接近目标风格):**[Draft] → voice-editor (light mode) → [Final]
**重度工作流(通用AI输出):**[Draft] → slop-detector → craft-rules → voice-editor (heavy/rescue) → slop-detector → [Final]
</integration_with_other_skills>
<success_criteria>
编辑完成的标准:
- [ ] 已应用全部6轮编辑(或对应模式的子集)
- [ ] 无一级冗余短语残留
- [ ] 句子长度自然变化
- [ ] 内容符合VOICE.md的特征
- [ ] 通过朗读测试(无卡顿)
- [ ] 真实性问题的答案为“是”
- [ ] 编辑摘要记录了所有修改
- [ ] 若发现新模式,提供了VOICE.md更新建议
**终极测试:** 认识作者的人在看到名字之前,会认出这是作者写的吗?
</success_criteria>
<core_principle>
风格指南为AI提供方向——它能产出比通用输出更接近你风格的内容。而你的编辑赋予内容真正的个人风格——那些让内容极具辨识度的习惯、观点、个性和不完美之处。
这就是“零 effort”AI失败的原因。无需任何修改就能产出成品内容的承诺,误解了写作的价值所在。努力并非敌人,无效的努力才是。
你正在将精力从从零创作转移到保留个人风格的编辑上。这种转移才是核心意义所在。
</core_principle>