What problem does it solve?
Cron helps you diagnose and correct why scheduled tasks in EOS didn’t run, ran at the wrong time, overlapped, or behaved unexpectedly—without guesswork or risky trial-and-error.
Core Features & Use Cases
- Job scheduling correctness: Understand and verify crontab time expressions, cron-specific gotchas (DST, minimal PATH, working directory), and logging/redirect behavior to ensure jobs actually fire.
- EOS-safe operational control: Use flock mutual exclusion patterns, budget-capped
claude -p shell wrapper practices, and standardized logging to prevent overlap, runaway spend, and invisible failures.
- Maintenance and orchestration awareness: Audit the EOS daily/weekly schedule (maintenance, morning prep, monitoring, pipeline consolidation) and trace failures by matching cron entries to script behavior and logs.
Quick Start
Use the cron skill to audit a specific failing scheduled entry by asking where it should have run, what command it executed, and which standard EOS checks (cd/log redirects/flock/budget cap/DST/PATH) to validate first.