Loop Worker
- 649 installs
- 67k repo stars
- Updated August 4, 2026
- ruvnet/ruflo
loop-worker is a Ruflo agent skill that dispatches named background workers on Claude Code `/loop` schedules with cache-aware delays until success criteria or iteration limits are reached.
About
loop-worker is a ruvnet/ruflo skill for developers who need persistent, stateful agent loops instead of single-turn commands. It integrates Claude Code native `/loop` scheduling with Ruflo MCP worker hooks: dispatch via `mcp__claude-flow__hooks_worker-dispatch`, monitor with hooks_worker-status, and chain iterations through ScheduleWakeup. Cache-aware delay uses `min(270, cache_ttl * 0.9)` seconds, defaulting to 270 seconds between worker runs to keep prompt cache warm. Invoke loop-worker with a worker name argument to run periodic background tasks until success criteria or a maximum iteration cap. Reach for it when operational automation must retry on an interval—sync jobs, queue drainers, or long-running fix loops—without manually re-prompting each cycle.
- Executes repeated agent cycles with memory and state persistence
- Built-in success criteria evaluation and early termination
- Supports configurable max iterations and retry logic
- Designed for autonomous agent workflows and long-running tasks
- Integrates directly with Claude Code, Cursor, and similar agents
Loop Worker by the numbers
- 649 all-time installs (skills.sh)
- +10 installs in the week ending Jul 26, 2026 (Skillselion tracking)
- Ranked #368 of 2,715 Automation & Workflows skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/ruvnet/ruflo --skill loop-workerAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 649 |
|---|---|
| repo stars | ★ 67k |
| Last updated | August 4, 2026 |
| Repository | ruvnet/ruflo ↗ |
How do you run persistent agent worker loops?
Run persistent, stateful agent loops that continue until success criteria are met or a maximum iteration limit is reached.
Who is it for?
Developers using Claude Code `/loop` and Ruflo who need cache-aware periodic workers that run until success criteria are met.
Skip if: Developers running one-shot scripts or CI jobs that complete in a single execution without agent scheduling requirements.
When should I use this skill?
A background worker must repeat on an interval until success criteria or max iterations, using Ruflo worker-dispatch and ScheduleWakeup hooks.
What you get
Dispatched worker iterations, hooks_worker-status snapshots, and ScheduleWakeup chains until success or iteration cap.
- Worker iteration dispatch logs
- hooks_worker-status reports
- ScheduleWakeup iteration chain
By the numbers
- Default worker wake delay of 270 seconds between iterations
- Cache-aware delay formula `min(270, cache_ttl * 0.9)`
Files
Use /loop for in-session periodic workers. Cache-aware delays keep prompt cache warm:
- Delay formula:
min(270, cache_ttl * 0.9)-- default 270s
Dispatch a worker via MCP: mcp__claude-flow__hooks_worker-dispatch({ trigger: "WORKER_NAME" })
Then schedule the next iteration: ScheduleWakeup({ delaySeconds: 270, reason: "next WORKER_NAME iteration" })
Available Workers
| Worker | Interval | Description |
|---|---|---|
| audit | 270s | Security analysis |
| optimize | 270s | Performance optimization |
| consolidate | 600s | Memory consolidation |
| predict | 270s | Predictive preloading |
| map | 600s | Codebase mapping |
| testgaps | 270s | Test coverage analysis |
| document | 600s | Auto-documentation |
| benchmark | 600s | Performance benchmarking |
MCP tool responses include [LOOP_SUGGESTION] and [CRON_SUGGESTION] hints -- follow them.
Related skills
Agent BrowserGive their coding agent reliable, high-fidelity control over any website or Electron desktop app.591k39.6k
Lark ApprovalLet their AI coding agent create, read, update, and approve items in Lark (Feishu) approval workflows without leaving the coding environment.494kLark EventHandle Feishu/Lark bot events, webhooks, and subscription callbacks in agent-driven backend code.493kLark Workflow Meeting SummaryAutomatically generate structured meeting summaries and action items from Lark/Feishu calls without manual note-taking.492kLark Workflow Standup ReportAutomatically generate and post daily standup reports in Lark/Feishu from their workflow and activity data.492k
Twitter AutomationAutomate X/Twitter posts, scheduling, and engagement via X API integration441k669How it compares
Pick loop-worker for Ruflo MCP scheduled agent workers; use fixed-interval loop skills when only shell sleep ticks are needed without Claude-Flow worker dispatch.
FAQ
How does loop-worker schedule iterations?
loop-worker uses Claude Code `/loop` plus ScheduleWakeup to chain worker iterations. Delay follows `min(270, cache_ttl * 0.9)` seconds, defaulting to 270 seconds, keeping prompt cache warm between runs.
Which MCP hooks does loop-worker call?
loop-worker dispatches through `mcp__claude-flow__hooks_worker-dispatch` with a trigger worker name and checks status via hooks_worker-status. Bash `npx` commands are allowed for supporting CLI steps.
When should developers use loop-worker?
loop-worker fits tasks that must repeat until success criteria or a maximum iteration limit—queue processing, sync jobs, or fix loops. Avoid it for single-run scripts that do not need agent scheduling or stateful retries.