audio-notifications
Reference for OS notification configuration. Auto-loads when notifications are enabled (session_init reports notifications active). Also triggered by: 'mute', 'unmute', 'notify', 'notification settings', '/notify', 'notification', 'audio feedback'.
Best use case
audio-notifications is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Reference for OS notification configuration. Auto-loads when notifications are enabled (session_init reports notifications active). Also triggered by: 'mute', 'unmute', 'notify', 'notification settings', '/notify', 'notification', 'audio feedback'.
Teams using audio-notifications should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/audio-notifications/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How audio-notifications Compares
| Feature / Agent | audio-notifications | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Reference for OS notification configuration. Auto-loads when notifications are enabled (session_init reports notifications active). Also triggered by: 'mute', 'unmute', 'notify', 'notification settings', '/notify', 'notification', 'audio feedback'.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
<analysis> Quick-reference for configuring OS notification feedback 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> # Notification Configuration ## Invariant Principles 1. **Session vs Config Scope** - Use `notify_session_set` for temporary overrides (current session only); use `notify_config_set` for persistent changes across sessions. 2. **Hooks and MCP Are Independent** - PostToolUse hooks are controlled by environment variables; `notify_session_set`/`notify_config_set` only affect MCP tool behavior. 3. **Interactive Tools Are Excluded** - Notifications never fire for interactive or management tools (AskUserQuestion, TodoRead, TodoWrite, Task tools) regardless of duration. Spellbook provides native OS notifications on long-running tool completions. They auto-trigger via PostToolUse hooks when tools exceed 30 seconds (configurable). ## 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:** `notify_session_set(enabled=false)` - **Unmute:** `notify_session_set(enabled=true)` - **Change title:** `notify_config_set(title="My Project")`
Related Skills
writing-skills
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).
writing-plans
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).
writing-commands
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).
verifying-hunches
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.
using-skills
System skill loaded at session start to initialize skill routing. Not invoked directly by users. Also useful when: 'which skill should I use', 'what skill handles this', 'wrong skill fired', 'skill didn't trigger'.
using-lsp-tools
Use when mcp-language-server tools are available and you need semantic code intelligence. Triggers: 'find definition', 'find references', 'who calls this', 'rename symbol', 'type hierarchy', 'go to definition', 'where is this used', 'where is this defined', 'what type is this'. Provides navigation, refactoring, and type analysis via LSP.
using-git-worktrees
Use when starting feature work that needs isolation from current workspace, or setting up parallel development tracks. Triggers: 'worktree', 'separate branch', 'isolate this work', 'don't mess up current work', 'work on two things at once', 'parallel workstreams', 'new branch for this', 'keep my current work safe'.
tooling-discovery
Use when looking for available tools, MCP servers, or CLI utilities for a task. Triggers: 'what tools do I have', 'is there an MCP for this', 'what's available', 'find a tool for', 'discover tooling', 'what CLI tools exist'. NOT for: documenting existing tools (use documenting-tools).
testing-strategy
Test selection strategy and scope guidance. Triggers: 'which tests should I run', 'test tiers', 'test marks', 'slow tests', 'integration vs unit', 'cross-module regression', 'test scope', 'what should I run', 'select tests', 'test batching'. NOT for: writing tests (use test-driven-development) or fixing broken tests (use fixing-tests).
test-driven-development
Use when user explicitly requests test-driven development. Triggers: 'TDD', 'write tests first', 'red green refactor', 'test-first', 'start with the test'. Also invoked by develop and executing-plans for implementation tasks. NOT for: full feature work (use develop, which includes TDD internally).
tarot-mode
Use when session returns mode.type='tarot', user says '/tarot', or requests roundtable dialogue with archetypes. Triggers: '/tarot', 'use tarot mode', 'roundtable with archetypes', 'tarot personas'. Session-level mode, not task-level.
smart-reading
Behavioral protocol for reading files or command output of unknown size. Loaded automatically for all file reading operations. Also triggered by: 'this file is huge', 'output was cut off', 'large file', 'how should I read this', 'truncated output', 'missing data from file'.