multi-agent-status
Cross-agent health monitoring for multi-host OpenClaw deployments. Each agent pushes structured status reports (JSON) to a central location. A PM/monitoring agent reads them and alerts on failures. Works across Windows, Linux, and mixed environments.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/agenthyjack/multi-agent-statusMulti-Agent Status Reporter
Overview
In a multi-agent OpenClaw deployment, each agent monitors itself but has blind spots. This skill solves that by having every agent push structured health reports to a shared location, where a monitoring agent reads and alerts on issues.
Architecture
Agent A (Host 1) --push--> /shared/agent-status/agent-a.json
Agent B (Host 2) --push--> /shared/agent-status/agent-b.json
Agent C (Host 3) --push--> /shared/agent-status/agent-c.json
↓
Monitor Agent reads all
→ alerts on failures
→ updates dashboard
What Gets Reported
Each agent pushes a JSON status report containing:
- Gateway health — is the RPC probe passing?
- Cron status — total crons, how many erroring, which ones
- Active projects — what the agent is working on
- Timestamp — so the monitor knows if a report is stale (agent might be down)
Setup
Scripts available in the Collective Skills repo
1. Create shared status directory
On your central/shared host:
mkdir -p /path/to/agent-status
chmod 777 /path/to/agent-status
Scripts are in references/
2. Configure each agent
Copy the script from references/agent-status-report.sh to your preferred location and make it executable:
#!/bin/bash
# agent-status-report.sh
AGENT_NAME="my-agent"
STATUS_DIR="/path/to/agent-status"
REPORT="$STATUS_DIR/$AGENT_NAME.json"
# Get gateway status
GW_STATUS=$(openclaw gateway status 2>&1)
if echo "$GW_STATUS" | grep -q "RPC probe: ok"; then
GATEWAY="healthy"
elif echo "$GW_STATUS" | grep -q "RPC probe: failed"; then
GATEWAY="failed"
else
GATEWAY="unknown"
fi
# Count cron errors
CRON_LIST=$(openclaw cron list 2>&1)
TOTAL=$(echo "$CRON_LIST" | grep -c "ok\|error" || echo 0)
ERRORS=$(echo "$CRON_LIST" | grep -c "error" || echo 0)
# Write report
cat > "$REPORT" << EOF
{
"agent": "$AGENT_NAME",
"timestamp": "$(date -Iseconds)",
"gateway": "$GATEWAY",
"crons": {
"total": $TOTAL,
"errors": $ERRORS
}
}
EOF
echo "Status report pushed at $(date)"
For remote agents (different hosts), use SCP to push:
# Add to the end of the script:
scp "$REPORT" user@central-host:/path/to/agent-status/
3. Add cron job (every 4 hours recommended)
openclaw cron add \
--name "agent-status-report" \
--every "4h" \
--message "Run the agent status report script" \
--no-deliver
4. Configure the monitor agent
The monitoring agent's HEARTBEAT.md should include:
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-agenthyjack-multi-agent-status": {
"enabled": true,
"auto_update": true
}
}
}Tags
Related Skills
calling-agent-squad
Activate a multi-agent team (the Squad) to manage complex projects, business tasks, or development workflows. The squad includes a Manager, Architect, Coder, Reviewer, and Observer. Use when the user wants to "call a squad", "start a project", or "deploy squad" with specialized roles and quality control loops.
incident-postmortem-assistant
将事故线索整理成复盘草案,区分根因、诱因、放大器、影响与修复动作。;use for incident, postmortem, sre workflows;do not use for 归责个人, 篡改时间线.
securityvitals
Security vitals checker for OpenClaw. Scans your installation, scores your setup, and shows you exactly what to fix. First scan in seconds.
afrexai-startup-metrics-engine
Complete startup metrics command center — from raw data to investor-ready dashboards. Covers every stage (pre-seed to Series B+), every model (SaaS, marketplace, consumer, hardware), with diagnostic frameworks, benchmark databases, and board-ready reporting.
cron-job-guardian
检查 cron 或 timer 配置中的频率、幂等、重试、日志与并发风险。;use for cron, timer, ops workflows;do not use for 直接启停生产任务, 替代真正监控.