mcpField
E
error-handling-patterns

error-handling-patterns

github.com/sickn33Development49.1k371 installsUpdated today
Repository

About error-handling-patterns

A skill for applying error-handling practices in application development, debugging, and reliability work. It covers API resilience, retries, circuit breakers, and errors in asynchronous or distributed systems.

Key features

  1. 01Design resilient API error handling
  2. 02Improve debugging and error messages
  3. 03Apply retry and circuit breaker patterns
  4. 04Handle asynchronous and concurrent errors
  5. 05Address failures in distributed systems

Use cases

  1. 01Add error handling to a new feature
  2. 02Debug production failures
  3. 03Improve reliability in APIs or distributed services

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sickn33/agentic-awesome-skills --skill error-handling-patterns

After installing, type/error-handling-patternsin Claude Code to confirm it loaded.

Bundled filesresources/implementation-playbook.md

Details

From the project README

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.

Comments

Markdown supported