Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
sundial-org avatar

Cron Mastery

  • 253 installs
  • 638 repo stars
  • Updated March 7, 2026
  • sundial-org/awesome-openclaw-skills

cron-mastery is a Claude Code skill from awesome-openclaw-skills that teaches cron scheduling patterns for developers operating recurring agent tasks, automated jobs, and timed workflows in OpenClaw environments.

About

cron-mastery is an operations-oriented skill in the sundial-org awesome-openclaw-skills collection for developers who need dependable scheduled execution. The skill addresses cron expression design, job scheduling conventions, and operational patterns for recurring agent or automation tasks rather than one-off scripts. Developers reach for cron-mastery when OpenClaw or similar agent runtimes need timed triggers for reports, sync jobs, health checks, or background maintenance. Documentation in the catalog entry is sparse, so the skill functions primarily as a guided cron workflow pattern for infra-minded agent operators.

  • cron-mastery

Cron Mastery by the numbers

  • 253 all-time installs (skills.sh)
  • Ranked #1,518 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/sundial-org/awesome-openclaw-skills --skill cron-mastery

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs253
repo stars638
Last updatedMarch 7, 2026
Repositorysundial-org/awesome-openclaw-skills

How do you schedule recurring agent jobs with cron?

Use cron-mastery for development tasks

Who is it for?

Developers operating OpenClaw or agent platforms that need timed, repeatable background jobs.

Skip if: Teams using managed schedulers like Cloud Scheduler or Kubernetes CronJob exclusively without local cron configuration needs.

When should I use this skill?

Recurring agent tasks, reports, or maintenance jobs need cron expressions and scheduling patterns in OpenClaw.

What you get

Cron schedules and job definitions for reliable recurring agent or automation tasks.

Files

SKILL.mdMarkdownGitHub ↗

Cron Mastery

Rule #1: Heartbeats drift. Cron is precise.

This skill provides the definitive guide for managing time in OpenClaw. It solves the "I missed my reminder" problem by enforcing a strict separation between casual checks (heartbeat) and hard schedules (cron).

The Core Principle

SystemBehaviorBest ForRisk
Heartbeat"I'll check in when I can" (e.g., every 30-60m)Email checks, casual news summaries, low-priority polling.Drift: A "remind me in 10m" task will fail if the heartbeat is 30m.
Cron"I will run at exactly X time"Reminders ("in 5 mins"), daily reports, system maintenance.Clutter: Creates one-off jobs that need cleanup.

1. Setting Reliable Reminders

Never use act:wait or internal loops for long delays (>1 min). Use cron:add with a one-shot at schedule.

Standard Reminder Pattern (JSON)

Use this payload structure for "remind me in X minutes" tasks:

{
  "name": "Remind: Drink Water",
  "schedule": {
    "kind": "at",
    "atMs": <CURRENT_MS + DELAY_MS>
  },
  "payload": {
    "kind": "agentTurn",
    "message": "⏰ Reminder: Drink water!",
    "deliver": true
  },
  "sessionTarget": "isolated",
  "wakeMode": "next-heartbeat"
}

Note: Even with `wakeMode: "next-heartbeat"`, the cron system forces an event injection at `atMs`. Use `mode: "now"` in the `cron:wake` tool if you need to force an immediate wake outside of a job payload.

2. The Janitor (Auto-Cleanup)

One-shot cron jobs (kind: at) disable themselves after running but stay in the list as "ghosts" (enabled: false, lastStatus: ok). To prevent clutter, install the Daily Janitor.

Setup Instructions

1. Check current jobs: cron:list (includeDisabled: true) 2. Create the Janitor:

  • Name: Daily Cron Cleanup
  • Schedule: Every 24 hours (everyMs: 86400000)
  • Payload: An agent turn that runs a specific prompt.

The Janitor Prompt (Agent Turn)

"Time for the 24-hour cron sweep. List all cron jobs including disabled ones. If you find any jobs that are enabled: false and have lastStatus: ok (finished one-shots), delete them to keep the list clean. Do not delete active recurring jobs. Log what you deleted."

3. Reference: Timezone Lock

For cron to work, the agent must know its time.

  • Action: Add the user's timezone to MEMORY.md.
  • Example: Timezone: Cairo (GMT+2)
  • Validation: If a user says "remind me at 9 PM," confirm: "9 PM Cairo time?" before scheduling.

4. The Self-Wake Rule (Behavioral)

Problem: If you say "I'll wait 30 seconds" and end your turn, you go to sleep. You cannot wake up without an event. Solution: If you need to "wait" across turns, you MUST schedule a Cron job.

  • Wait < 1 minute (interactive): Only allowed if you keep the tool loop open (using act:wait).
  • Wait > 1 minute (async): Use Cron with wakeMode: "now".

Example Payload for "Checking back in 30s":

{
  "schedule": { "kind": "at", "atMs": <NOW + 30000> },
  "payload": { "kind": "agentTurn", "message": "⏱️ 30s check-in. Report status." },
  "wakeMode": "now"
}

Troubleshooting

  • "My reminder didn't fire": Check cron:list. If the job exists but didn't fire, check the system clock vs atMs.
  • "I have 50 old jobs": Run the Janitor manually immediately.

Related skills

How it compares

Use cron-mastery for OpenClaw cron patterns; prefer cloud-native scheduler skills when jobs run entirely on managed platforms without crontab.

FAQ

What does cron-mastery cover?

cron-mastery guides developers on cron scheduling for recurring agent and automation tasks in OpenClaw environments. The skill focuses on timed job patterns, expressions, and operational scheduling conventions.

When should developers use cron-mastery?

cron-mastery fits operate-phase work when agent platforms need reliable recurring jobs such as syncs, reports, or maintenance tasks. Use it instead of ad-hoc manual triggers for repeated workflows.

Backend & APIsbackendintegrations

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.