error-recovery

Automate error recovery for agent workflows using retry, fallback, diagnose-and-fix, escalation, and graceful degradation with logging and auditable outcomes.

9|1|Updated Jul 21, 2025

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

Ready to run

npx skills add https://github.com/usepowershell/PoshMcp --skill error-recovery-usepowershell

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: error-recovery
Source: https://github.com/usepowershell/PoshMcp/tree/main/.copilot/skills/error-recovery
Command: npx skills add https://github.com/usepowershell/PoshMcp --skill error-recovery-usepowershell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standard recovery patterns help squads adapt to failures quickly instead of merely signaling errors.

Core Features & Use Cases

Retry with backoff: handle transient failures by retrying operations with an increasing delay.
Fallback alternatives: switch to alternative tools or methods when the primary option is unavailable.
Diagnose-and-Fix & escalation: analyze errors, attempt targeted fixes, and escalate with context when needed.
Graceful degradation: continue delivering value by skipping non-critical steps while warning about the skipped work.
Applies to automated workflows across distributed systems, including API calls, data processing, and task orchestration.

Quick Start

Provide a practical example applying the error-recovery patterns to a failing automation task.

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 automated workflows?▼

Handle transient API failures by applying retry with backoff patterns, which retry operations with an increasing delay to recover automated workflows without manual intervention.

What is graceful degradation in multi-agent coordination?▼

Graceful degradation in multi-agent coordination allows workflows to continue delivering value by skipping non-critical steps during failures while warning about the skipped work.

How do I implement fallback alternatives when a primary tool is unavailable?▼

Implement fallback alternatives to switch to alternative tools or methods automatically when the primary option is unavailable, ensuring automated workflows proceed despite component outages.

What's the best way to escalate errors with context in distributed systems?▼

Escalate errors with context by analyzing failures, attempting targeted diagnose-and-fix actions first, and escalating with full context only when needed to ensure auditable outcomes.

Does this error recovery approach work for network issues in task orchestration?▼

Yes, this error recovery approach works for network issues in task orchestration by standardizing recovery patterns across distributed systems, including data processing and API calls.

When should I not use retry with backoff for processing errors?▼

Avoid using retry with backoff for processing errors when failures are permanent, as retrying will not resolve non-transient issues; instead, use diagnose-and-fix or escalation patterns.