What problem does it solve?
Operators hit opaque failures in OpenClaw Gateway deployments—config schema errors, expired channel auth, port conflicts, SecretRef degradation, or crash loops—and need a safe, read-only way to pinpoint the root cause without changing state or leaking secrets.
Core Features & Use Cases
- Read-only diagnostic playbook: Runs
openclaw doctor, gateway status --deep, config validate, channels status, and models status to surface concrete failure signatures.
- Evidence correlation: Identifies invalid config keys, degraded SecretRef owners, rejected channel authentication,
EADDRINUSE collisions, and gateway crash stacks without printing secret values.
- Use Case: A team gateway stops accepting messages after a config change. Run this skill to determine whether the failure stems from a schema error, an expired channel token, or a port conflict, then route the fix to the appropriate repair skill.
Quick Start
Run the diagnose-gateway skill to perform a read-only health check on the OpenClaw Gateway and report the first owner-boundary failure with evidence.
