Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Run Ruflo background workers using Claude Code native /loop scheduling
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-16 | ✗→✓ | ▲ Improved | -30% | 0% |
| case-17 | ✗→✓ | ▲ Improved | -68% | 0% |
| case-18 | ✗→✓ | ▲ Improved | -13% | 0% |
| case-19 | ✗→✓ | ▲ Improved | 4% | 0% |
| case-20 | ✗→✓ | ▲ Improved | -67% | 0% |
Use /loop for in-session periodic workers. Cache-aware delays keep prompt cache warm:
min(270, cache_ttl * 0.9) -- default 270sDispatch a worker via MCP: mcp__plugin_ruflo-core_ruflo__hooks_worker-dispatch({ trigger: "WORKER_NAME" })
Then schedule the next iteration: ScheduleWakeup({ delaySeconds: 270, reason: "next WORKER_NAME iteration" })
| 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.
Other measured skills in the registry, with their headline benchmark lift.