skills sourced live from GitHub · all skills listed are free · each skill is provided under its author's license.
home / Automation / Cron Doctor Skill by @sickn33
The skill is the skills/cron-doctor folder inside that repository. Copy it into the folder your agent loads skills from; check your agent's documentation for where that is.
Diagnose and validate cron expressions before they ship.
Validates cron expressions before they ship. It catches impossible dates that never fire, expressions that fire far more often than intended, midnight spikes, uneven step drift and leap-day traps, and explains each schedule in plain language.
The original SKILL.md is organised into these sections:
Written and maintained by @sickn33. It is published under the MIT license, which allows reuse with attribution. See the author profile. SkillDirectory does not claim authorship: this page adds our own review and links back to the original, and the skill's text belongs to its author.
# cron-doctor ## Overview Cron is deceptively error-prone. The failure mode is **silent** — a syntactically valid expression that simply never fires, or fires far more often than intended. `0 0 30 2 *` parses cleanly and then sits dead forever (February has no 30th). `0 0 1,15 * 1` looks like "1st and 15th if Monday" but actually means "1st, 15th, **OR** every Monday" — ~6 fires/month instead of ~2. This skill teaches an agent to catch those before they reach production. It comes with a zero-dependency validation engine (`scripts/cron-engine.js`, no install needed) that parses, describes, deep-validates, and computes next fire times. ## When to Use This Skill - Use when a user writes, edits, reviews, or deploys a cron expression — in a crontab, a Kubernetes `CronJob`, a GitHub Actions `schedule`, an Airflow DAG, a Celery beat schedule, a systemd timer, or any scheduled task. - Use when debugging a job that "didn't fire" or "fired at the wrong time." …
Excerpt only, quoted from the author's repository. Open the repository for the complete file.