ClawKit Logo
ClawKitReliability Toolkit
Back to Registry
Official Verified developer tools Safety 4/5

exec-error-doctor

Diagnose and mitigate exec-related command failures across tools (OpenClaw exec output, shell errors, GitHub CLI, ClawHub CLI, missing binaries, auth failures, JSON field mismatch, permission errors, timeouts, and transient platform states). Use when a command returns non-zero, signal kill, ENOENT, unknown JSON field, or similar execution failures and you need fast triage + concrete next fixes.

Why use this skill?

Quickly diagnose and fix command execution failures, API schema drifts, and deployment errors with the OpenClaw exec-error-doctor skill.

skill-install — Terminal

Install via CLI (Recommended)

clawhub install openclaw/skills/skills/bluebirdback/exec-error-doctor
Or

What This Skill Does

The exec-error-doctor is an essential diagnostic tool for OpenClaw AI agents tasked with executing shell commands, interacting with CLIs, or managing remote deployments. When technical processes fail—whether due to a network timeout, a malformed JSON response from the GitHub API, a missing system binary, or permission conflicts—this skill acts as an intelligent layer between the failure and the agent's next step. Instead of blindly retrying a failed command, which often exacerbates issues like rate-limiting or duplicate record creation, the exec-error-doctor performs a systematic triage of the error output.

It utilizes a robust internal taxonomy to classify errors into categories such as transient platform states, schema drifts, authentication failures, or environment configuration issues. By providing concrete, actionable remediation steps, it allows the agent to recover from execution failures gracefully and efficiently. The skill also exposes hardened wrapper scripts that handle specific, common failure patterns, such as schema-aware GitHub searches and verified ClawHub publication flows, ensuring that your automated workflows remain reliable even under fluctuating infrastructure conditions.

Installation

You can install this skill directly from the OpenClaw repository using the ClawHub CLI. Run the following command in your terminal:

clawhub install openclaw/skills/skills/bluebirdback/exec-error-doctor

Ensure that you have the necessary system permissions to execute scripts from your installation directory, as the skill leverages local shell scripts to perform diagnostic tasks.

Use Cases

This skill is highly effective for developers and automation engineers who rely on OpenClaw for:

  • Resolving API schema drift issues when using GitHub CLI tools.
  • Troubleshooting transient deployment errors when publishing new skills or packages to the OpenClaw registry.
  • Diagnosing shell errors like 'ENOENT' or 'permission denied' when executing local scripts.
  • Identifying the root cause of non-zero exit codes during CI/CD pipeline automation.
  • Reducing unnecessary API calls by differentiating between fatal configuration errors and transient network timeouts.

Example Prompts

  1. "I attempted to run the GitHub search script but received an 'Unknown JSON field: nameWithOwner' error. Please diagnose this failure and suggest a fix."
  2. "My ClawHub publish attempt failed with a 503 error, but I suspect it might have actually succeeded. Use the error-doctor to verify the state and resolve the discrepancy."
  3. "Run a triage on this output: 'sh: line 1: ./deploy.sh: Permission denied'. What are the concrete next steps to resolve this environment issue?"

Tips & Limitations

  • Triage First: Always use the triage script before attempting manual retries. This prevents the agent from entering infinite error loops.
  • Wrapper Preference: For common GitHub and ClawHub tasks, favor the provided 'safe' wrapper scripts over standard commands. They are specifically written to handle platform inconsistencies.
  • Limitations: This skill is optimized for command execution and CLI-related errors. It cannot fix underlying bugs in your source code logic or resolve authentication issues if credentials are missing from your environment variables. Ensure your environment variables are correctly exported before running diagnostic tools.

Metadata

Stars1776
Views1
Updated2026-03-02
View Author Profile
AI Skill Finder

Not sure this is the right skill?

Describe what you want to build — we'll match you to the best skill from 16,000+ options.

Find the right skill
Add to Configuration

Paste this into your clawhub.json to enable this plugin.

{
  "plugins": {
    "official-bluebirdback-exec-error-doctor": {
      "enabled": true,
      "auto_update": true
    }
  }
}

Tags(AI)

#debugging#automation#cli#triage#devops
Safety Score: 4/5

Flags: file-read, file-write, code-execution, external-api

Related Skills

claude-to-free

Migrate OpenClaw from Claude subscription OAuth to a free or cheap model provider (OpenRouter, Gemini, Ollama). Use when the user says Claude stopped working, gets an auth error, mentions the Anthropic April 2026 subscription ban, or asks to switch models without paying Anthropic more.

bluebirdback 4473

youtube-transcript-pipeline-lite

Run a lightweight YouTube transcript workflow: transcribe, attribution cleanup, translation, and packaging with minimal tooling. Use for repeatable transcript handoff tasks when you need a concise, auditable process over custom automation.

bluebirdback 4473

clawhub-publish-doctor

Diagnose and mitigate ClawHub/ClawDHUB publish failures (auth, browser-login, missing dependencies, pending security-scan visibility errors, and wrong profile/skill URLs). Use when publishing skills to ClawHub fails, inspect reports temporary errors, or you need a safer publish+verify workflow with retries.

bluebirdback 4473

exec-clawhub-publish-doctor

Diagnose and mitigate exec-related tooling failures around ClawHub publishing and GitHub CLI queries (auth, browser-login, missing dependencies, pending security-scan visibility errors, wrong profile/skill URLs, and gh JSON-field mismatch errors like Unknown JSON field). Use when publishing skills to ClawHub fails, inspect reports temporary errors, or GitHub CLI search commands fail due to field schema differences.

bluebirdback 4473

claw-history

Provide a chronological history of all actions the agent has taken from the beginning (birth) until now. Use when the user asks for full lifetime timeline/accountability, "from birth until now," "everything you've done so far," "full action log," or equivalent chronological-history requests.

bluebirdback 4473