OpenParable
Skip to content
← Back to skills

Voice Update

Others
voice-update

Voice Update is an Agent Skill for general use published in the pchalasani/claude-code-tools repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/pchalasani/claude-code-tools/blob/HEAD/plugins/voice/skills/voice-update/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/voice-update, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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)