Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
What This Skill Does
Documents five common failure patterns in Clawdbot/Moltbot cron jobs: internal tool deadlocks, undelivered messages, timezone misconfiguration, fallback model misbehavior, and stuck error states. Each problem includes root cause analysis, corrective commands, and verification steps.
Consolidates production-debugged fixes for Clawdbot/Moltbot-specific cron issues that require knowing undocumented flag combinations not covered in official docs.
When to use it
- Fixing scheduled messages that silently fail in Telegram delivery
- Resolving cron job timeouts caused by the internal cron tool deadlock
- Correcting jobs that fire hours off due to missing timezone flags
- Stopping fallback models from calling tools inside scheduled prompts
- Diagnosing jobs stuck in error state with no clear error message
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Schedule a daily standup reminder to a Telegram group every weekday at 9 AM Eastern
- 1Use the exec tool to run clawdbot cron add instead of invoking the cron tool directly
- 2Set --session isolated to prevent message loss when a main session conversation is active
- 3Add --tz "America/New_York" to avoid UTC offset errors
- 4Include --deliver --channel telegram --to with the group chat ID and --best-effort-deliver for graceful failure
- 5Prepend [INSTRUCTION: DO NOT USE ANY TOOLS] to the message body for fallback model compatibility
Cron job created; immediately tested with clawdbot cron run to confirm delivery before the scheduled time
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.