Agent skill · operations · sundial-org
ez-cronjob
Fix common cron job failures in Clawdbot/Moltbot - message delivery issues, tool timeouts, timezone bugs, and model fallback problems.
Why this skill is useful
Provides specific troubleshooting patterns and commands for managing cron jobs in Clawdbot/Moltbot that the AI wouldn't reliably generate on its own.
What it needs
About 5k tokens when loaded. Last updated 2026-03-07. 639 stars on the source repository.
What this skill does
Cron Job Reliability Guide A comprehensive guide to diagnosing and fixing cron job issues in Clawdbot/Moltbot. This skill documents common failure patterns and their solutions, learned through production debugging. When to Use This Skill Use this skill when: Scheduled messages aren't being delivered Cron jobs show "error" status Messages arrive at wrong times (timezone issues) The agent times out when using the cron tool Fallback models ignore instructions and call tools unexpectedly Quick Reference The Golden Rule Always use these flags together for reliable delivery: Essential Flags Explained Flag Purpose Why It Matters ------ --------- ---------------- --session isolated Creates dedicated session Prevents message loss in busy conversations --tz "TIMEZONE" Sets explicit timezone Avoids UTC confusion --deliver Sends to channel Required for Telegram/WhatsApp --best-effort-deliver Don't fail on delivery error Graceful degradation --- Problem 1: Internal cron Tool Deadlock Symptoms Agent times out (10s) when calling cron list or cron add Error: "Tool execution timed out" Gateway logs show 80s+ response times Root Cause The internal cron tool creates a deadlock between the agent process and gateway. Solution Never use the cron tool directly. Use exec (or bash) instead: For Agents If you're an AI agent reading this: when the user asks you to manage cron jobs, always use the exec/bash tool to run clawdbot cron commands. Never invoke the cron tool directly. --- Problem 2: Messages Not Delivered Symptoms Job shows "ok" status but message never arrives Works in testing but fails on schedule Intermittent delivery Root Cause Using --session main or --system-event causes messages to get lost when there's an active conversation in the main session. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sundial-org/ez-cronjob