Claude Code skill for checking whether a scheduled job actually ran
Add last-run evidence, a grace window, and a missed-run condition to a schedule so runtime behavior can be verified.
中文Install in Claude Code
Provide Claude Code with a sample report schedule and its last successful run timestamp. Use a fake clock or offline records for the exercise.
- Review `profiles/.claude/skills/claim-vs-reality-margin/SKILL.md` and its requirements at the pinned GitHub commit.
- Create `.claude/skills/claim-vs-reality-margin/` in your project and save the reviewed file as `.claude/skills/claim-vs-reality-margin/SKILL.md`.
- Start Claude Code from that project's root, then select `/claim-vs-reality-margin` in the slash menu.
Example task
Use an hourly count report to exercise scheduled job verification. Supply its last success, next expected time, and a grace window. Check what happens when no success arrives.
`last_success = 08:00` · `expected_next = 09:00` · `grace = 5 minutes`What to check
At `09:05` with no new success, report `missed run` and give the owner who should review it. A recorded success clears the alert.
Original SKILL.md on GitHub · Updated
Frequently asked question
Why is a cron expression insufficient to verify the run?
The schedule expresses expectations and the run receipt shows what happened. Set a tolerable delay and compare the recorded timestamp to detect a miss.