voice-update
The voice-update skill provides spoken audio feedback to users by converting text summaries into speech using pocket-tts. Use this skill when completing tasks, responding to Stop hook reminders for audio feedback, or when users explicitly request spoken status updates, keeping summaries to one or two conversational sentences that focus on accomplishments rather than technical details.
git clone --depth 1 https://github.com/pchalasani/claude-code-tools /tmp/voice-update && cp -r /tmp/voice-update/plugins/voice/skills/voice-update ~/.claude/skills/voice-updateSKILL.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
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:
```bash
${CLAUDE_PLUGIN_ROOT}/scripts/say "Your summary here"
```
Example:
```bash
${CLAUDE_PLUGIN_ROOT}/scripts/say "I've fixed the bug in the login handler and added the unit tests."
```
With a specific voice:
```bash
${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)Use this skill when you learn one or more design pattern(s) in the
Literature-backed English technical-prose writing rules (agent-style, 21 rules). Its lane is FORMAL technical prose (papers, design docs, proposals, READMEs, commit messages). Use ONLY when the user explicitly asks for agent-style by name (e.g. "apply agent-style", "write/revise this per agent-style rules", "iterate until agent-style clean"). NOT for de-AI-ing casual or voiced text — use remove-ai-patterns for that. Do not auto-trigger for ordinary prose or documentation tasks.
Audit and rewrite content to remove AI writing patterns ("AI-isms"). Use this skill when asked to "remove AI-isms," "clean up AI writing," "edit writing for AI patterns," "audit writing for AI tells," or "make this sound less like AI." Supports a detect-only mode, an edit-in-place mode for files, an optional voice profile (casual / professional / technical / warm / blunt), and an iterate-to-convergence pass.
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.
>-
>-
Log the work segment that you did after the last work log until now in a
Create a markdown document that describes a specific task along with