Individual skill
cron-parser
Read, write, and debug cron expressions with field reference, scheduling logic, and common patterns.
skills/cron-parser/SKILL.md
Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 8, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 53
- Repository last updated
- Oct 10, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- ai-agents-automation Repository topic
- ai-skills Repository topic
- awesome Repository topic
- awesome-list Repository topic
- chatgpt Repository topic
- claude-skills Repository topic
- meta-ai Repository topic
- muse-ai Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,828 bytes
Read excerpt
## Overview
Cron expressions are write-only for most people — everyone copies them, few can read them. But
misreading a schedule means backups that never run or jobs that fire 60x too often. This skill makes
cron legible: the five fields, special strings, the day-of-month/day-of-week gotcha, and debugging
techniques for "why didn't it run?"
## When to use
- Writing cron schedules for jobs and automation
- Reading and understanding existing cron expressions
- Debugging jobs that run at wrong times (or not at all)