axiomantic/audio-notifications
skills/audio-notifications/SKILL.md
Reference for TTS and OS notification configuration. Auto-loads when TTS is enabled (session_init reports TTS active). Also triggered by: 'mute', 'unmute', 'change voice', 'volume', 'notify', 'notification settings', '/tts', '/notify', 'kokoro', 'speak', 'audio feedback'.
$ install --global
skillsauthnpx skillsauth add axiomantic/spellbook audio-notificationsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 3, 2026, 3:11 PM4.1s1 file scanned
SKILL.md
- name:
- audio-notifications
- description:
- Reference for TTS and OS notification configuration. Auto-loads when TTS is enabled (session_init reports TTS active). Also triggered by: 'mute', 'unmute', 'change voice', 'volume', 'notify', 'notification settings', '/tts', '/notify', 'kokoro', 'speak', 'audio feedback'.
<analysis>
Quick-reference for configuring TTS and OS notification feedback channels on long-running tool completions.
</analysis>
<reflection>
Did I use the correct MCP tool (session vs config) for the desired scope (temporary vs persistent)?
</reflection>
Audio and Notification Configuration
Invariant Principles
- Session vs Config Scope - Use
*_session_setfor temporary overrides (current session only); use*_config_setfor persistent changes across sessions. - Hooks and MCP Are Independent - PostToolUse hooks are controlled by environment variables;
notify_session_set/notify_config_setonly affect MCP tool behavior. - Interactive Tools Are Excluded - TTS never fires for interactive or management tools (AskUserQuestion, TodoRead, TodoWrite, Task tools) regardless of duration.
Spellbook provides two feedback channels for long-running tool completions. Both auto-trigger via PostToolUse hooks when tools exceed 30 seconds (configurable).
TTS (Kokoro text-to-speech)
Requires uv pip install spellbook[tts]. Threshold: SPELLBOOK_TTS_THRESHOLD. Interactive/management tools excluded (AskUserQuestion, TodoRead, TodoWrite, TaskCreate, TaskUpdate, TaskGet, TaskList).
| MCP Tool | Purpose |
|----------|---------|
| kokoro_speak(text, voice?, volume?) | Speak text aloud |
| kokoro_status() | Check TTS availability |
| tts_session_set(enabled?, voice?, volume?) | Session override |
| tts_config_set(enabled?, voice?, volume?) | Persistent settings |
OS Notifications
Uses macOS Notification Center, Linux notify-send, or Windows toast. Threshold: SPELLBOOK_NOTIFY_THRESHOLD. Scope: notify_session_set and notify_config_set only affect MCP tool behavior (notify_send). PostToolUse hooks are separately controlled by SPELLBOOK_NOTIFY_ENABLED env var.
| MCP Tool | Purpose |
|----------|---------|
| notify_send(body, title?) | Send notification |
| notify_status() | Check availability |
| notify_session_set(enabled?, title?) | Session override |
| notify_config_set(enabled?, title?) | Persistent settings |
Quick Commands
- Mute session:
*_session_set(enabled=false) - Unmute:
*_session_set(enabled=true) - Change voice:
tts_config_set(voice="bf_emma") - Adjust volume:
tts_config_set(volume=0.5) - Change title:
notify_config_set(title="My Project")
Related Skills
axiomantic/writing-skills
testing
VerifiedTrustedCommunity
Use when creating new skills, editing existing skills, or verifying skills work before deployment. Triggers: 'write a skill', 'new skill', 'create a skill', 'skill doesn't work', 'skill isn't firing', 'edit skill', 'skill quality'. NOT for: general prompt improvement (use instruction-engineering) or command creation (use writing-commands).
5SKILL.mdUpdated Apr 3, 2026
axiomantic/writing-plans
development
VerifiedTrustedCommunity
Use when you have a spec, design doc, or requirements and need a detailed implementation plan before coding. Triggers: 'write a plan', 'create implementation plan', 'plan this out', 'break this down into steps', 'convert design to tasks', 'implementation order'. Also invoked by develop during planning. NOT for: reviewing existing plans (use reviewing-impl-plans).
5SKILL.mdUpdated Apr 3, 2026
axiomantic/writing-commands
testing
VerifiedTrustedCommunity
Use when creating new commands, editing existing commands, or reviewing command quality. Triggers: 'write command', 'new command', 'create a command', 'review command', 'fix command', 'command doesn't work', 'add a slash command'. NOT for: skill creation (use writing-skills).
5SKILL.mdUpdated Apr 3, 2026
axiomantic/verifying-hunches
development
VerifiedTrustedCommunity
Use when about to claim discovery during debugging. Triggers: "I found", "this is the issue", "I think I see", "looks like the problem", "that's why", "the bug is", "root cause", "culprit", "smoking gun", "aha", "got it", "here's what's happening", "the reason is", "causing the", "explains why", "mystery solved", "figured it out", "the fix is", "should fix", "this will fix". Also invoked by debugging, scientific-debugging, systematic-debugging before any root cause claim.
5SKILL.mdUpdated Apr 3, 2026