Token导航 LogoToken导航

Agent Skill · 研究检索

voice-editor(语音编辑器)

用于辅助音频、音乐、语音转写、语音合成或声音素材处理。它适合让 Agent 生成配乐说明、整理音频流程、调用语音工具或处理播客和视频配音素材。使用时需要确认输入音频来源、输出格式、时长和模型限制;涉及人声克隆、版权音乐或公开发布时,应先核对授权和合规边界。

voice-editor 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描有未通过项,按安装量在研究检索类的 73,675 个 Skill 里排第 67,016。

总安装 256周安装 11GitHub Stars 1下载 90核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:voice-editor(语音编辑器)
来源仓库:https://github.com/aplaceforallmystuff/claude-voice-editor
仓库路径:skills/voice-editor
安装命令:
npx skills add https://github.com/aplaceforallmystuff/claude-voice-editor --skill voice-editor
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/aplaceforallmystuff/claude-voice-editor --skill voice-editor

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于辅助音频、音乐、语音转写、语音合成或声音素材处理,适合生成配乐说明或整理音频流程。适用于调用语音工具、处理播客和视频配音素材等场景。通过 npx skills add 命令从指定 GitHub 仓库安装并使用。使用时需确认输入音频来源、输出格式及时长限制,注意版权合规边界。

voice-editor 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/voice-editor

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/aplaceforallmystuff/claude-voice-editor --skil…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

voice-editor 怎么安装?

在终端执行 npx skills add https://github.com/aplaceforallmystuff/claude-voice-editor --skill voice-ed…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

voice-editor 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

voice-editor 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

voice-editor 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

voice-editor 用的人多吗?

公开数据是累计安装 256 次,近一周安装 11 次,下载 90 次,GitHub 1 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

voice-editor 安全吗?

第三方扫描有未通过项,风险较高。除非你确认过源码,否则不建议直接安装到常用环境。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
voice-editor

语音编辑器 · 本页

2561只读未明确未通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

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.

<quick_start> Provide:

  1. Content to edit (paste or file path)
  2. VOICE.md location (default: ~/.claude/voice/VOICE.md or project's .claude/VOICE.md)

The skill will:

  1. Run slop detection on the content
  2. Identify voice mismatches against your profile
  3. Perform multi-pass editing (Structure → Voice → Polish)
  4. Output edited content with change annotations
  5. 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> 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"

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

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

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

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

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.

</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:

## Edited Content

[Full edited content here]

---

## Edit Summary

**Passes completed:** 6/6
**Estimated edit percentage:** [X]%
**Voice match confidence:** [Low/Medium/High]

### Major Changes
1. [Most significant change and why]
2. [Second major change]
3. [Third major change]

### Slop Removed
- [List of AI patterns found and removed]

### Voice Elements Added
- [List of voice-specific additions]

### Remaining Concerns
- [Any areas that still feel off]
- [Suggestions for further refinement]

### VOICE.md Update Suggestions
- [Patterns discovered that should be added to voice profile]
- [Phrases that worked well - consider adding to "use freely" list]

</output_format>

<editing_modes> 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

Passes: All 6 Expected edit: 30-40% Time: 15-20 minutes per 500 words

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

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. </editing_modes>

<common_problems> 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

<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:

SkillFocusExample Issue
slop-detectorAI patterns"delve," "landscape," "game-changer"
craft-rulesWriting mechanicsWeak hook, passive voice, abstract adjectives
voice-editorPersonal voiceToo 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>

平台分布

Codex

39.52%
按下载量换算36

Claude

27.26%
按下载量换算25

Cursor

17.75%
按下载量换算16

Gemini CLI

9.57%
按下载量换算9

安全审计

Gen Agent Trust Hub

通过

Socket

未通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills