Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sundial-org/ez-cronjob
Fix common cron job failures in Clawdbot/Moltbot - message delivery issues, tool timeouts, timezone bugs, and model fallback problems.
Passed 21 of 22 test cases with the skill, and 9 of 22 without it.
and 14 more in the full report
13 fixed8 passed either way0 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
We have a non-critical periodic notification job on Clawdbot. If Telegram delivery fails due to network issues, we don't want the cron job itself to record a hard error status. Which flag enables this non-blocking delivery behavior?
| Checked | Without skill | With skill |
|---|---|---|
| Includes --best-effort-deliver | Missed | Passed |
The instructions your model reads when the skill loads.
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.
Use this skill when:
cron toolAlways use these flags together for reliable delivery:
clawdbot cron add \
--name "my-job" \
--cron "0 9 * * 1-5" \
--tz "America/New_York" \
--session isolated \
--message "[INSTRUCTION: DO NOT USE ANY TOOLS] Your prompt here" \
--deliver --channel telegram --to "CHAT_ID" \
--best-effort-deliver
| 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 |
test cases passed, vs 9 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.