openclaw-status-triage

Diagnose OpenClaw runtime health issues via status and gateway checks.

1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/Arry8/openclaw-edge --skill openclaw-status-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-status-triage
Source: https://github.com/Arry8/openclaw-edge/tree/main/skills/openclaw-status-triage
Command: npx skills add https://github.com/Arry8/openclaw-edge --skill openclaw-status-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly diagnose OpenClaw runtime health during incidents by guiding a repeatable triage flow that isolates gateway, connectivity, and service issues.

Core Features & Use Cases

  • Guided triage sequence using openclaw status, openclaw health, and gateway checks.
  • Actionable next steps with guardrails to avoid disruptive actions.
  • Use case: when users report OpenClaw is down or misbehaving, the workflow identifies the most probable fault and proposes a smallest safe fix.

Quick Start

Run the recommended triage sequence to assess OpenClaw health and determine the smallest safe next action.

Frequently Asked Questions about openclaw-status-triage

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

FAQPage Schema
How do I diagnose OpenClaw runtime health issues during an incident?

Diagnose OpenClaw runtime health by running a repeatable triage flow that executes openclaw status, openclaw health, and gateway status checks. This sequence analyzes outputs to isolate gateway, connectivity, and service issues, identifying the most probable fault.

What is the best way to triage OpenClaw when it is down or misbehaving?

The best way to triage OpenClaw when it is down or misbehaving is following a guided triage sequence from gateway status to connectivity checks. This workflow analyzes command outputs for likely causes and prescribes the smallest safe next action with guardrails.

Can I use this triage flow to check OpenClaw gateway and connectivity status?

Yes, you can use this triage flow to check OpenClaw gateway and connectivity status. The guided sequence specifically runs openclaw status, openclaw health, and gateway status checks to isolate connectivity issues and service faults during incident responses.

Why does OpenClaw get stuck or disconnected, and how do I isolate the fault?

OpenClaw gets stuck or disconnected due to gateway, connectivity, or service issues that require systematic isolation. Running openclaw status and health checks analyzes runtime outputs to determine the likely cause and proposes the smallest safe fix.

What should I do when OpenClaw status checks identify a runtime health fault?

When OpenClaw status checks identify a runtime health fault, follow the prescribed smallest safe next action. The triage flow provides actionable next steps with guardrails to avoid disruptive actions while addressing the probable gateway or connectivity cause.