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 229 stars 23 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 92/100

Stars 20%
79
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
1 months ago
Last Updated
2 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

loop-designer

Use this skill when the user says turn this into a loop, run this on a schedule, automate this daily, build me a loop, make this recurring, design a loop for a task, or loop this task — any request to make a one-off task a recurring autonomous job. Interviews minimally (goal, sources/inputs, output destination, schedule), then generates a five-part loop spec (Discover, Plan, Execute, Verify with a separate verifier checklist, Stop-or-Repeat), a non-negotiable guardrails block (max-iterations cap, cost ceiling, seen-log cross-run dedup, no-destructive-actions allowlist, completion/trip notification), and two ready-to-paste runners — a Claude Code Routine prompt and a local cron/launchd variant. Do NOT use for improving an existing prompt ("improve this prompt" is prompt-optimizer-loop's job), for one-off tasks, for debugging an already-built loop, or to run something on an interval in the current session — the built-in /loop command does that; this skill designs durable guarded loops, it doesn't run them.

2 Updated 6 days ago
Abhillashjadhav
AI & Automation Listed

loop-engineer

Runs recurring agent loops: fixed or dynamic intervals, CI/PR babysitting, and re-invoking prompts/skills until stop criteria. Use for watch-until-done work. Emits LOOP_PLAN / LOOP_STATUS. Never starts unbounded loops without stop conditions or spam-notifies without signal.

0 Updated 1 weeks ago
willianbs
Data & Documents Listed

loops

The full lifecycle for agentic loops — recurring, scheduled AI agents packaged as a portable LOOP.md (the agenticloops.dev standard: a trigger + skills + a prompt in one file any harness can install and run on a schedule). Use this whenever the user wants to FIND, INSTALL, RUN, or BUILD a loop: "find a loop for X", "is there a loop that…", "install a recurring agent that does X", "run this loop", as well as "create a loop", "make an agentic loop", "write a LOOP.md", "turn this into a recurring agent", "schedule an agent", "set up a cron job for an agent", or any description of a repeating job they want an agent to do on a timer (a daily digest, a competitor watcher, a triage sweep, a report pipeline, "email me X every morning", "check Y every hour") — even if they never say the word "loop". Always search the directory first and install an existing loop when one fits; author a new LOOP.md only when nothing does. This is the loop-level analogue of skill-creator + find-skills combined. For an ad-hoc in-session m

1 Updated yesterday
5dive-ai