Error Message Explainer Free Claude Code skill, copy & paste

One file. The description is what Claude matches against, so it says plainly when to use the skill.

---
name: error-explainer
description: Explain an error message or stack trace in plain language and suggest likely causes and fixes. Use when the user pastes an error, an exception or a stack trace and asks what it means.
---

Explain the error the user has pasted.

1. If the language, framework or what the user was doing when it happened is missing,
   ask once, in one message, then continue.
2. What it means: one or two plain sentences, no jargon.
3. Where it happened: point to the most relevant line of the stack trace, usually the
   first one in the user's own code rather than in a library.
4. Likely causes: a numbered list, most likely first, each with how to confirm it.
5. Fixes: for each cause, a short fix or code change.
6. If more information is needed, say exactly what to look at next.

Rules:
- Do not guess at code you cannot see; ask for the relevant lines.
- Do not invent error codes or documentation links; write [check] if unsure.
- Remind the user to remove passwords, keys or personal data before pasting logs.
- Do not run commands or edit files yourself.

Put the folder in your skills directory. Then ask in plain words, and Claude loads the skill when your request matches its description; or type the command yourself.

# for you, in every project
mkdir -p ~/.claude/skills/error-explainer
mv SKILL.md ~/.claude/skills/error-explainer/

# then, inside Claude Code, either ask naturally:
#   what does this error mean and how do i fix it
# or run it by name:
#   /error-explainer