Error Diagnosis

v1.0.0

Analyze error messages and logs to identify root causes of crashes, build failures, or runtime errors and suggest actionable fixes with code examples.

0· 40·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for charlie-morrison/error-diagnosis.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Error Diagnosis" (charlie-morrison/error-diagnosis) from ClawHub.
Skill page: https://clawhub.ai/charlie-morrison/error-diagnosis
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install error-diagnosis

ClawHub CLI

Package manager switcher

npx clawhub@latest install error-diagnosis
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description match the provided SKILL.md and the included parse_stacktrace.py. The script purpose (extracting error type, frames, and search queries) is directly relevant to diagnosing errors.
Instruction Scope
SKILL.md confines runtime behavior to parsing provided error text, classifying, tracing, and suggesting fixes. It does not instruct the agent to read system files, environment variables, or external config paths beyond what the user pastes or provides explicitly.
Install Mechanism
No install spec is present (instruction-only plus a small included Python script). There are no downloads, external installers, or archive extraction steps. The included script is readable, not obfuscated, and contains no network or exec calls.
Credentials
The skill declares no required env vars or credentials, which is appropriate. Note: the SKILL.md encourages pasting logs/configs and the parser builds search queries containing error text; these could contain sensitive info (tokens, file paths, emails) if users paste raw logs—so avoid or redact secrets before use.
Persistence & Privilege
always is false, no install writes or system modifications are requested, and the skill does not request persistent privileges or access to other skills' configs.
Assessment
This skill looks coherent and low-risk: it includes a harmless Python parser and no extra permissions. Before using it, do not paste secrets, credentials, or entire unredacted production logs (the tool generates search queries that include snippets of your input). If you plan to run the included script locally, inspect it yourself (it's simple regex parsing) and run it in a sandboxed environment if you have any doubt. Finally, treat any suggested fixes as guidance—verify in a safe test environment before applying to production.

Like a lobster shell, security has layers — review code before you run it.

latestvk9734y2n13mza66b8h8ss0zhkh85n6yy
40downloads
0stars
1versions
Updated 1d ago
v1.0.0
MIT-0

Error Diagnosis

Analyze error messages, stack traces, and log output to diagnose root causes and suggest fixes. Use when debugging crashes, runtime errors, build failures, or unexpected behavior.

Usage

Diagnose this error: [paste error message or stack trace]

Or with context:

Diagnose: [error]. Language: [lang]. Framework: [framework]. Recent changes: [what changed].

How It Works

  1. Parse — extract error type, message, file locations, line numbers from raw output
  2. Classify — categorize the error (syntax, runtime, dependency, config, permission, network, OOM, etc.)
  3. Trace — follow the call stack to identify the originating code vs. where the error surfaced
  4. Diagnose — determine root cause using error patterns, common pitfalls, and framework-specific knowledge
  5. Fix — provide actionable fix with code snippets

Supported Error Sources

  • Stack traces: Python, JavaScript/Node.js, Java, Go, Rust, C/C++, Ruby, PHP
  • Build errors: npm, pip, cargo, gradle, maven, webpack, vite, tsc
  • Runtime errors: segfaults, OOM, deadlocks, race conditions, type errors
  • Infrastructure: Docker, Kubernetes, systemd, nginx, database connection errors
  • CI/CD: GitHub Actions, GitLab CI, CircleCI failure logs

Output Format

## Error Type
[Classification: e.g., "TypeError — accessing property of undefined"]

## Root Cause
[1-2 sentences explaining WHY this happened]

## Fix
[Code snippet or command to resolve]

## Prevention
[How to avoid this in the future: type check, test, lint rule, etc.]

Advanced Features

Multi-Error Analysis

Paste multiple errors — the skill identifies whether they share a root cause or are independent issues.

Regression Detection

This error started after [commit/change]. Analyze whether the change could cause this.

Environment Comparison

Works in dev, fails in prod. Error: [error]. Dev config: [config]. Prod config: [config].

Scripts

scripts/parse_stacktrace.py

Extracts structured data from raw stack traces:

python3 scripts/parse_stacktrace.py < error.log

Returns JSON with error type, message, frames (file, line, function), and suggested search queries.

Comments

Loading comments...