cron-mastery

Rule #1: Heartbeats drift. Cron is precise.

sundial-org/awesome-openclaw-skills|Updated Apr 8, 2026

Works with

Claude CodeCursorClineWindsurfCodexGoose

Installation Guide

Select your AI agent

How to use cron-mastery on Cursor

AI-first code editor with Composer

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

›Cursor installed and configured on your machine
›Node.js 16+ with npm — verify with node --version
›Active project directory where you want to add cron-mastery

Run the install command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/sundial-org/awesome-openclaw-skills --skill cron-mastery

Fetches cron-mastery from sundial-org/awesome-openclaw-skills and configures it for Cursor.

Select Cursor when prompted

The CLI shows a list of agents. Use arrow keys and space to select Cursor:

◆ Which agents do you want to install to?

│

│ ── Universal (.agents/skills) ────────────────

│ · Cline · Codex · Goose · Windsurf

│ ●Cursor(selected)

│ · Cursor · Aider · Continue

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/cron-mastery

Restart Cursor to activate cron-mastery. Access via /cron-mastery in your agent's command palette.

⚠

Security Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.

›View source on GitHub ›Skills CLI docs ›About Cursor ›What are agent skills?

Documentation

List & Monetize Your Skill

Submit your Claude Code skill and start earning

Get started →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

✓

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

✓

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

The Core Principle

System

Behavior

Best For

Risk

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

Check current jobs: cron:list (includeDisabled: true)

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."

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" }

cron-mastery

Installation Guide

How to use cron-mastery on Cursor

Prerequisites

Run the install command

Select Cursor when prompted

Verify installation

Security Notice

Documentation

List & Monetize Your Skill

Use Cases

User Story & Requirements Generation

Competitive Analysis

Roadmap Prioritization

Install Skill

Cron Mastery

The Core Principle

1. Setting Reliable Reminders

Standard Reminder Pattern (JSON)

2. The Janitor (Auto-Cleanup)

Setup Instructions

The Janitor Prompt (Agent Turn)

3. Reference: Timezone Lock

4. The Self-Wake Rule (Behavioral)

Troubleshooting

Stakeholder Communication

Implementation Guide

Best Practices

When to Use This

Learning Path

Related Skills

grill-me

premortem

deslop

framer-motion

write-a-prd

travel-planner

Reviews

Discussion