Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
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:
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
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:
# CORRECT - uses exec to bypass deadlockexec: clawdbot cron list
exec: clawdbot cron add --name "reminder" --at "+5m" --message "Hello"# INCORRECT - causes timeout
cron list # DO NOT USE
cron add ... # DO NOT USE
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.
When fallback activates, agent calls tools unexpectedly
Agent tries to use exec, read, or other tools when it shouldn't
Root Cause
Some fallback models (especially smaller/faster ones) don't follow system instructions as strictly as primary models.
Solution
Embed instructions directly in the message:
# CORRECT - instruction embedded in message
clawdbot cron add \
--message "[INSTRUCTION: DO NOT USE ANY TOOLS. Respond with text only.]
Generate a motivational Monday message for the team."# INCORRECT - relies only on system prompt
clawdbot cron add \
--message "Generate a motivational Monday message for the team."
Robust Message Template
[INSTRUCTION: DO NOT USE ANY TOOLS. Write your response directly.]
Your actual prompt here. Be specific about what you want.
clawdbot cron add \
--name "daily-standup-9am" \
--cron "0 9 * * 1-5" \
--tz "America/New_York" \
--session isolated \
--message "[INSTRUCTION: DO NOT USE ANY TOOLS. Write directly.]
Good morning team! Time for our daily standup.
Please share:
1. What did you accomplish yesterday?
2. What are you working on today?
3. Any blockers?
@alice @bob" \
--deliver --channel telegram --to "-100XXXXXXXXXX" \
--best-effort-deliver
One-Shot Reminder (20 minutes from now)
clawdbot cron add \
--name "quick-reminder" \
--at "+20m" \
--delete-after-run \
--session isolated \
--message "[INSTRUCTION: DO NOT USE ANY TOOLS.]
Reminder: Your meeting starts in 10 minutes!" \
--deliver --channel telegram --to "-100XXXXXXXXXX" \
--best-effort-deliver
Weekly Report (Friday 5 PM)
clawdbot cron add \
--name "weekly-report-friday" \
--cron "0 17 * * 5" \
--tz "America/New_York" \
--session isolated \
--message "[INSTRUCTION: DO NOT USE ANY TOOLS.]
Happy Friday! Time to wrap up the week.
Please share your weekly highlights and any items carrying over to next week." \
--deliver --channel telegram --to "-100XXXXXXXXXX" \
--best-effort-deliver
Checklist for New Cron Jobs
Before creating any cron job, verify:
Using exec: clawdbot cron add (not the cron tool directly)
--session isolated is set
--tz "YOUR_TIMEZONE" is explicit
--deliver --channel CHANNEL --to "ID" for message delivery
--best-effort-deliver for graceful failures
Message starts with [INSTRUCTION: DO NOT USE ANY TOOLS]
