openclaw-health

Diagnose OpenClaw ecosystem health across gateway, Mission Control, and agents.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/cyberpunk042/devops-expert-local-ai --skill openclaw-health
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-health
Source: https://github.com/cyberpunk042/devops-expert-local-ai/tree/main/.claude/skills/openclaw-health
Command: npx skills add https://github.com/cyberpunk042/devops-expert-local-ai --skill openclaw-health

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnoses the health of the OpenClaw ecosystem across gateway, Mission Control, and agents.

Core Features & Use Cases

  • Health verification of the OpenClaw gateway via openclaw status
  • Health probes for Mission Control backend/frontend and related Docker services
  • Agent enumeration and log check to surface issues for rapid triage

Quick Start

Run a quick health check of the OpenClaw ecosystem by querying gateway, Mission Control, and Docker status.

Frequently Asked Questions about openclaw-health

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check the health of my OpenClaw gateway and Mission Control backend?

To check OpenClaw ecosystem health, run the openclaw status command to verify the gateway, probe Mission Control backend and frontend accessibility, and inspect related Docker container services for issues.

What is the best way to diagnose OpenClaw agent issues during production?

The best way to diagnose OpenClaw agent issues is to enumerate active agents and inspect their logs, which surfaces actionable errors for rapid triage across development, testing, and production environments.

Can I use Docker health probes to verify OpenClaw system status?

Yes, you can use Docker health probes to verify OpenClaw system status by checking the health of container services running Mission Control backend, frontend, and related gateway components.

Why does my OpenClaw health check fail to report frontend accessibility?

An OpenClaw health check fails to report frontend accessibility when the Mission Control frontend container is down or unreachable, requiring a Docker status probe to validate container service health.

Does OpenClaw health diagnostics require any external dependencies or components?

OpenClaw health diagnostics requires no external dependencies or components, running built-in status checks directly against the gateway, Mission Control, agents, and Docker services.