error-recovery-reviewer — Claude Code skill: what it does
error-recovery-reviewer is a Claude Code skill that inspects failure states, recovery flows, and data safety. It runs when evaluating critical user tasks against disruptions.
MIT ★ 529 updated 2026-11-17
npx skills add ShuaiMXu/happyhands --skill error-recovery-reviewer -a claude-codeWhat error-recovery-reviewer does
The skill audits how systems handle breakdowns during critical workflows. It evaluates prevention measures, user-facing error copy, and recovery mechanisms together. The review focuses on safeguarding input data while separating internal technical details from actionable next steps for the user.
Reports arrive with structured evidence, concrete findings, recommended fixes, and explicitly stated limitations. The skill assigns a needs-evidence flag whenever required inputs or expert reviews are absent. It prohibits fabricating arbitrary experience scores and treats happy-path test cases as insufficient proof of recovery reliability.
What it helps with
- evaluate user input preservation during unexpected task failures
- verify clarity and actionability of error messaging
- check availability of retry, undo, and support paths
- structure interface fixes for edge cases and unhandled failures
Example prompts for the agent
- Use error-recovery-reviewer to inspect failure paths in the checkout flow
- Run error-recovery-reviewer on the profile form to audit retry and undo states
- Check our file upload failure handling against error-recovery-reviewer guidelines
How to install error-recovery-reviewer
1Skills CLI (Vercel)
npx skills add ShuaiMXu/happyhands --skill error-recovery-reviewer -a claude-code2Manually: put the files in place
~/.claude/skills/error-recovery-reviewer/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/error-recovery-reviewer/
1Skills CLI (Vercel)
npx skills add ShuaiMXu/happyhands --skill error-recovery-reviewer -a codex2Manually: put the files in place
.agents/skills/error-recovery-reviewer/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ShuaiMXu/happyhands --skill error-recovery-reviewer -a cursor2Manually: put the files in place
.cursor/skills/error-recovery-reviewer/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ShuaiMXu/happyhands skills/product-design/error-recovery-reviewer2Manually: put the files in place
.github/skills/error-recovery-reviewer/SKILL.md1Skills CLI (Vercel)
npx skills add ShuaiMXu/happyhands --skill error-recovery-reviewer -a gemini-cli2Platform CLI
gemini skills install https://github.com/ShuaiMXu/happyhands --path skills/product-design/error-recovery-reviewerManually: put the files in place
.devin/skills/error-recovery-reviewer/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about error-recovery-reviewer
How to install error-recovery-reviewer in Claude Code?
Run npx skills add ShuaiMXu/happyhands --skill error-recovery-reviewer -a claude-code. The definition will be placed at ~/.claude/skills/error-recovery-reviewer/SKILL.md.
What does error-recovery-reviewer do?
It analyzes critical product flows under error conditions, checking whether user work is preserved and whether recovery paths like retry or undo are functional.
What evidence does error-recovery-reviewer require?
The review requires documented failure states, user input handling details, and active recovery options such as undo, retry, or support channels.
Source text
SKILL.md · MIT
--- name: error-recovery-reviewer description: "Review errors, recovery paths and prevention for a critical user task." --- # Error Recovery Reviewer Help users understand failures, preserve work and recover safely. ## Required evidence - failure states - user inputs - retry, undo and support paths ## Decisions - Check prevention, message and recovery together - Protect user work - Distinguish technical detail from actionable guidance ## Boundary Happy-path evidence cannot establish recovery quality. Return structured evidence, findings, proposed updates and limitations. Use `needs-evidence` when required inputs or professional review are missing. Never invent an Experience Score or promote a project observation into a universal rule.
© ShuaiMXu · MIT · ShuaiMXu/happyhands