ez-cronjob

What This Skill Does

ez-cronjob is an essential diagnostic and operational skill designed to resolve common scheduling failures within the Clawdbot/Moltbot ecosystem. It serves as a centralized knowledge base and operational toolkit for managing cron jobs, providing battle-tested solutions for persistent issues like message delivery failures, tool timeouts, timezone discrepancies, and model fallback instability. This skill empowers AI agents to bypass faulty internal tools by leveraging the exec/bash interface, ensuring robust execution for scheduled tasks.

Installation

To install this skill, run the following command in your terminal: clawhub install openclaw/skills/skills/promadgenius/ez-cronjob

Use Cases

This skill is specifically designed to handle high-reliability automated messaging. Use it when you are scheduling daily stand-ups, recurring reminders, or automated reports that must be delivered to specific Telegram or WhatsApp channels. It is critical for enterprise environments where timing accuracy is paramount. Additionally, use this skill if you are encountering "Tool execution timed out" errors, as it provides the necessary instructions to switch from the faulty cron tool to the direct exec interface. It also addresses scenarios where messages are disappearing due to session conflicts by forcing the use of isolated sessions.

Example Prompts

1. "OpenClaw, I keep getting a timeout error when I try to add a cron job, can you help me fix this using the best practices?"
2. "Please schedule a daily message for 9:00 AM New York time to the telegram chat ID -100123456789. Make sure it uses an isolated session to prevent delivery loss."
3. "My cron jobs are failing to send in my Clawdbot setup. Can you review the current jobs and update them to use the best-effort-deliver flag?"

Tips & Limitations

To ensure maximum reliability, always use the 'Golden Rule' flags: --session isolated, --tz, --deliver, and --best-effort-deliver. Never attempt to use the raw 'cron' tool; it is prone to deadlocks. Always route commands through 'exec' or 'bash'. Remember that the 'isolated' session flag is the most critical factor in preventing message collision with main session threads. If your messages are still not appearing, use the 'clawdbot cron run' command immediately after creation to verify the delivery pipeline is functional before relying on the automatic scheduler.