error-handling

Define RFC 9457 error responses and resilience patterns for APIs.

6|1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/wesleyosantos91/multi-agents --skill error-handling-wesleyosantos91
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: error-handling
Source: https://github.com/wesleyosantos91/multi-agents/tree/main/devin/.devin/skills/error-handling
Command: npx skills add https://github.com/wesleyosantos91/multi-agents --skill error-handling-wesleyosantos91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you design error handling and resilience patterns so failures are communicated clearly to clients, logged properly for operators, and recovered safely without breaking business flows.

Core Features & Use Cases

  • Consistent API errors (RFC 9457 / Problem Details): Standardizes error payloads with stable fields like type, title, status, detail, and instance for better client handling.
  • Correct exception mapping by type: Distinguishes validation, authentication/authorization, not-found, business-rule violations, rate limiting, and internal/dependency failures with appropriate HTTP statuses and log levels.
  • Resilience patterns for production systems: Provides cross-language guidance for retry with exponential backoff + jitter, circuit breaker, bulkhead isolation, rate limiting, and explicit timeouts.
  • Anti-pattern prevention: Avoids swallowing exceptions, returning stack traces to clients, throwing generic errors, and using exceptions for normal control flow.

Quick Start

Ask the AI to map your service’s current exceptions and failure modes to an RFC 9457 Problem Details response plan, and to propose the appropriate retry, circuit breaker, bulkhead, rate limiting, and timeout strategy for each outbound dependency.

Frequently Asked Questions about error-handling

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize API error responses using RFC 9457 Problem Details?

Map API exceptions to HTTP error responses by separating business versus technical failures. Standardize validation, authentication, not-found, and dependency failures with appropriate HTTP statuses and RFC 9457 Problem Details payloads.

What is the best way to handle transient failures like 429 and 503 responses?

Handle transient failures like 429 and 503 responses by applying resilience patterns including retry with exponential backoff plus jitter, circuit breakers, bulkhead isolation, rate limiting, and explicit timeouts to recover safely.

How should I map exception types to HTTP statuses and log levels?

Map exception types to HTTP statuses and log levels by distinguishing validation, authentication, not-found, business-rule, and dependency failures. Use disciplined logging that avoids leaking internal stack traces to clients.

What are common API error handling anti-patterns to avoid in production?

Common API error handling anti-patterns to avoid include swallowing exceptions, returning stack traces to clients, throwing generic errors, and using exceptions for normal control flow. These practices break business flows and obscure operational visibility.

When do I need a circuit breaker versus a retry with backoff for downstream dependencies?

You need a circuit breaker when an unstable downstream dependency repeatedly fails, preventing cascading outages. Use retry with exponential backoff and jitter for transient failures like timeouts or occasional 429 and 503 responses.