Start a fresh conversation. Replace the highlighted placeholders.
Use error-handling-patterns to review [code or workflow] for error-handling gaps and provide prioritized fixes with expected behavior for [key failure cases].
Required inputs
[code or workflow]
[key failure cases]
User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
SKILL.md
name: error-handling-patternsdescription: "Build resilient applications with robust error handling strategies that gracefully handle failures and provide excellent debugging experiences."risk: safesource: communitydate_added: "2026-02-27"
Error Handling Patterns
Build resilient applications with robust error handling strategies that gracefully handle failures and provide excellent debugging experiences.
Use this skill when
Implementing error handling in new features
Designing error-resilient APIs
Debugging production issues
Improving application reliability
Creating better error messages for users and developers
Implementing retry and circuit breaker patterns
Handling async/concurrent errors
Building fault-tolerant distributed systems
Do not use this skill when
The task is unrelated to error handling patterns
You need a different domain or tool outside this scope
Instructions
Clarify goals, constraints, and required inputs.
Apply relevant best practices and validate outcomes.
Provide actionable steps and verification.
If detailed examples are required, open resources/implementation-playbook.md.
Resources
resources/implementation-playbook.md for detailed patterns and examples.
Limitations
Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.