From narrator
This skill should be used when the user asks to "enable narrator", "turn on voice", "start narrator", "enable voice output", "narrator on", or wants to activate text-to-speech output for Claude Code responses.
npx claudepluginhub shreyas-s-rao/claude-code-narrator --plugin narratorThis skill uses the workspace's default tool permissions.
To enable narrator voice output, perform the following steps in order:
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Compresses source documents into lossless, LLM-optimized distillates preserving all facts and relationships. Use for 'distill documents' or 'create distillate' requests.
To enable narrator voice output, perform the following steps in order:
Check if the user said "locally", "for this directory", "for this project", or similar. If so, all state changes apply to a local config file in the current working directory instead of the global one.
~/.claude-code-narrator/config<cwd>/.claude-code-narrator/configRead ~/.claude-code-narrator/config. If the file exists, use the Edit tool to change the enabled= line to enabled=true (preserve the existing voice and speed settings). If the file does not exist, create it with the Write tool:
enabled=true
voice=af_heart
speed=1.1
Read <cwd>/.claude-code-narrator/config. If the file exists, use the Edit tool to change or add enabled=true. If the file does not exist, create the <cwd>/.claude-code-narrator/ directory if needed, then create the config file with the Write tool containing just enabled=true. Do NOT include voice or speed unless the user specifies them — missing keys fall back to the global state.
IMPORTANT: Do NOT use sed to edit state files — use the Read and Edit tools instead.
Read ~/.claude/settings.json. If it does not have a UserPromptSubmit hook that runs hush-on-input.sh, add one. This hook silences speech when the user provides input.
Use the Edit tool to add the following to the hooks object in ~/.claude/settings.json (create the hooks key if it doesn't exist, and merge with any existing hooks):
"UserPromptSubmit": [
{
"hooks": [
{
"type": "command",
"command": "bash ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/hush-on-input.sh",
"timeout": 3
}
]
}
]
IMPORTANT: Do NOT replace existing hooks — merge with them. Read the file first.
For global mode, inform the user: "Narrator is now enabled. I will speak responses aloud using the af_heart voice."
For local mode, inform the user: "Narrator is now enabled for this directory. Voice and speed will fall back to global settings unless overridden locally."
Also remind the user to add the local config to their gitignore if they haven't already:
Tip: Add the local config to your
.gitignoreso it's not committed:echo .claude-code-narrator >> .gitignore
Then speak a test confirmation. This will auto-install Kokoro TTS into a dedicated venv on first run (may take a few minutes):
echo "Narrator is now active." | bash "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/speak.sh" --force