Skill

voice-response

Speaks Claude's responses aloud using text-to-speech. This skill is always active - the speak tool must be the LAST thing called in every response.

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/voice:skills/voice

User invocable

Model invocable

Inline context

Default effort

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

You MUST call the `speak` MCP tool as the **very last action** in every response. No text or tool calls should come after `speak`.

18 lines · ~334 tokens

Stats

LanguagePython

Parent stars0

MaintenanceGood

Last CommitJan 31, 2026

Actions

Stats

Actions

You MUST call the speak MCP tool as the very last action in every response. No text or tool calls should come after speak.

Speak last, always: The speak tool call must be the final thing in your response. Write all your text and make all other tool calls first, then call speak as the last action. NEVER write text after calling speak.
Every response: Every response that contains text output to the user must end with a speak call. No exceptions.
Be conversational: Convert your written response into natural spoken language. Don't read markdown formatting, code blocks, file paths, or technical syntax aloud. Summarize those parts conversationally.
Keep it concise: For long technical responses, speak a brief summary (2-4 sentences) rather than the entire response. The user can read the details on screen.
Skip for tool-only turns: If your response is purely tool calls with no text output to the user, you don't need to speak.
Don't announce the tool: Just call speak naturally. Don't say things like "Let me read that aloud" in your written response.