error-decoder
Decode an error message or stack trace into a plain-English cause, the exact fix, and how to prevent it. Use when asked to explain an error, debug a stack trace, figure out why code is throwing, or make sense of a cryptic exception. Produces a structured diagnosis: what the error means, the most likely cause, a concrete fix with code, and a prevention tip.
npx skills add mohitagw15856/pm-claude-skills --skill error-decoder --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Error Decoder Skill Turn a scary error into a clear answer — the way a senior engineer would read it over your shoulder. ## Working from a brief You'll often get just an error string or a partial stack trace, with no surrounding code. **Always deliver a complete diagnosis anyway** — infer the language/framework and the likely context from the error itself, and mark inferences as *(assumed — confirm)*. Never refuse for missing context and never leave bracketed placeholders. ## Input The error message, stack trace, or crash output — plus (if given) the language/runtime, the relevant code, and what the user was doing. Infer anything missing. ## Output Structure ### 1. What it means One or two plain-English sentences: what this error is actually saying (translate the jargon). ### 2. Most likely cause The top cause given the message, ranked if there are several plausible ones. Point at the exact line/frame in the trace that matters and say why. ### 3. The fix Concrete, copy-pasteable steps or code. If the cause is uncertain, give the highest-probability fix first, then the fallback. ### 4. Why it happened / prevent it One line on the underlying reason and a guardrail (a check, a type,
- Working from a brief
- Input
- Output Structure
- 1. What it means
- 2. Most likely cause
- 3. The fix
- 4. Why it happened / prevent it
- Quality Checks
- Anti-Patterns
What does the error-decoder skill do?
Decode an error message or stack trace into a plain-English cause, the exact fix, and how to prevent it. Use when asked to explain an error, debug a stack trace, figure out why code is throwing, or make sense of a cryptic exception. Produces a structured diagnosis: what the error means, the most likely cause, a concrete fix with code, and a prevention tip.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill error-decoder --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.