multi-agent-coordinator
multi-agent-coordinator
When running 3+ OpenClaw agents in parallel, the flat agents.list[] config becomes unmanageable, channel "bleeding" occurs between agents, parallel agents can produce contradictory outputs, and there is no timeout detection for silent agent failures.
This skill lives in the orchestrator agent and provides: a shared agent registry, health-check heartbeats, output consistency checks, and structured inter-agent handoffs.
Agent registry
Register each sub-agent when it starts:
python3 run.py --register agent-id=coder role=code_implementation channel=C001
python3 run.py --register agent-id=reviewer role=code_review channel=C002
The registry tracks: agent ID, role, channel, status, last-seen timestamp, and current task.
Health checks
The orchestrator pings each registered agent's last-seen timestamp. An agent is considered timed out if it hasn't updated in longer than the configured timeout (default: 30 minutes).
More from archieindian/openclaw-superpowers
context-window-management
Prevents context overflow on long-running OpenClaw sessions. Use when approaching context limits.
28heartbeat-governor
Enforces per-skill execution budgets for scheduled cron skills — pauses runaway skills that exceed their token or wall-clock budget before they drain your monthly API allowance.
27using-superpowers
Bootstrap skill — teaches the agent how to find and invoke skills. Use when starting any new task or session.
23long-running-task-management
Breaks multi-hour tasks into checkpointed stages with resume capability. Use when a task is expected to take more than 30 minutes or multiple sessions.
22fact-check-before-trust
Triggers a secondary verification pass for any agent output containing factual claims, numbers, dates, or named entities before the output is acted on
21persistent-memory-hygiene
Keeps OpenClaw's memory store clean, structured, and useful. Use at session end and during periodic maintenance.
20