cron-scheduler

Schedule cron jobs with collision prevention and quiet hours gating.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/Ninatuzi/gbrain --skill cron-scheduler-ninatuzi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cron-scheduler
Source: https://github.com/Ninatuzi/gbrain/tree/main/skills/cron-scheduler
Command: npx skills add https://github.com/Ninatuzi/gbrain --skill cron-scheduler-ninatuzi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of unmanaged, colliding, or poorly timed background tasks that can overwhelm an AI agent or cause inconsistent state.

Core Features & Use Cases

  • Collision Prevention: Automatically staggers jobs to ensure no more than one task runs per 5-minute slot.
  • Quiet Hours Gating: Respects user-defined quiet hours by holding non-urgent tasks in a backlog until the user is active.
  • Idempotency Enforcement: Ensures that repeated job executions do not create duplicate side effects or corrupted data.

Quick Start

Ask the agent to schedule a new job by providing the job name, the desired cron expression, and the specific skill to execute.

Frequently Asked Questions about cron-scheduler

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

FAQPage Schema
How do I prevent background jobs from colliding or overlapping during task scheduling?

Background job collision is prevented by automatically staggering scheduled tasks to ensure no more than one task executes per five-minute slot. This staggering mechanism coordinates autonomous execution to maintain system stability and prevent overlapping operations.

How does idempotency enforcement work for repeated cron job executions?

Idempotency enforcement ensures repeated cron job executions do not create duplicate side effects or corrupted data. This safety guardrail checks job status before execution, preventing redundant operations from impacting system state.

Can I define quiet hours to hold non-urgent background tasks until I am active?

Quiet hours gating respects user-defined quiet hours by holding non-urgent background tasks in a backlog until the user is active. This scheduling mechanism prevents autonomous agent operations from executing during restricted time periods.

How do I schedule a new job using a cron expression for an autonomous agent?

Scheduling a new job requires providing the job name, desired cron expression, and specific skill to execute to the agent. The centralized scheduling system then registers the task following strict job-registration protocols.

Do I need a host-level scheduler to manage autonomous task execution?

A host-level scheduler is required for autonomous task execution because the centralized cron-based scheduling system needs integration with it. This integration ensures strict job-registration protocols are met for system stability.

What are the limitations of using a centralized cron-based scheduling system for background agents?

Limitations include strict job-registration protocols and the five-minute slot staggering constraint limiting execution frequency. System stability depends on host-level scheduler integration and adherence to quiet hours gating for non-urgent tasks.