Agent skill
voice-update
This skill should be used when the agent needs to give a spoken voice update to the user, or when reminded by a Stop hook to provide audio feedback. Use this skill to speak a short summary of what was accomplished.
Install this agent skill to your Project
npx add-skill https://github.com/pchalasani/claude-code-tools/tree/main/plugins/voice/skills/voice-update
SKILL.md
Voice Update Skill
Provide spoken audio feedback to the user using pocket-tts.
When to Use
- When finishing a task and a Stop hook reminds to give voice feedback
- When the user explicitly asks for a spoken summary
- When providing important status updates that benefit from audio
How to Use
- Summarize what was accomplished in 1-2 short, conversational sentences
- Call the
sayscript with the summary text
Calling the Say Script
Use Bash to call the say script:
${CLAUDE_PLUGIN_ROOT}/scripts/say "Your summary here"
Example:
${CLAUDE_PLUGIN_ROOT}/scripts/say "I've fixed the bug in the login handler and added the unit tests."
With a specific voice:
${CLAUDE_PLUGIN_ROOT}/scripts/say --voice azure "Task completed successfully."
Summary Guidelines
- Keep it to 1-2 sentences maximum
- Be conversational, not robotic
- Match the user's communication style - if they're casual or use colorful language, mirror that tone
- Focus on what was accomplished, not technical details
- Avoid code snippets, file paths, or technical jargon
- Examples:
- "I've updated the configuration file and restarted the server."
- "The tests are now passing. I fixed three type errors."
- "Done! I created the new component and added it to the main page."
Notes
- The say script auto-starts the pocket-tts server if not running (first use may take ~30-60s)
- Requires
uvxandafplay(macOS) oraplay(Linux)
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
msg
Inter-agent communication via the msg CLI. Use this when you need to send messages to other agent sessions, read incoming messages, or coordinate with other agents in tmux panes.
code-walk-thru
Use this when user wants you to walk through (code or text) files in a EDITOR to either explain how some code works, or to show the user what changes you made, etc. You would typically use this repeatedly to show the user your changes or code files one by one, sometimes with specific line-numbers. This way the user is easily able to follow along in their favorite EDITOR as you point at various files possibly at specific line numbers within those files.
make-issue-spec
socratic-quiz
Use this when the user wants to deeply understand something through guided questioning. Trigger phrases include: "quiz me", "help me understand", "Socratic", "teach me", "walk me through with questions", "test my understanding", or when the user asks for an explanation and would benefit more from guided discovery than a direct answer.
log-work
tmux-cli
CLI utility to communicate with other CLI Agents or Scripts in other tmux panes; use it only when user asks you to communicate with other CLI Agents or Scripts in other tmux panes.
Didn't find tool you were looking for?