error-recovery

Name: error-recovery
Availability: InStock
Author: acmeleme

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

Updated Nov 11, 2025

Search Tags:#error-handling #diagnose #escalation #fallback #retry #recovery-patterns #graceful-degradation

Ready to run

npx skills add https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator --skill error-recovery-acmeleme

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: error-recovery
Source: https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator/tree/main/.copilot/skills/error-recovery
Command: npx skills add https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator --skill error-recovery-acmeleme

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes error handling across agent workflows to reduce downtime and manual intervention.

Core Features & Use Cases

Retry with backoff for transient failures to improve reliability.
Fallback and graceful degradation to maintain partial functionality when a component fails.
Diagnose-and-Fix guidance to systematically identify and remediate root causes.
Escalate with context to hand off unresolved issues to humans or specialists.

Quick Start

Initiate appropriate recovery patterns in response to a failure by selecting and applying the most suitable pattern (retry, fallback, diagnose-and-fix, escalate with context, or graceful degradation) based on the fault type.

Frequently Asked Questions about error-recovery

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

FAQPage Schema

How do I handle transient API failures in agent workflows?▼

Handle transient API failures in agent workflows by applying retry with backoff patterns, which systematically re-attempt failed requests to improve reliability without manual intervention.

What is the best way to maintain partial functionality when a component fails?▼

The best way to maintain partial functionality when a component fails is to apply fallback and graceful degradation patterns, allowing agent workflows to continue operating in a reduced capacity instead of crashing completely.

How do I systematically diagnose and fix root causes of build or test errors?▼

Systematically diagnose and fix build or test errors by applying diagnose-and-fix guidance patterns, which provide structured steps to identify root causes and remediate operational faults across squad agents.

When should I use escalation with context for unresolved agent operational faults?▼

Use escalation with context for operational faults when automated recovery patterns fail, ensuring unresolved issues are handed off to humans or specialists with the necessary logging and criteria for remediation.

Does this error-handling approach work across multiple squad agents?▼

Yes, this error-handling approach works across multiple squad agents by standardizing recovery patterns for retry, fallback, and graceful degradation to ensure operational faults are addressed consistently across the entire workflow.

What are the limitations of automatic recovery patterns for agent workflows?▼

Automatic recovery patterns for agent workflows are limited by fault type; while they standardize handling for transient failures and build errors, unresolved issues still require manual escalation with context to a human specialist.