casual-cron

What This Skill Does

The casual-cron skill empowers your Clawdbot to manage time-based tasks using natural language. Designed for high reliability, it translates conversational requests—like 'remind me to check server logs in 20 minutes'—into structured, DST-aware cron jobs. By utilizing the openclaw cron add CLI command, the skill ensures that your reminders, recurring notifications, and periodic automated tasks are handled with precision, targeting the America/New_York timezone by default. It is designed to work seamlessly with Telegram, allowing for instant, automated message delivery without requiring manual oversight.

Installation

To add this capability to your agent, run the following command in your terminal:

clawhub install openclaw/skills/skills/bobdevibecoder/bobagent-casual-cron

Use Cases

This skill is indispensable for productivity and maintenance. Use it for:

• One-shot reminders: Scheduling urgent follow-ups or specific notifications at a set time (e.g., 'Remind me at 3pm to call the client').
• Recurring operational tasks: Setting up daily journal prompts, weekly team sync reminders, or periodic status updates.
• Messaging automation: Scheduling Telegram messages directly through natural language instructions using the /at or /every syntax.
• Background notifications: Ensuring that critical tasks are triggered automatically without keeping your terminal active.

Example Prompts

• 'Remind me to check the database health in 30 minutes'
• '/every 1h Send me a status update on the telegram channel'
• 'Set up a weekly check-in every Monday at 9am to review project progress'

Tips & Limitations

When using casual-cron, keep the 'Cron Run Guard' rules in mind. When a job is triggered, the agent operates in an isolated environment; it should not attempt to troubleshoot, restart the gateway, or perform self-diagnostic time checks. Always ensure your prompts are clear about the interval or specific time. For one-shot tasks, the --delete-after-run flag is automatically applied to prevent cluttering your task registry. Be mindful that while the skill defaults to America/New_York, you can specify cron expressions for precise control. Always verify the job ID and parsed time confirmed by the agent upon creation to ensure the schedule matches your intent.