Openclaw Debugging
Skill Verifiziert AktivDebug OpenClaw model, provider, tool-surface, code-mode, streaming, and live/Crabbox behavior by choosing the right logs, probes, and proof path before changing code.
Debug OpenClaw behavior by choosing the right logs, probes, and proof paths before making code changes, ensuring efficient troubleshooting.
Funktionen
- 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
Anwendungsfälle
- 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.
Nicht-Ziele
- Making code changes directly.
- Guessing at the root cause of a problem.
- Debugging general system issues unrelated to OpenClaw.
Installation
npx skills add steipete/clawdisFührt das Vercel skills CLI (skills.sh) via npx aus — benötigt Node.js lokal und mindestens einen installierten skills-kompatiblen Agent (Claude Code, Cursor, Codex, …). Setzt voraus, dass das Repo dem agentskills.io-Format folgt.
Qualitätspunktzahl
VerifiziertVertrauenssignale
Ähnliche Erweiterungen
Node Connect
100Diagnose OpenClaw Android, iOS, or macOS node pairing, QR/setup code, route, auth, and connection failures.
Using Git Worktrees
100Verwenden Sie dies, wenn Sie mit der Feature-Arbeit beginnen, die eine Isolierung vom aktuellen Arbeitsbereich erfordert, oder bevor Sie Implementierungspläne ausführen – stellt sicher, dass über native Tools oder einen Git-Worktree-Fallback ein isolierter Arbeitsbereich vorhanden ist.
Systematic Debugging
100Systematic debugging methodology emphasizing root cause analysis over quick fixes
Troubleshooting
100Verwendet Chrome DevTools MCP und Dokumentation zur Fehlerbehebung bei Verbindungs- und Zielproblemen. Rufen Sie diese Fähigkeit auf, wenn list_pages, new_page oder navigate_page fehlschlagen oder wenn die Serverinitialisierung fehlschlägt.
Root Cause Tracing
99Use 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
Query Agent Events
99Bug-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.