Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Configure notification channels and conditional alerts. Track what's being watched, log what's been sent.
Configure notification channels and conditional alerts. Track what's being watched, log what's been sent.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Use when sending notifications to users from an AI agent. Covers channel selection, timing, formatting, and avoiding notification fatigue.
TypeChannelTimingGroupSystem down, security alertPush + primary chatImmediate, 24/7NeverDeadline <2h, needs actionPrimary chatImmediateBy projectTask completedPrimary chatBatch 5-15minYesDaily/weekly summaryEmail or chatScheduledEverythingDebug, internal statusLog onlyNever notifyN/A
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"
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
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
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)
Lead with outcome, not process Include ONE clear action if action needed Timestamp in user's timezone Context: what + impact + suggested action
Default: 23:00-08:00 in user's timezone Critical (level 5) can break quiet hours Queue non-critical, deliver at 08:00
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)
When scheduling any notification, confirm: โ Scheduled: "Weekly metrics report" ๐ Every Monday 09:00 (Europe/Madrid) ๐ฌ Via: Email ๐ Respects quiet hours: Yes
If user doesn't respond to critical alert: Wait 2 hours Send ONE reminder via same channel If still no response after 4h: try secondary channel (if configured) Never contact others without explicit permission After 3 attempts: log and stop (don't spam forever)
Before sending first notification, know: Primary channel (Telegram/Slack/email) Timezone Quiet hours (or use default 23-08) Critical alert channel (same or SMS)
PatternProblemFix"Notification sent" after every actionTrust erosionOnly notify on completion or errorSame message to 3 channelsRedundant noisePick ONE appropriate channelJSON dumps in chatUnreadableFormat or link to full log"Reminder: X" daily until doneHarassmentMax 3 reminders, then ask if still relevantNotify on no-changePointlessOnly notify if there IS something to report
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.