loopify
FeaturedWhen 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
Install
Quality Score: 95/100
Skill Content
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
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.
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).
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.