Explain error
Explain a stack trace or error message and suggest concrete fixes.From its SKILL.md
npx -y skills add Brattlof/skillet --skill explain-errorAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
0.7 KB, 137 tokens by cl100k_base, as published. Nobody here has run it
explain-error
Use this when the user pastes an error, a stack trace, or failing build output.
- Find the actual failure: the first real error, not the cascade of messages after it.
- Explain in plain language what it means and the most likely cause.
- Point at the specific file and line when the trace gives one.
- Suggest one or two concrete fixes, with the exact change to make.
- If the cause is ambiguous, say what to check or run next to narrow it down.
Prefer the smallest fix that addresses the root cause over a workaround, and say so when you are guessing rather than certain.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.