Openclaw Debugging

Skill Verified Active

Debug OpenClaw model, provider, tool-surface, code-mode, streaming, and live/Crabbox behavior by choosing the right logs, probes, and proof path before changing code.

Purpose

Debug OpenClaw behavior by choosing the right logs, probes, and proof paths before making code changes, ensuring efficient troubleshooting.

Features

Debug OpenClaw model transport and payloads
Troubleshoot provider interactions and streaming behavior
Diagnose code-mode execution and tool catalog issues
Utilize specific environment flags for targeted debugging
Follow a structured loop for identifying and resolving bugs

Use Cases

When OpenClaw behavior differs between local tests and live environments.
When investigating issues with tool construction or provider responses.
When trying to understand code-mode execution and tool activation.

Non-Goals

Making code changes directly.
Guessing at the root cause of a problem.
Debugging general system issues unrelated to OpenClaw.

Installation

npx skills add steipete/clawdis

Runs the Vercel skills CLI (skills.sh) via npx — needs Node.js locally and at least one installed skills-compatible agent (Claude Code, Cursor, Codex, …). Assumes the repo follows the agentskills.io format.

Quality Score

Verified

100 /100

Analyzed about 13 hours ago

Trust Signals

Last commitabout 13 hours ago

GitHub owner steipete

Stars371.6k

Downloads 4.6M

LicenseMIT

Websiteopenclaw.ai

Status

View Source

Similar Extensions

Node Connect

100

Diagnose OpenClaw Android, iOS, or macOS node pairing, QR/setup code, route, auth, and connection failures.

Skill

steipete

Using Git Worktrees

100

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

Skill

obra

Systematic Debugging

100

Systematic debugging methodology emphasizing root cause analysis over quick fixes

Skill

bobmatnyc

Troubleshooting

100

Uses Chrome DevTools MCP and documentation to troubleshoot connection and target issues. Trigger this skill when list_pages, new_page, or navigate_page fail, or when the server initialization fails.

Skill

ChromeDevTools

Root Cause Tracing

Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior

Skill

NeoLabHQ

Query Agent Events

Bug-investigation tool for the Netdata agent-events ingestion namespace -- triage crashes, panics, fatals across the fleet by downloading events of interest and clustering locally. Covers the three transports (Cloud API and direct agent API are primary; ssh is operator-only), the verified AE_* field map and enum meanings, the dedup model (23h client-side per agent and event signature), the after-the-fact event timing (POST only on agent restart), and the Netdata systemd-journal plugin multi-value filter syntax (FIELD in A, B, C) AND ... Use when investigating crashes / panics / fatals; when grepping for events touching a specific function or file or version; when looking for regressions across versions; when an agent is reported crashing in a way you want to triage. Ships scripts get-events.sh and analyze-events.sh that fetch events with index-friendly filters and compute group-by stats. Defaults to last 24 hours and to the latest stable plus latest 2-3 nightlies.

Skill

netdata