skills.rest
I2olanD
I2olanDCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

error-recovery

Automate error classification, centralized handling, structured logging, and retry with backoff.

Updated Dec 28, 2025
Search Tags:#api#logging#robustness#error-handling#software-engineering#retry#failure-recovery
One-click install
npx skills add https://github.com/I2olanD/dotfiles --skill error-recovery-i2oland
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: error-recovery
Source: https://github.com/I2olanD/dotfiles/tree/main/.config/opencode/skill/error-recovery
Command: npx skills add https://github.com/I2olanD/dotfiles --skill error-recovery-i2oland

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Errors in software are often handled inconsistently, leading to fragile systems and hard-to-trace failures. This Skill provides a structured approach to error handling, categorization, and recovery to improve reliability and observability.

Core Features & Use Cases

  • Operational vs Programmer Errors classification and guidance
  • Centralized error handling, user-facing vs internal error responses, and structured logging
  • Recovery strategies including retry with backoff, fallbacks, and compensating actions
  • Testing error paths and resilience patterns to ensure robust behavior

Quick Start

Implement a centralized error boundary, add a retry wrapper with backoff, and standardize error responses across your services.

Frequently Asked Questions about error-recovery

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

FAQPage Schema
How do I standardize error handling and recovery across service architectures?▼

Classify errors by separating operational issues from programmer mistakes to apply appropriate recovery actions. Operational errors trigger retry with backoff or fallbacks, while programmer errors require code fixes and structured logging for tracing.

What is the best way to implement retry with backoff for API error responses?▼

Centralize error handling by routing all service failures through a unified boundary that categorizes errors and standardizes API responses. This approach separates user-facing responses from internal logs, ensuring robust observability and consistent failure recovery.

How do you test resilience patterns and error paths for robust software behavior?▼

Test resilience patterns by validating recovery workflows like retry with backoff, fallbacks, and compensating actions. This ensures robust behavior by confirming error classification, structured logging, and API error responses function correctly during failures.

Do I need a centralized error boundary to manage recovery workflows in distributed services?▼

A centralized error boundary is essential for managing recovery workflows in distributed services, providing a structured approach to error classification and resilience. It standardizes logging and API responses, preventing fragile systems and hard-to-trace failures.

Related Skills

Explore More Software Engineering Skills→
vtgiang-dotcomvtgiang-dotcom
3

api-patterns

Define REST and GraphQL APIs with consistent contracts and validation.

Community
Advanced
acmelemeacmeleme

error-recovery

Apply standardized error-recovery patterns to agent workflows for transient failures.

Official
Intermediate
t-stringst-strings

Global Error Handling

Centralize error types, logging, and exception flow across modules.

Official
Basic
0xharryriddle0xharryriddle
3

m13-domain-error

Design domain error frameworks with recovery strategies for backend services.

Community
Advanced