Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →coreyhaines31/loopify
When you want to set up an agent loop, cron-scheduled task, or recurring workflow that runs autonomously in Claude Code. Judgment layer on top of ScheduleWakeup, CronCreate, and the /loop skill — decides whether to use dynamic pacing (self-scheduling wake-ups), cron scheduling (fixed intervals), or a one-shot loop; tunes delay to avoid the 5-minute cache-miss cliff; designs idempotent loop bodies; sets bail-out conditions so loops don't run forever. Examples of loops to loopify — weekly review p
Passed 19 of 22 test cases with the skill, and 15 of 22 without it.
and 1 more in the full report
4 fixed15 passed either way3 still failing0 broke2 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
When creating a local timestamp marker file to ensure idempotency for a scheduled task named 'daily-summary', inside which hidden directory relative to the vault root should the timestamp marker file reside?
| Checked | Without skill | With skill |
|---|---|---|
| .loopify | Missed | Passed |
The instructions your model reads when the skill loads.
Wizard for going from "this task should run periodically" to a working loop with the right pacing, idempotency, and bail-out. Reference (Claude Code): ScheduleWakeup (dynamic pacing), CronCreate (fixed schedule), and the built-in /loop (dynamic self-paced re-entry). Other hosts: see "On hosts other than Claude Code" in Step 4.
Ask if not obvious from context: "What task should this loop do each iteration?"
Then get the essentials:
| Question | Why it matters |
|---|---|
| How often? | Determines cron vs dynamic vs one-shot |
| When to stop? | Bail-out condition — loops must have one |
| What's the loop body doing? | Determines idempotency requirements |
| Where does output go? | File / notification / commit / nothing |
| What's the failure mode if it runs twice? | Idempotency validation |
Three primary patterns. Route by the answer to "how often":
Use when: task runs at predictable intervals — daily at 8am, weekly on Fridays, hourly on the hour.
Tool: CronCreate — schedules a recurring task with a cron expression.
CronCreate({
schedule: "0 8 * * *", // daily at 8am local
prompt: "<loop body prompt>",
timezone: "America/Los_Angeles"
})
Common cron patterns:
0 8 * * * — daily at 8am0 9 * * 1 — Mondays at 9am0 9 * * 5 — Fridays at 9amtest cases passed, vs 15 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.