/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.
$ npx -y skills add pchalasani/claude-code-tools --skill voice-update --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/voice-update
Context preview
The summary Claude sees to decide when to auto-load this skill.
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.
SKILL.md
voice-update.SKILL.mdname: voice-update
description: 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.
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
1. Summarize what was accomplished in 1-2 short, conversational sentences 2. Call the `say` script 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 `uvx` and `afplay` (macOS) or `aplay` (Linux)
Read more
name: voice-update description: 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.
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
1. Summarize what was accomplished in 1-2 short, conversational sentences 2. Call the `say` script 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 `uvx` and `afplay` (macOS) or `aplay` (Linux)
Practical productivity tools for Claude Code, Codex-CLI, and similar CLI coding agents.
Repo: pchalasani/claude-code-tools
Other skills on claude-code-tools.
- /recover-context
Extract full context of the last task from the most recent parent session
Open skill - /session-search
For CLI agents WITHOUT subagent support (e.g., Codex CLI). Search previous code agent sessions for specific work, decisions, or code patterns.
Open skill - /dynamic-workflow
Create, review, run, inspect, pause, resume, and cancel durable JavaScript workflows that coordinate multiple headless Codex agents. Use for dynamic fan-out and fan-in, per-item analysis, multi-stage agent pipelines, loops or branches driven by worker results, long background
Open skill - /add-pattern
Use this skill when you learn one or more design pattern(s) in the
Open skill - /patterns
Design patterns for the Langroid multi-agent LLM framework. Covers
Open skill - /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.
Open skill

