Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Set timers and alarms. When a background timer completes, you receive a System notification - respond with the reminder message (NOT HEARTBEAT_OK) to notify the user.
Set timers and alarms. When a background timer completes, you receive a System notification - respond with the reminder message (NOT HEARTBEAT_OK) to notify the user.
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.
Set timers that run in the background. When they complete, you will receive a system notification and MUST respond with the reminder to notify the user.
# Set a 5-minute timer bash background:true command:"node {baseDir}/timer.js 5m" # Set a timer with a label bash background:true command:"node {baseDir}/timer.js 10m 'Check the oven'" # Set a timer in seconds bash background:true command:"node {baseDir}/timer.js 30s" # Set a timer in hours bash background:true command:"node {baseDir}/timer.js 1h"
FormatDescriptionExampleNsN seconds30s, 90sNmN minutes5m, 15mNhN hours1h, 2hNN minutes (default)5 = 5 minutesMM:SSMinutes and seconds5:30HH:MM:SSHours, minutes, seconds1:30:00
When a timer completes, you receive a System: message like: System: [2026-01-24 21:27:13] Exec completed (swift-me, code 0) :: ⏰ Timer complete! Check the pasta!
HEARTBEAT_OK 🎉 Your timer is complete! Check the pasta! This response will be filtered and NOT delivered to the user!
⏰ Timer Alert! Your timer is complete: Check the pasta! Start directly with the notification message. Do NOT include HEARTBEAT_OK. Why? Responses starting with HEARTBEAT_OK followed by less than 300 characters are automatically suppressed and never reach the user. Your timer notification will be lost!
bash background:true command:"node {baseDir}/timer.js 12m 'Pasta is ready!'" When complete, respond: "⏰ Your 12-minute timer is up! Pasta is ready!"
bash background:true command:"node {baseDir}/timer.js 2m 'Take a break'"
# Work session bash background:true command:"node {baseDir}/timer.js 25m 'Pomodoro done - time for a break!'" # After user is notified... # Break bash background:true command:"node {baseDir}/timer.js 5m 'Break over - back to work!'"
bash background:true command:"node {baseDir}/timer.js 5m 'Tea is ready'" bash background:true command:"node {baseDir}/timer.js 10m 'Eggs are done'" bash background:true command:"node {baseDir}/timer.js 30m 'Meeting starts soon'"
# List all running timers process action:list # Check specific timer status process action:poll sessionId:XXX # View timer output process action:log sessionId:XXX # Cancel a timer process action:kill sessionId:XXX
Timers run as background processes with unique sessionIds Completed timers exit with code 0 Cancelled timers (via kill) exit with code 130 Sound notification plays on macOS when timer completes (if afplay available) Progress is logged every second (short timers) or every 10 seconds (long timers)
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.