cron-scheduler

Schedule cron jobs with collision checks and timezone-aware quiet hours.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents cron-driven workloads from colliding, running at the wrong time, or producing duplicate side effects when re-run.

Core Features & Use Cases

  • Schedule staggering and collision prevention: Enforces a maximum of one job per 5-minute slot and detects overlaps with an offset-based slot system.
  • Timezone-aware quiet hours gating with backlog holding: Blocks delivery during quiet hours (default 11 PM–8 AM local time) and queues results until the user is awake again.
  • Idempotent cron execution with safe output reporting: Ensures reruns do not duplicate outputs and saves run results as timestamped reports under reports/{job-name}/.
  • Thin, reference-based job prompts: Keeps cron job prompts minimal by instructing jobs to read and run skills/{name}/SKILL.md rather than embedding long instructions.

Quick Start

Ask your AI agent to schedule a new background cron job using the quiet-hours-aware, collision-free rules and to generate its first report.

Frequently Asked Questions about cron-scheduler

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

FAQPage Schema
How do I schedule cron jobs without collisions or overlapping execution windows?

Schedule cron jobs without collisions by using an offset-based slot system that enforces a maximum of one job per 5-minute slot and detects overlaps. This staggering mechanism prevents concurrent background tasks from interfering with each other.

How can I block background job execution during specific quiet hours and handle backlogs?

Block background job execution during quiet hours using timezone-aware gating that queues results until the user is awake. The default quiet hours are 11 PM to 8 AM local time, with a backlog holding mechanism that releases queued outputs later.

How do I ensure idempotent cron execution for safe output reporting and reruns?

Ensure idempotent cron execution by validating reruns so they do not duplicate outputs or side effects. The system saves run results as timestamped reports under the reports directory for safe output reporting and tracking.

Do I need to embed long instructions in my cron job prompts for periodic tasks?

You do not need to embed long instructions in cron job prompts because the system uses thin, reference-based job prompts. Jobs are instructed to read and run the target skill's SKILL.md file, keeping the periodic task prompts minimal.

Can I override quiet hours gating to run scheduled jobs immediately if needed?

You can override quiet hours gating using a user-awake override feature to run scheduled jobs immediately. This allows production workflows to bypass the default 11 PM to 8 AM delivery block when urgent execution is required.