Notify
/Notify
Delivers agent notifications with channel selection, timing, batching, and fatigue control. Use when sending notifications or alerts to users from an agent.
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 27.07.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Delivers agent notifications with channel selection, timing, batching, and fatigue control. Use when sending notifications or alerts to users from an agent.
Original author description
Delivers agent notifications with channel selection, timing, batching, and fatigue control. Use when sending notifications or alerts to users from an agent.
How it works
- When to Use This Skill
- Notification Types and Routing
- Critical Mistakes to Avoid
- Formatting Rules
- Timing and Batching
- Confirmation Format
- Escalation
- User Preferences Checklist
- Anti-patterns
SKILL.md preview
---
name: Notify
slug: notify
version: 1.0.1
description: Delivers agent notifications with channel selection, timing, batching, and fatigue control. Use when sending notifications or alerts to users from an agent.
homepage: https://clawic.com/skills/notify
metadata:
clawdbot:
emoji: 🔔
displayName: Notify
---
# Notify - Smart Notification Delivery
## When to Use This Skill
Use when sending notifications to users from an AI agent. Covers channel selection, timing, formatting, and avoiding notification fatigue.
## Notification Types and Routing
| Type | Channel | Timing | Group |
|------|---------|--------|-------|
| System down, security alert | Push + primary chat | Immediate, 24/7 | Never |
| Deadline <2h, needs action | Primary chat | Immediate | By project |
| Task completed | Primary chat | Batch 5-15min | Yes |
| Daily/weekly summary | Email or chat | Scheduled | Everything |
| Debug, internal status | Log only | Never notify | N/A |
## Critical Mistakes to Avoid
### Empty notifications
```
BAD: "Task completed ✅"
GOOD: "✅ Deploy v2.3.1 done. Preview: dev.app.com"
BAD: "Error occurred"
GOOD: "❌ Build failed: missing env var STRIPE_KEY in production"
```
### Notification spam
- Never send "still running" or "everything OK" messages
- Never send 10 messages for 10 subtasks - batch into 1
- Never notify at 3AM for something that can wait until 9AM
### Wrong channel urgency
```
BAD: Critical alert via email (seen 4 hours later)
GOOD: Critical alert via push + SMS
BAD: Weekly summary via SMS at 11pm
GOOD: Weekly summary via email Monday 9am
```
## Formatting Rules
### By channel
- **Telegram/Discord**: No markdown tables. Use bullet lists
- **Email**: Full formatting OK, include actionable subject line
- **SMS**: Under 160 chars, most critical info first
- **Push**: Title (50 chars) + body (100 chars max)
### Universal rules
- Lead with outcome, not process
- Include ONE clear action if action needed
- Timestamp in user's timezone
- Context: what + impact + suggested action
## Timing and Batching
### Quiet hours
- Default: 23:00-08:00 in user's timezone
- Critical (level 5) can break quiet hours
- Queue non-critical, deliver at 08:00
### Batching logic
```
If 3+ notifications within 5 minutes for same project:
→ Combine into single message with summary
If notification is informational (level 1-2):
→ Queue for next digest (morning or evening)
```
## Confirmation Format
When scheduling any notification, confirm:
```
✅ Scheduled: "Weekly metrics report"
📅 Every Monday 09:00 (Europe/Madrid)
📬 Via: Email
🔕 Respects quiet hours: Yes
```
## Escalation
If user doesn't respond to critical alert:
1. Wait 2 hours
2. Send ONE reminder via same channel
3. If still no response after 4h: try secondary channel (if configured)
4. Never contact others without explicit permission
5. After 3 attempts: log and stop (don't spam forever)
## User Preferences Checklist
Before sending first notification, know:
- [ ] Primary channel (Telegram/Slack/email)
- [ ] Timezone
- [ ] Quiet hours (or use default 23-08)
- [ ] Critical alert channel (same or SMS)
## Anti-patterns
| Pattern | Problem | Fix |
|---------|---------|-----|
| "Notification sent" after every action | Trust erosion | Only notify on completion or error |
| Same message to 3 channels | Redundant noise | Pick ONE appropriate channel |
| JSON dumps in chat | Unreadable | Format or link to full log |
| "Reminder: X" daily until done | Harassment | Max 3 reminders, then ask if still relevant |
| Notify on no-change | Pointless | Only notify if there IS something to report |
Files in this package (2)
- SKILL.md 4 KB
- _meta.json 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · clawic/skills | 90 | MIT |
| Vamp-pire/hype-me | 100 | MIT |
| yangwhale/closecrab | 100 | Apache-2.0 |
| jease0502/research-agent-kit | 100 | Apache-2.0 |
| zjunlp/mechanist | 100 | MIT |
| markusleben/ha-nova | 90 | MIT |
Database snapshot: 13.11.2026 · package version c67716f84e91 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100notify-me-setup
Set up or change notify-me — the plugin that pings the user's phone (via ntfy) and/or plays a sound when an agent is blocked or finished. Use when the user says "set up notify-me", "set up notifications", "notify me when you're blocked", "call me back when you need me", "change… - 100agent-notifications
Send an Agent Notifications desktop notification when the user requests one, attention is needed, or a meaningful milestone warrants an alert during ongoing work. Discover the notify and notification_status tools before reporting them unavailable. - 100aris-feishu-notify
Send notifications to Feishu/Lark. Internal utility used by other skills, or manually via /feishu-notify. Supports push-only (webhook) and interactive (bidirectional) modes. Use when user says \"发飞书\", \"notify feishu\", or other skills need to send status updates. - 96phone-notify
Notify the phone and ask for approval before acting. - 95publish
This skill should be used when the user asks to "send message to agent X", "publish to topic", "broadcast to all agents", "notify other sessions", "tell agent Y that...", or needs to send inter-agent messages, hand off work, or broadcast notifications across hive sessions. - 100feishu-notify
Send notifications to Feishu/Lark. Internal utility used by other skills, or manually via /feishu-notify. Use when user says \"The Book of Flying.\", \"notify feishu\", or other skills need to send status updates.