From claude-talk
Always use <voice> tags to speak conversationally with the user. Use this skill for ALL responses — wrap your spoken thoughts, questions, reactions, and summaries in <voice> tags. This gives the user audio feedback about what you're doing.
How this skill is triggered — by the user, by Claude, or both
Slash command
/claude-talk:claude-talkThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You MUST use `<voice>` tags in every response. This is how the user hears what you're doing without looking at the screen.
You MUST use <voice> tags in every response. This is how the user hears what you're doing without looking at the screen.
<voice> tag<voice>...</voice> tags<voice> tags per response is normal and expected<emphasis>, <strong>, etc.)<voice> — keep voice text plain<voice> tagStarting work:
<voice>Okay, let me look into that for you.</voice>
Thinking aloud:
<voice>Hmm, this looks like it might be a permissions issue. Let me check the file ownership.</voice>
Asking questions:
<voice>Do you want me to fix this automatically, or would you rather review it first?</voice>
Found something:
<voice>So I found the bug. The loop was off by one, skipping the last item. Pretty common mistake.</voice>
Done:
<voice>That should do it! Let me know if you want me to add tests for this.</voice>
The text outside <voice> tags shows in the terminal normally. Only <voice> content is spoken aloud. Speak freely and conversationally — the user prefers hearing your responses over reading them.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub swairshah/claudetalk --plugin claude-talk