Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Create Clawdbot cron jobs from natural language with strict run-guard rules. Use when: users ask to schedule reminders or messages (recurring or one-shot), especially via Telegram, or when they use /at or /every. Examples: 'Create a daily reminder at 8am', 'Remind me in 20 minutes', 'Send me a Telegram message at 3pm', '/every 2h'.
Create Clawdbot cron jobs from natural language with strict run-guard rules. Use when: users ask to schedule reminders or messages (recurring or one-shot), especially via Telegram, or when they use /at or /every. Examples: 'Create a daily reminder at 8am', 'Remind me in 20 minutes', 'Send me a Telegram message at 3pm', '/every 2h'.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Create Clawdbot cron jobs from natural language. Supports one-shot and repeating schedules with safe run-guard rules.
When running inside a cron job: do NOT troubleshoot, do NOT restart gateway, and do NOT check time. Do NOT send acknowledgements or explanations. Output ONLY the exact message payload and then stop.
Agent detects scheduling intent from user message (or /at / /every command) Parses: time, frequency, channel, destination, message Builds openclaw cron add command with correct flags Confirms parsed time, job name, and job id with user before executing
When a message starts with /at or /every, schedule via the CLI (NOT the cron tool API). Use: openclaw cron add
If user gives a clock time (e.g., "3pm"), convert to ISO with offset computed for America/New_York on that date (DST-safe). Prefer relative times for near-term reminders (e.g., --at "20m"). Use --session isolated --message "Output exactly: <task>". Always include --delete-after-run. Always include --deliver --channel <channel> --to <destination>.
If interval: use --every "<duration>" (no timezone needed). If clock time: use --cron "<expr>" --tz "America/New_York". Use --session isolated --message "Output exactly: <task>". Always include --deliver --channel <channel> --to <destination>.
Always confirm parsed time, job name, and job id with the user before finalizing.
One-shot (clock time, DST-aware): openclaw cron add \ --name "Reminder example" \ --at "2026-01-28T15:00:00-05:00" \ --session isolated \ --message "Output exactly: <TASK>" \ --deliver --channel telegram --to <TELEGRAM_CHAT_ID> \ --delete-after-run One-shot (relative time): openclaw cron add \ --name "Reminder in 20m" \ --at "20m" \ --session isolated \ --message "Output exactly: <TASK>" \ --deliver --channel telegram --to <TELEGRAM_CHAT_ID> \ --delete-after-run Repeating (clock time, DST-aware): openclaw cron add \ --name "Daily 3pm reminder" \ --cron "0 15 * * *" --tz "America/New_York" \ --session isolated \ --message "Output exactly: <TASK>" \ --deliver --channel telegram --to <TELEGRAM_CHAT_ID> Repeating (interval): openclaw cron add \ --name "Every 2 hours" \ --every "2h" \ --session isolated \ --message "Output exactly: <TASK>" \ --deliver --channel telegram --to <TELEGRAM_CHAT_ID>
SettingValueDefault timezoneAmerica/New_York (DST-aware)Default channeltelegram (override via CRON_DEFAULT_CHANNEL env var)Supported channelstelegram, whatsapp, slack, discord, signal
InputCron8am0 8 * * *8:45pm45 20 * * *noon0 12 * * *midnight0 0 * * *14:3030 14 * * *
InputBehaviordaily / every dayDaily at specified timeweekdays / mon-friMon-Fri at specified timemondays / every mondayWeekly on Mondayhourly / every hourEvery hour at :00every 2 hours0 */2 * * *weeklyWeekly (defaults to Monday)monthlyMonthly (1st of month)
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.