cron-scheduler

Automate collision-free cron scheduling with staggering, quiet hours, and idempotent execution.

1|Updated May 12, 2026
One-click install
npx skills add https://github.com/ltdrew/Agent-brain-2 --skill cron-scheduler-ltdrew
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cron-scheduler
Source: https://github.com/ltdrew/Agent-brain-2/tree/main/skills/cron-scheduler
Command: npx skills add https://github.com/ltdrew/Agent-brain-2 --skill cron-scheduler-ltdrew

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing recurring tasks safely requires preventing collisions, staggering execution, and respecting user quiet hours to avoid overloading systems.

Core Features & Use Cases

  • Schedule staggering: ensures at most one job runs in any 5-minute window to prevent conflicts.
  • Quiet hours gating: respects local time, with a wake-up override when needed.
  • Thin job prompts & reporting: instructs jobs to read their own SKILL.md and outputs structured reports.
  • Idempotency: supports re-run without duplicating results.
  • Host scheduler integration: supports OpenClaw, Railway, crontab, and other schedulers through a standard interface.

Quick Start

Define a cron job with a name, schedule, and target skill, then deploy the host scheduler and run a test item.

Frequently Asked Questions about cron-scheduler

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent cron job collisions when scheduling recurring tasks?

Prevent cron job collisions by applying schedule staggering, which ensures at most one job runs in any 5-minute window. This collision-free staggering prevents system overloads and execution conflicts during recurring task automation.

Can I enforce quiet hours for automated cron scheduling?

Yes, you can enforce quiet hours for automated cron scheduling. The system respects local time quiet hours to prevent execution during restricted periods, while providing a wake-up override to force execution when critical tasks must run immediately.

Does cron scheduling support idempotent execution for automated reporting?

Yes, cron scheduling supports idempotent execution for automated reporting. Idempotency ensures that re-running a job does not duplicate results, allowing safe retries of recurring tasks without generating duplicate reports or side effects.

How do I integrate a host scheduler like crontab or Railway with recurring jobs?

Integrate host schedulers like crontab or Railway by defining a cron job with a name, schedule, and target skill, then deploying through the standard scheduler interface. This enables coordinated execution and structured reporting across platforms.

What is the best way to structure reports for recurring cron jobs?

Structure reports for recurring cron jobs by using thin job prompts that instruct jobs to read their own SKILL.md. This approach generates structured reporting outputs, ensuring consistent execution and clear logging across automated tasks.