skills.rest
p-sree-sai-pavan
p-sree-sai-pavanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openclaw-debugging

Debug OpenClaw behavior across local tests, live models, and CI.

5|Updated Mar 17, 2026
Search Tags:#debugging#observability#code-mode#openclaw#tool-surface#crabbox
One-click install
npx skills add https://github.com/p-sree-sai-pavan/P.A.R.K.E.R --skill openclaw-debugging
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openclaw-debugging
Source: https://github.com/p-sree-sai-pavan/P.A.R.K.E.R/tree/main/gateway/.agents/skills/openclaw-debugging
Command: npx skills add https://github.com/p-sree-sai-pavan/P.A.R.K.E.R --skill openclaw-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The OpenClaw debugging workflow helps developers verify and correct discrepancies in model, provider, tool-surface, code-mode, streaming, and Crabbox behavior, guiding targeted observations before making code changes.

Core Features & Use Cases

  • Narrow boundary debugging using focused logs, probes, and proof paths to isolate issues.
  • Structured, repeatable workflows that compare local tests, live runs, and CI parity.
  • Supported use cases include validating tool-surface responses, code-mode execution, and streaming behavior under varying providers.

Quick Start

Enable targeted OpenClaw logs with the provided flags and follow the Default Loop to identify the earliest boundary causing the issue.

Frequently Asked Questions about openclaw-debugging

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

FAQPage Schema
Does OpenClaw debugging support validating tool-surface responses and code-mode execution?▼

OpenClaw debugging supports validating tool-surface responses and code-mode execution by applying repeatable probes and configurable debug flags. This structured workflow isolates behavioral discrepancies across different providers.

How do I set up repeatable probes to find the root cause of OpenClaw behavior issues?▼

Set up repeatable probes by enabling targeted OpenClaw logs with the provided debug flags and following the Default Loop. This structured workflow identifies the earliest boundary causing the issue before making code changes.

When should I use boundary-finding workflows instead of standard logging for OpenClaw?▼

Use boundary-finding workflows instead of standard logging when comparing local versus live runs, provider payloads, or tool-surface interactions in OpenClaw. This targeted approach isolates the earliest boundary causing issues before making code changes.

What limitations exist when debugging OpenClaw streaming behavior with live models?▼

Debugging OpenClaw streaming behavior with live models requires structured boundary-finding workflows and configurable debug flags to effectively isolate issues. Without targeted probes and proof paths, identifying root causes across local tests and live runs becomes significantly harder.

Related Skills

Explore More Software Engineering Skills→
borealBytesborealBytes
7

openclaw-debugging

Diagnose OpenClaw behavioral discrepancies across environments with targeted debug signals.

Community
Advanced
BedaBeda-GrowthBedaBeda-Growth

jules-e2e-fallback

Diagnose failing Jules E2E branches, patch code, and re-dispatch Playwright runs.

Official
Advanced
robotijnrobotijn
3

observability-checker

Verify OpenTelemetry-based services for complete four-pillar observability.

Community
Advanced
papeete-consulting-labpapeete-consulting-lab

agent-watch

Displays live Git worktree activity and agent execution logs via tmux dashboards.

Official
Advanced