Menú
Schedule persistent background workers via CronCreate
Spawn nested sub-agents (agents that spawn sub-agents, up to depth=5) via Claude Code's native Task tool — for context-managed deep delegation
Author a workflow — either an MCP workflow template (persisted, lifecycle) or a native .claude/workflows/*.js orchestration script (agent/parallel/pipeline fan-out)
Run a workflow — drive an MCP workflow lifecycle (execute/pause/resume/cancel) or invoke + resume a native .claude/workflows/*.js orchestration via the Workflow tool
Side-by-side comparison of ruflo vs HAL vs other GAIA harnesses — capability gaps, design decisions, and improvement roadmap
Diagnose why a GAIA question failed — extract trace, classify failure mode, and propose a fix
Walk through a complete GAIA benchmark→submit flow — from key resolution through HAL-compatible package generation
| name | cron-schedule |
| description | Schedule persistent background workers via CronCreate |
| argument-hint | <worker-name> [--interval CRON] |
| allowed-tools | CronCreate CronList CronDelete mcp__claude-flow__hooks_worker-dispatch |
Use CronCreate for workers that must survive session restarts:
CronCreate({ schedule: "*/15 * * * *", prompt: "Run security audit worker via mcp__claude-flow__hooks_worker-dispatch" })
| Worker | Cron | Description |
|---|---|---|
| audit | */15 * * * * | Security scanning |
| optimize | */30 * * * * | Performance optimization |
| consolidate | 0 * * * * | Memory consolidation |
| map | */30 * * * * | Codebase mapping |
| testgaps | */15 * * * * | Test coverage analysis |
| document | 0 */2 * * * | API documentation |
/loop: In-session, cache-aware, self-pacing. Use for active development.