Agent skill · operations · aiskillstore
error-resolver
Systematic error diagnosis and resolution using first-principle analysis. Use when encountering any error message, stack trace, or unexpected behavior. Supports replay functionality to record and reuse solutions.
Why this skill is useful
Provides a systematic framework for diagnosing and resolving errors that the AI wouldn't generate on its own.
What it needs
About 5k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Error Resolver A first-principle approach to diagnosing and resolving errors across all languages and frameworks. Core Philosophy The 5-step Error Resolution Process: Quick Start When you encounter an error: 1. Paste the full error (including stack trace if available) 2. Provide context (what were you trying to do?) 3. Share relevant code (the file/function involved) Error Classification Framework Primary Categories Category Indicators Common Causes ---------- ------------ --------------- Syntax Parse error, Unexpected token Typos, missing brackets, invalid syntax Type TypeError, type mismatch Wrong data type, null/undefined access Reference ReferenceError, NameError Undefined variable, scope issues Runtime RuntimeError, Exception Logic errors, invalid operations Network ECONNREFUSED, timeout, 4xx/5xx Connection issues, wrong URL, server down Permission EACCES, PermissionError File/directory access, sudo needed Dependency ModuleNotFound, Cannot find module Missing package, version mismatch Configuration Config error, env missing Wrong settings, missing env vars Database Connection refused, query error DB down, wrong credentials, bad query Memory OOM, heap out of memory Memory leak, large data processing Secondary Attributes Severity: Fatal / Error / Warning / Info Scope: Build-time / Runtime / Test-time Origin: User code / Framework / Third-party / System Analysis Workflow Step 1: Classify Identify the error category by examining: Error name/code (e.g., ENOENT, TypeError) Error message keywords Where it occurred (compile, runtime, test) Step 2: Parse Extract key information: Step 3: Match Patterns Check against known error patterns: See patterns/ directory for language-specific patterns Match error signatures to known solutions Check replay history for previous solutions Step 4: Root Cause Analysis Apply the 5 Whys technique: Step 5: Resolve Generate actionable solution: 1. Immediate fix - Get it working now 2. Proper fix - The right way to solve it 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/error-resolver