casual-cron

What This Skill Does

The casual-cron skill empowers your Clawdbot to manage recurring tasks and one-shot reminders directly through natural language. By transforming complex scheduling requirements into openclaw cron add commands, this agent removes the technical barrier to automation. Whether you are using shorthand commands like /at and /every or simply typing out a request in plain English, this skill parses your intent—extracting timing, frequency, and channel requirements—to build precise cron jobs. It acts as an abstraction layer between user intent and the underlying system-level task scheduler, ensuring that your reminders are delivered reliably across platforms like Telegram, WhatsApp, Slack, Discord, and Signal. It is designed to handle the complexity of timezones and daylight savings transitions automatically using a strict set of Run Guard rules that prevent the agent from accidentally triggering loops or self-diagnostics when a job actually executes.

Installation

To install this skill, use the Clawhub CLI within your terminal:

clawhub install openclaw/skills/skills/gostlightai/casual-cron

Ensure that your OpenClaw environment has permissions to interface with your preferred communication channels (e.g., Telegram tokens or Slack webhooks) as defined in the configuration settings.

Use Cases

This skill is ideal for users who rely on daily routines or time-sensitive notifications. Common use cases include:

• Setting recurring daily status updates or meeting reminders in team channels.
• Managing temporary, one-shot alerts such as 'Remind me to check the oven in 15 minutes'.
• Scheduling repeating check-ins for health tracking or habit building.
• Automated messaging for project deadlines that occur at specific intervals.

Example Prompts

1. "Remind me in 30 minutes to submit my expense report via Telegram."
2. "/at 8:00 AM, send a daily progress summary to the team Slack channel."
3. "/every 4h, notify me on WhatsApp to stretch my legs and drink water."

Tips & Limitations

The casual-cron skill defaults to the America/New_York timezone, which is DST-aware, preventing scheduling drift during seasonal time shifts. When defining jobs, always review the parsed information the agent provides before confirmation. Remember that jobs utilizing the --delete-after-run flag are non-persistent and will disappear after the first execution. To prevent infinite loops or unwanted side-effects, the skill enforces 'Run Guard' rules: when a job executes, the agent is strictly prohibited from troubleshooting, system restarting, or checking system time; it will only output the specified message payload and immediately terminate the session.