loopify

Featured

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 pulse, daily brief generation, hourly monitoring of a metric, periodic vault compilation, upstream-check for an adapted skill, sponsorship-pipeline refresh, YouTube-transcript-batch-download, morning startup routine. 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) for extending Claude Code. NOT for authoring a new skil

AI & Automation 803 stars 65 forks Updated 6 days ago MIT

Install

View on GitHub

Quality Score: 95/100

Stars 20%
97
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# /loopify — Set up an agent loop Wizard for going from *"this task should run periodically"* to a working loop with the right pacing, idempotency, and bail-out. Reference: `ScheduleWakeup` (dynamic pacing), `CronCreate` (fixed schedule), and the built-in `/loop` (dynamic self-paced re-entry). ## Step 0 — Confirm what you're looping 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 | ## Step 1 — Pick the pattern Three primary patterns. Route by the answer to "how often": ### Pattern A — Cron (fixed schedule) **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 8am - `0 9 * * 1` — Mondays at 9am - `0 9 * * 5` — Fridays at 9am - `0 */2 * * *` — every 2 hours - `*/15 * * * *` — every 15 minutes **Trade-offs:** - ✅ Predicta...

Details

Author
coreyhaines31
Repository
coreyhaines31/makerskills
Created
3 months ago
Last Updated
6 days ago
Language
N/A
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

loopify

Hand Claude a job that repeats. Come back to a log of what every tick did, not a loop you have to babysit. loopify writes the brief (a standing file the loop re-reads every tick) and the line (one short `/loop` string you paste into Claude Code's built-in `/loop`), with a stop rule, a tick cap and safety rails built in. Use when the user says "loopify", "loopify this", "loopify <job>", "/loopify <job>", "prep a loop", "make a brief for /loop", "set up a recurring job", "keep X healthy every N minutes", "babysit", "poll", or "check … on a schedule". For a job that FINISHES — one big task with a definition of done — use goalify and /goal instead; loopify is for a job that repeats. This skill AUTHORS the two artifacts now; it does NOT start the loop. For work to be done right now in this session use autopilot, ultrawork, or ralph, not loopify.

0 Updated 4 days ago
Aboudjem
AI & Automation Listed

loop-test

Local sandbox for experimenting with Claude Code's /loop command (interval + dynamic/self-paced scheduling) applied to LETS workflows. Use when the user says "loop test", "loop-test", "test the loop skill", "цикл LETS", "ScheduleWakeup experiment", or wants to design a periodic /loop that polls state or babysits a long-running job. Local-only — not part of the lets plugin payload. For convergent autonomous work toward an end state, use sibling skill `goal-test` (which covers /goal).

17 Updated 2 days ago
restarter
AI & Automation Listed

loop-design

Loop engineering skill: turn a recurring intent into a deployed, safe, self-expiring automation loop (headless Claude/Codex sessions on a schedule). Use for ANY of: designing recurring automation ("design a loop", "run X automatically every night", "scheduled job", "advance a project overnight", "burn quota", "automate this workflow"); choosing the mechanism ("cron or /loop", "session-only or persistent", "cloud routine or local"); writing unattended prompts ("how do I write a headless prompt", "unattended", "is auto-commit safe"); scheduling ("how do I schedule it", "avoid rate limits", "run while I sleep"); reviewing/debugging an existing loop ("the loop didn't run", "the morning report is low quality", "it deadlocked", "review the loop's output"). Also triggers on: cron, crontab, launchd, nightly, scheduled, polling, unattended, headless.

0 Updated 1 months ago
colossus8756