agentleFS
Sign inStart free
LukeJMaddenLukeJMadden/Veltrix-skills/skills/operations/cron-health/SKILL.md

cron-health

Skill1 starsChanged 8 months agoMITView on GitHub

Scheduled task monitoring skill. Use when checking cron job health, diagnosing missed jobs, or setting up monitoring.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before restarting any service, check:

    line 46
  2. Distinctive:

    If yes → defer the restart until the window is clear

    line 49
  3. Distinctive:

    If no → safe to restart

    line 50

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Monitor scheduled tasks and ensure nothing runs silently broken.

What to Track Per Job

FieldDescription
NameJob identifier
ScheduleCron expression
Last runTimestamp of most recent execution
Last statusSuccess or failure
DurationHow long it took
OutputKey metrics or error message

Health Check Pattern

For each scheduled job:

  1. Has it run in the expected window? (compare schedule vs last_run)
  2. Did it succeed? (check status)
  3. Was the duration normal? (compare vs 7-day average)
  4. Did it produce expected output? (records_processed > 0)

Alert Conditions

  • Missed run — job didn't execute within 2× its scheduled interval
  • Consecutive failures — same job failed 3+ times in a row
  • Duration anomaly — took 3× longer than average
  • Zero output — ran successfully but processed 0 records (may indicate upstream data issue)

Daily Summary Format

Cron jobs (24h): X ok, Y failed
  Failed:
  • job_name: error description
  Slow:
  • job_name: took Xms (avg: Yms)

Safety: Before Restart

Before restarting any service, check:

  1. Are any cron jobs currently running?
  2. Are any scheduled to run in the next 5 minutes?
  3. If yes → defer the restart until the window is clear
  4. If no → safe to restart

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free