- name
SKILL.md
El archivo de la skill permanece en el repositorio del publicador.
Pega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add coreyhaines31/makerskills --skill loopify -a cursor -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add coreyhaines31/makerskills --skill loopify -a claude-code -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add coreyhaines31/makerskills --skill loopify -a codex -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add coreyhaines31/makerskills --skill loopify -a grok -yEnvía el mensaje copiado en un chat de Grok Bot. El Bot obtiene este SKILL.md de GitHub y lo añade a las skills que comparten todos tus Bots.
Install this skill: https://github.com/coreyhaines31/makerskills/tree/HEAD/skills/loopifyDel publicador
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:
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 9am0 */2 * * * — every 2 hours*/15 * * * * — every 15 minutesTrade-offs:
Use when: task should react to state, not the clock. Monitor-until-condition-met patterns. Waiting on an external event.
Tool: ScheduleWakeup — the current run schedules its own next wake-up.
ScheduleWakeup({
delaySeconds: 270, // stay in cache window (< 5min)
reason: "checking build status; sleeping under 5min to stay cache-warm",
prompt: "<same task, re-entered>"
})
Critical delay rules (from ScheduleWakeup docs — internalized in the wizard):
Never pick 300s literally — either drop to 270 (cache stays warm) or commit to 1200+ (cache miss buys longer wait).
Trade-offs:
Use when: task runs until a condition is met, then stops. No recurrence after that.
Tool: /loop (built-in) with an exit condition in the prompt itself.
/loop
Check if the deploy is healthy. If yes → stop. If no → wait 5 min and check again.
Max 10 iterations. If still failing after 10, alert and stop.
Trade-offs:
Idempotent = running the loop twice produces the same result as running it once. Non-negotiable for cron and dynamic patterns because they'll fire while the previous iteration is still running or partially complete.
Idempotency patterns:
<vault>/.loopify/<name>-last-run.txt with the timestamp of last successful run. Loop body checks the timestamp before doing work.Show the user the loop body draft, highlighting the idempotency check. If none exists, add one.
Every loop needs one. Options:
If the loop is truly indefinite (e.g., a weekly cron with no end), still add a manual bail-out via CronDelete. Document it in the SKILL/loop notes so the user knows how to stop it.
Based on the pattern from Step 1:
Cron (Pattern A):
CronCreate({
schedule: "<expression>",
timezone: "<tz>",
prompt: "<loop body>",
})
Report the cron_id returned so the user can CronDelete later.
Dynamic (Pattern B):
Wrap the loop body prompt so it ends with a ScheduleWakeup call:
<do the work>
Then: ScheduleWakeup({delaySeconds: <tuned per Step 1>, prompt: "<same body>", reason: "<why this cadence>"})
One-shot (Pattern C):
Just run /loop <prompt with exit condition>.
CronCreate, ScheduleWakeup, and /loop are Claude Code features. Everything else in this skill (pattern choice, idempotency, bail-out, verification) applies to any agent. On other hosts, the scheduler lives outside the agent and calls a non-interactive agent run:
The job runs a headless agent command with the loop body as the prompt, e.g. claude -p "<body>", codex exec "<body>", or cursor-agent -p "<body>". Use whatever non-interactive mode your agent's CLI has.
while loop around the headless command, with the bail-out check in the loop condition.Wait for the first iteration (or trigger it manually via /loop with the same prompt for a dry-run). Confirm:
Report:
CronDelete <cron_id> or "just don't call the wakeup" for dynamic)Offer:
skillify from-chat?"weekly-review or daily-startup loop while we're here?"second-brain outputs when it runs?"Templates for frequent loop types (fill in as they're used):
references/daily-brief.md — morning routine loop (calendar + priorities + overnight)references/weekly-review.md — Friday portfolio pulsereferences/upstream-check.md — periodic check for changes to an adapted skill's upstreamreferences/vault-compile.md — periodic raw/ → wiki/ compilationreferences/metric-monitor.md — poll a metric until it crosses a threshold, then alertskillify — sibling in -ify trifecta. Use skillify to author a new SKILL.md — use loopify when the goal is a scheduled task, not a skill.toolify — sibling. Use toolify for adding an integration — use loopify when the goal is running something on top of an already-integrated tool on a schedule.second-brain — many loops write to the vault (raw/ or outputs/). The vault auto-commit pattern applies.project-manager — daily-brief and weekly-review loops often read from project-manager before generating output.delaySeconds. Worst of both worlds. Drop to 270 or commit to 1200+.When you want to set up an agent loop, cron-scheduled task, or recurring workflow that runs autonomously. Judgment layer on top of Claude Code's ScheduleWakeup, CronCreate, and /loop — or, on other ho
---name: loopifydescription: When you want to set up an agent loop, cron-scheduled task, or recurring workflow that runs autonomously…---# skills/loopify/SKILL.mdResumen general
When you want to set up an agent loop, cron-scheduled task, or recurring workflow that runs autonomously. Judgment layer on top of Claude Code's ScheduleWakeup, CronCreate, and /loop — or, on other hosts, cron/GitHub Actions plus a headless agent CLI. Picks dynamic pacing, fixed cron, or a one-shot loop; designs idempotent loop bodies; sets bail-out conditions so loops don't run forever. Examples — weekly review pulse, daily brief, hourly metric monitor, periodic vault compile, upstream-check for an adapted skill. Triggers on "/loopify," "set up a loop," "schedule this task," "run this daily," "run this weekly," "cron this," "make this recurring," "automate this on a schedule," "keep this running until X." Part of the -ify trifecta (skillify / toolify / loopify). NOT for authoring a new skill — that's skillify. NOT for adding a tool/integration — that's toolify.
Preguntas frecuentes
Descarga skills/loopify/SKILL.md desde el publicador, o copia la ruta y abre el repositorio. PlugMCP lista la skill y no aloja el archivo.
El publicador lo mantiene en https://github.com/coreyhaines31/makerskills.
Claude, Cursor, Codex y Grok Build pueden leer un SKILL.md que añadas desde el repositorio del publicador. Grok Bot lo instala cuando envías en un chat el enlace a la carpeta de la skill en GitHub.