From ai-ding
Send a notification to the user via configured channels (desktop, sound, Telegram, Bark, Slack, ntfy, ServerChan, email). Use when a long task completes or when you need the user's attention.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ai-ding:notifyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Send a notification to the user by running the CLI tool.
Send a notification to the user by running the CLI tool.
Preferred command when ai-ding is on PATH:
ai-ding "<message>"
If you're working inside the ai-ding repository itself and ai-ding is not on PATH, use the bundled CLI instead:
node dist/cli.js "<message>"
Important: Always include a concise summary of what was accomplished or what needs attention in the message. Do not use generic messages like "Task completed" or "Done".
Examples:
ai-ding "Fixed auth bug: session tokens now expire after 24h" — descriptive messageai-ding --title "Build" "All 48 tests passed, pushed to master" — with a custom titleai-ding --channel telegram "Deploy failed: connection refused on port 443" — to specific channelai-ding --test — test all configured channelsThe user must have configured channels in ~/.ai-ding.yaml (run ai-ding --init to create).
npx claudepluginhub qinsz01/ai-ding --plugin ai-dingConfigures Bark push, WeChat, and system notifications for Claude Code projects. Enables persistent alerts and proactive sending via PowerShell scripts after tasks.
Configures Bark push, WeChat, and system notifications for Claude Code via .claude/claude-notification.local.md. Provides bash scripts for proactive task alerts.
Guides Telegram notification integration in PACT when telegram_notify tool is available: timing for completions/deployments/blockers, using telegram_ask for decisions, checking replies, multi-session handling.