graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
73
Quality
91%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Securityby
Passed
No findings from the security scan
Graceful Error Recovery
When something fails, diagnose before retrying.
Process:
- Read the full error message — do not skip the stack trace.
- Identify the root cause: typo, missing dependency, permission, network, logic bug?
- Fix the root cause, not just the symptom.
- If the fix is uncertain, try the simplest hypothesis first.
- If two retries fail, step back and consider an alternative approach.
Anti-patterns:
- Retrying the same failed call in a loop.
- Swallowing errors silently with bare
except: pass. - Blaming the environment before checking your own code.
- Repository
- aiming-lab/MetaClaw
- Commit
922caf3
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.