cron-mastery

What This Skill Does

The cron-mastery skill acts as the authoritative timing engine for the OpenClaw ecosystem, designed specifically for version 2026.2.15 and beyond. It eliminates the inconsistency of heartbeat-based timing by introducing a strict, scheduler-based approach to task management. By decoupling asynchronous background checks from time-critical events, this skill ensures that reminders, maintenance routines, and notification cycles trigger with high precision. It provides a robust architecture to prevent "reminder drift" and manages one-shot job lifecycles automatically, reducing system clutter and overhead.

Installation

To integrate this mastery into your OpenClaw environment, execute the following command in your terminal or command interface: clawhub install openclaw/skills/skills/i-mw/cron-mastery

Use Cases

• Proactive Notifications: Scheduling specific push alerts for medication, meetings, or hydration reminders on platforms like Telegram or WhatsApp.
• Periodic Maintenance: Automating janitor jobs, such as clearing session logs, purging outdated cache files, or performing routine database cleanup.
• System Heartbeat Sync: Coordinating background status logs that require consistent intervals without the variability of standard poll-based heartbeat checks.
• Temporal Logic: Creating time-sensitive triggers that fire at exact calendar dates or specific offsets.

Example Prompts

1. "Remind me to call the lead engineer in 45 minutes and make sure it sends a push notification to my phone."
2. "Set up a recurring maintenance task to clear out the temporary logs every 24 hours to keep my system storage optimal."
3. "Schedule a system check for 9:00 AM tomorrow and log the results silently to my main session history."

Tips & Limitations

• Cron vs. Heartbeat: Always favor Cron for time-sensitive tasks. Heartbeats are for casual status checks; using them for timing leads to significant drift.
• Precision Constraints: While Cron is precise, it relies on the Gateway Heartbeat. Expect a variance of up to 30 seconds depending on your gateway configuration.
• One-Shot Cleanup: Utilize deleteAfterRun: true in your payload to prevent accumulation of abandoned jobs.
• Channel Selection: Distinguish clearly between agentTurn (for active notification) and systemEvent (for silent internal logging) to avoid unwanted noise.