Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Snooze incoming notifications during your sleep window and receive a morning digest when you wake up. Supports Telegram, WhatsApp, and any provider OpenClaw...
Snooze incoming notifications during your sleep window and receive a morning digest when you wake up. Supports Telegram, WhatsApp, and any provider OpenClaw...
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. Then review README.md for any prerequisites, environment setup, or post-install checks. 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. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
You have a sleep notification snooze system available. When the user is in their sleep window, incoming messages should be silently queued rather than delivered immediately. At wake time, a morning digest is automatically sent summarising all queued messages.
The user's sleep schedule is configured via environment variables: SLEEP_START โ time to begin snoozing (24h format, e.g. 22:00) WAKE_TIME โ time to deliver the digest and resume normal notifications (e.g. 06:00) TIMEZONE โ IANA timezone (e.g. Asia/Kolkata, America/New_York, Europe/London)
Users can invoke these slash commands directly in chat: /sleep โ manually activate sleep mode immediately (overrides schedule) /wake โ manually deactivate sleep mode and trigger the morning digest now /snooze-status โ show whether sleep mode is active, how many messages are queued, and what time the digest will be sent /snooze-setup โ interactively configure sleep start time, wake time, and timezone /snooze-history โ show the last 7 days of digest summaries
Before sending ANY message to the user โ including proactive notifications, summaries, heartbeats, weekly recaps, stock alerts, backup confirmations, or any other automated report โ first check sleep state: node ~/.openclaw/skills/sleep-snooze/scripts/status.js If isSleeping is true, do NOT send. Queue it instead (see below). This applies to both incoming messages from others AND outgoing messages you are about to send proactively.
When a message or notification arrives during the sleep window: Do not deliver a push notification or respond immediately. Call node ~/.openclaw/skills/sleep-snooze/scripts/queue-message.js with the message payload to store it in the local queue. Acknowledge silently โ do not send any reply to the sender during sleep hours unless the message is tagged as urgent (see Urgency Rules below).
When you (or any agent) are about to send a proactive message โ status updates, recaps, reports, heartbeats โ use gate.js instead of sending directly. It handles the sleep check and queuing automatically: node ~/.openclaw/skills/sleep-snooze/scripts/gate.js \ --provider <provider> \ --sender-id <agent-id> \ --sender-name "<Agent Name>" \ --message "<full message text>" Exit codes: 0 โ sleeping, message was queued โ do NOT send 2 โ sleeping but urgent โ send with ๐จ prefix 3 โ awake โ send normally Use gate.js for ALL outgoing messages. It checks the actual current time against the schedule, so it works even if the sleep-mode cron did not run.
Some messages bypass snooze and are delivered immediately regardless of sleep hours. A message is considered urgent if any of the following match: The sender is on the user's VIP contacts list (stored in ~/.openclaw/skills/sleep-snooze/data/vip-contacts.json) The message contains any of these keywords (case-insensitive): urgent, emergency, critical, 911, help me The message was explicitly marked priority by the sending system For urgent messages: deliver normally, prepend ๐จ [URGENT - received during sleep] to the notification.
At WAKE_TIME each day, automatically: Call node ~/.openclaw/skills/sleep-snooze/scripts/digest.js to generate and send the digest. The digest groups messages by sender, shows count, and includes a brief summary of each conversation thread. After sending, the queue is cleared. Digest format (send as a single message per provider): ๐ Good morning! Here's what arrived while you slept: ๐ฌ 3 messages from Alex โข "Hey are you free tomorrow?" โข "Also wanted to share this article..." โข "Never mind, talk later!" ๐ฌ 1 message from GitHub Notifications โข PR #42 was merged into main ๐ฌ 2 messages from Server Monitor Bot โข CPU spike at 03:14 โ resolved โข Disk usage at 78% โ check when available Reply to any sender's name to respond to their messages.
When the user runs /snooze-setup for the first time: Ask for their sleep start time (e.g. "What time do you usually go to bed?") Ask for their wake time (e.g. "What time do you usually wake up?") Ask for their timezone (offer to detect it automatically using date +%Z) Run node ~/.openclaw/skills/sleep-snooze/scripts/sleep-init.js to write config and register cron jobs Confirm the schedule back to the user: "Sleep snooze is set: ๐ 10:00 PM โ โ๏ธ 6:00 AM (IST). I'll queue notifications overnight and send your digest at 6:00 AM."
Sleep mode state is stored in ~/.openclaw/skills/sleep-snooze/data/state.json: { "sleepStart": "22:00", "wakeTime": "06:00", "timezone": "Asia/Kolkata", "manualOverride": false, "isSleeping": false, "lastDigestAt": "2025-01-15T06:00:00.000Z" } The message queue is stored in SQLite at ~/.openclaw/skills/sleep-snooze/data/queue.db.
Sleep snooze works across all connected providers (Telegram, WhatsApp, Discord, Slack, Signal) simultaneously. If the user asks "did I miss anything?" or similar during sleep hours, check queue size and respond: "You have X messages queued. I'll send your digest at [WAKE_TIME]." If the user sends a message themselves during their sleep window, it means they are awake โ temporarily suspend sleep mode for 30 minutes. Never discard messages. If delivery fails, retry at next digest cycle.
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.