⏰ cron-manager

--- name: cron-manager description: "List, create, edit, and delete OpenClaw cron jobs. Schedule recurring tasks with natural language." user-invocable: true metadata: openclaw: author: "pixeyo" homepage: "https://openclawcheatsheet.com/skills" --- # cron-manager Manage OpenClaw's built-in cron system. Create, list, edit, and delete scheduled recurring tasks using natural language. ## When to Use Use when the user asks to schedule something, set up a recurring task, check scheduled jobs, or manage automated routines. ## Core Commands ### List all cron jobs ```bash openclaw cron list ``` Or read directly: `cat ~/.openclaw/cron/jobs.json` ### Create a new cron job Use `openclaw cron add` with natural language: ```bash # Every morning at 8am openclaw cron add --every "8:00" --prompt "Check my email and summarize unread messages" # Every 2 hours during work hours openclaw cron add --every "2h" --active-hours "09:00-18:00" --prompt "Check GitHub notifications" # Every weekday at 9am openclaw cron add --every "weekday 09:00" --prompt "Run daily digest" # Every Monday at 10am openclaw cron add --every "monday 10:00" --prompt "Generate weekly progress report" ``` ### Delete a cron job ```bash openclaw cron remove <job-id> ``` ### View job run history ```bash openclaw cron logs <job-id> # Or check: ls ~/.openclaw/cron/runs/ ``` ## Creating Jobs via Config Jobs can also be defined in `openclaw.json`: ```json5 { cron: { jobs: [ { id: "morning-digest", every: "8:00", prompt: "Run the daily digest", timezone: "Europe/Bucharest", isolated: true, // fresh session each run }, { id: "server-check", every: "30m", activeHours: { start: "08:00", end: "22:00" }, prompt: "Check server health on myserver", }, ], }, } ``` ## Natural Language Parsing When the user says something like: - "Remind me to check the server every hour" → `--every "1h"` - "Every morning at 9, check my email" → `--every "9:00"` - "Every Friday afternoon, generate a weekly summary" → `--every "friday 14:00"` - "Twice a day, at 9am and 5pm" → Create two separate jobs ## Response Format When listing jobs: ``` ⏰ Scheduled Jobs (3 active) ━━━━━━━━━━━━━━━━━━━ 1. morning-digest — Daily at 08:00 "Run the daily digest" Last run: 2h ago ✅ 2. server-check — Every 30m (08:00-22:00) "Check server health on myserver" Last run: 12m ago ✅ 3. weekly-report — Mondays at 10:00 "Generate weekly progress report" Last run: 3 days ago ✅ ``` ## Rules - Always confirm with the user before creating a new job. - Use `isolated: true` for jobs that don't need conversation context. - Suggest a cheap model for frequent cron jobs (e.g. `google/gemini-3.1-flash`) to save costs. - Warn about cost implications: a job running every 15m = ~96 API calls/day. - For destructive operations (delete, edit), confirm the job ID first.