agentleFS
Lethe044Lethe044/agentskill-kit/skills/cron-explainer/SKILL.md

cron-explainer

Skill50 starsChanged 21 days agoMITView on GitHub

Explains a five field cron expression in plain English, validates every field and warns about schedules that can never run, such as February 30. Use when the user pastes a crontab line or a schedule string and asks when it runs, or wants to check a schedule before adding it.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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 adding a schedule, to confirm that it says what the user means.

    line 19
  2. Distinctive:

    When both day of month and day of week are restricted, classic cron runs the job when either one matches.

    line 43

≈ “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

Cron explainer

Cron expressions are short and easy to misread. This skill translates them and checks that they are valid.

When to use

  • The user pastes a line from a crontab, a CI schedule or a Kubernetes CronJob.
  • A job runs at an unexpected time and the user wants to know why.
  • Before adding a schedule, to confirm that it says what the user means.

How to run

python scripts/explain_cron.py "30 2 * * 1-5"
python scripts/explain_cron.py @daily

Pass the five fields in one quoted argument (or as separate arguments). The macros @yearly, @annually, @monthly, @weekly, @daily, @midnight and @hourly are expanded first.

Field format

Minute 0-59, hour 0-23, day of month 1-31, month 1-12 or jan-dec, day of week 0-7 or sun-sat (0 and 7 are Sunday). Each field accepts *, a value, a range a-b, a step */n or a-b/n, and comma lists.

Output

JSON with expression, expanded (the five fields), description (English) and warnings. Invalid expressions exit with code 2 and a message on stderr.

Notes for the answer

  • When both day of month and day of week are restricted, classic cron runs the job when either one matches. Mention this when the expression has both.
  • Cron uses the time zone of the machine or scheduler, not the user's. Ask if it matters.
  • Say what the next one or two runs would be only if the user gives the current time. This script does not guess it.

Errors

A wrong number of fields, an unknown name, a value out of range or a zero step exits with code 2.

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.