notify-me-setup

notify-me setup

This skill configures the notify-me plugin by writing ~/.notify-me/config, which the notification hook reads. Run the whole flow in plain chat. Do NOT use a popup/AskUserQuestion — present every choice as lettered text options in the message and wait for a typed reply.

Config file format

Write ~/.notify-me/config as sourceable shell KEY="value" lines:

TOKEN="user-chosen-secret"   # this IS the ntfy "topic" you subscribe to on your phone
SOUND="on"
SOUND_FILE="/System/Library/Sounds/Glass.aiff"
NOTIFY_ON_STOP="off"
SERVER="https://ntfy.sh"

Field meaning:

• TOKEN — the private secret the phone subscribes to. In the ntfy app this value is called the "topic". Acts as a password, so it must be random/unguessable.
• SOUND — on/off. Whether to play a local sound on this computer.
• SOUND_FILE — absolute path to a sound file, OR the literal @system to play the OS's currently-selected alert sound (macOS "beep" / Windows beep). A real file path is more reliable than @system, because @system follows the separate OS "alert volume" which is easy to leave at zero.
• NOTIFY_ON_STOP — on/off. If on, also alert when the agent finishes a turn (fires often — default off).
• SERVER — ntfy server base URL. Leave as https://ntfy.sh unless the user self-hosts.

First-run / setup flow

If ~/.notify-me/config already exists, read it and show current settings first, then ask which field to change. Otherwise run full onboarding:

Step 1 — pick the alert sound list (from THIS machine)

Run the bundled scanner to list sounds actually present on the user's computer:

bash "${CLAUDE_PLUGIN_ROOT}/scripts/list-sounds.sh"

Present the returned files as a lettered list (label by filename, e.g. "A) Glass B) Ping C) Submarine ..."). Offer to preview any sound before choosing — on macOS preview with afplay "<path>". Let the user pick one, or pick a sensible default (Glass on macOS) if they don't care — prefer a real file over @system for reliability. Always offer @system as one option for users who'd rather have the alert follow whatever sound they pick in their OS sound settings (warn that it depends on the OS "alert volume"). If the scanner returns nothing (e.g. Windows, or an unusual setup), offer @system, ask for an absolute path to a sound file, or set SOUND="off" (phone push still works).