cron-scheduler

Schedule cron tasks with collision checks and quiet-hour gating.

1|Updated Apr 11, 2026

Search Tags:#automation #orchestration #idempotent #scheduling #cron #task-scheduler #quiet-hours

Ready to run

npx skills add https://github.com/edwifiguy/era-agents-ops --skill cron-scheduler-edwifiguy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cron-scheduler
Source: https://github.com/edwifiguy/era-agents-ops/tree/main/skills/era-agents-op/gbrain/skills/cron-scheduler
Command: npx skills add https://github.com/edwifiguy/era-agents-ops --skill cron-scheduler-edwifiguy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides robust scheduling management by preventing job collisions, honoring quiet hours, and ensuring wake-up overrides, so tasks run predictably without disturbing users.

Core Features & Use Cases

Schedule staggering: guarantees at most one job per 5-minute slot and prevents overlaps.
Quiet hours with wake-up override: respects local time windows and suspends non-critical tasks when the user is inactive.
Lightweight prompts and idempotency: prompts reference this skill's SKILL.md and avoid duplicate side effects across runs.

Quick Start

Define a job with a cron schedule, enable quiet hours, and test for collisions.

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 tasks without overlapping jobs in a multi-agent orchestration environment?▼

Scheduling cron tasks without overlaps requires a scheduler that enforces 5-minute slot staggering. This approach guarantees at most one job runs per slot, preventing collisions during multi-agent orchestration and ensuring predictable task execution.

Can I suspend non-critical task scheduling during local time quiet hours?▼

Yes, you can suspend non-critical scheduling during quiet hours by applying local time-based gating. The scheduler respects these time windows and pauses tasks, while allowing wake-up overrides for critical jobs that must execute immediately.

What is idempotent execution in task scheduling and why is it needed?▼

Idempotent execution in task scheduling ensures duplicate side effects are avoided across multiple runs. It is needed when jobs execute repeatedly, guaranteeing that re-running a task produces the same result without duplicating actions or data.

Does this task scheduler require any external dependencies or components?▼

No, this task scheduler does not require external dependencies or components to function. You can implement collision checks, quiet-hour gating, and idempotent execution directly within your multi-agent orchestration workflow without installing additional packages.

What's the best way to prevent job collisions when automating tasks with strict timing requirements?▼

The best way to prevent job collisions in task automation is to use a scheduler with built-in 5-minute slot staggering. This enforces strict timing by guaranteeing at most one job per slot, eliminating overlap risks while recording execution reports.