error-recovery

Name: error-recovery
Availability: InStock
Author: pagerguild

Orchestrate cascading error recovery for multi-agent workflows with tiered strategies.

1|Updated Jan 15, 2026

Search Tags:#multi-agent #orchestration #error-recovery #escalation #retry #backoff #circuit-breaker

Ready to run

npx skills add https://github.com/pagerguild/guilde-lite --skill error-recovery-pagerguild

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: error-recovery
Source: https://github.com/pagerguild/guilde-lite/tree/main/marketplace/plugins/context-preservation/skills/error-recovery
Command: npx skills add https://github.com/pagerguild/guilde-lite --skill error-recovery-pagerguild

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Cascading error recovery for multi-agent workflows addresses the need to gracefully recover from failures across orchestrated agents, tools, and tasks, reducing downtime and manual intervention.

Core Features & Use Cases

Tiered recovery: transient retries with exponential backoff, semantic fallbacks, agent substitution, and human escalation
Error classification: tailored strategies for transient, output, capability, and blocking errors
Guardrails: circuit breakers and structured escalation templates
Use cases: failing tasks, rate limits, invalid outputs, context overflow, and cross-agent cooperation

Quick Start

Provide a failed task description and let the system apply tiered recovery automatically.

Frequently Asked Questions about error-recovery

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

FAQPage Schema

How do I handle cascading failures across multiple agents in a workflow?▼

Cascading failure across multi-agent workflows is handled by applying tiered recovery strategies like transient retries with exponential backoff, semantic fallbacks, agent substitution, and human escalation, reducing downtime and manual intervention across orchestrated tasks.

What is the best way to retry transient errors and rate limits in agent orchestration?▼

Retrying transient errors and rate limits in agent orchestration is best handled using exponential backoff with jitter, which spaces out repeated requests to prevent system overload and gracefully recover from temporary failures.

How does circuit breaking work for blocking errors in multi-agent systems?▼

Circuit breaking for blocking errors in multi-agent systems works by acting as a guardrail that trips when failure thresholds are exceeded, halting repeated execution attempts and triggering structured human escalation templates instead of causing a total workflow collapse.

Can I use agent substitution to bypass capability gaps and context overflow during task execution?▼

Yes, you can use agent substitution rules to bypass capability gaps and context overflow. The system classifies these specific output and capability errors, automatically substituting the failing agent with a suitable alternative to maintain workflow continuity.

Do I need to manually classify errors before applying recovery strategies to failing tasks?▼

No, you do not need to manually classify errors before applying recovery strategies. The system automatically classifies failures into transient, output, capability, and blocking error categories to apply tailored recovery logic and structured escalation automatically.

How do I set up human escalation templates for invalid outputs in an orchestrated agent workflow?▼

Human escalation templates for invalid outputs are set up as a final tier in the recovery process. When semantic fallbacks and agent substitution rules fail to resolve output issues, the system generates structured templates to alert human operators for manual intervention.