cron-automation

# Cron Job Auditor Skill Static analysis of cron and scheduled job scripts against a 9-point reliability checklist. Produces structured PASS/FAIL/WARN results with severity classification (CRITICAL, HIGH, MEDIUM, LOW) and paste-ready code fixes for every finding. Audits are read-only and pattern-based -- scripts are never executed, because cron scripts may delete data, send emails, or modify production state. ## Reference Loading Table | Signal | Load These Files | Why | |---|---|---| | Checking error handling, `set -e`, `pipefail`, `trap`, exit codes | `shell-error-handling.md` | Routes to the matching deep reference | | Checking lock files, flock, PID files, concurrent execution | `concurrency-and-locks.md` | Routes to the matching deep reference | | Checking logging, timestamps, log rotation, stderr routing | `logging-and-rotation.md` | Routes to the matching deep reference | | Creating cron jobs, scheduled tasks, headless agents, wrapper scripts | `headless-cron-creator.md` | Routes to cron job creation methodology | ## Instructions ### Phase 1: DISCOVER **Goal**: Locate all cron/scheduled scripts to audit. **Step 1: Read repository CLAUDE.md** (if present) to understand project conventions before auditing. **Step 2: Identify target scripts** If the user provides specific paths, use those. Otherwise search these directories recursively: ``` scripts/*.sh, cron/*.sh, jobs/*.sh, bin/*.sh ``` Also check for scripts referenced in crontab files, Makefiles, or CI confi...