error-recovery

Implement retry, fallback, diagnosis, escalation, and graceful degradation strategies for automated system failures.

18|3|Updated Jul 3, 2020
One-click install
npx skills add https://github.com/jguadagno/jjgnet-broadcast --skill error-recovery-jguadagno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: error-recovery
Source: https://github.com/jguadagno/jjgnet-broadcast/tree/main/.agents/skills/error-recovery
Command: npx skills add https://github.com/jguadagno/jjgnet-broadcast --skill error-recovery-jguadagno

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It addresses the need for structured and reliable recovery strategies when agents encounter failures or errors, ensuring continuous operation and minimizing downtime.

Core Features & Use Cases

  • Error Handling Patterns: Implements retry, fallback, diagnosis, escalation, and graceful degradation strategies.
  • Use Case: Automate error recovery in system workflows such as API calls, builds, and data processing tasks to improve robustness.
  • Scenario: When a network request fails, retry with exponential backoff; if a tool is unavailable, fallback to an alternative; or escalate with context if issues persist.

Quick Start

Refer to the patterns documented to implement consistent error recovery procedures within agent workflows, ensuring resilience against common failure modes.

Frequently Asked Questions about error-recovery

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

FAQPage Schema
How do I handle automated system failures and ensure reliable agent operation?

To handle automated system failures and ensure reliable agent operation, implement structured error recovery strategies like retry, fallback, diagnosis, and escalation to maintain continuous workflow execution and minimize downtime.

What is the best way to retry failed network requests in automated workflows?

The best way to retry failed network requests in automated workflows is applying structured error handling patterns, specifically utilizing exponential backoff strategies to systematically manage transient failures and improve operational robustness.

How do automated agents manage fallback when a tool is unavailable?

Automated agents manage fallback when a tool is unavailable by switching to alternative tools or processes, ensuring graceful degradation and allowing the system to continue functioning despite localized component failures.

When should error escalation be used in data processing or build workflows?

Error escalation should be used in data processing or build workflows when persistent issues exceed standard retry limits, triggering a diagnostic handover with contextual information to resolve complex failures safely.

Does implementing error recovery require external dependencies for system workflows?

Implementing structured error recovery for system workflows does not require external dependencies, as the skill provides self-contained reference patterns for failure handling, escalation, and diagnosis directly within automated agent environments.

Why do automated agents fail to recover from persistent tool failures without escalation?

Automated agents fail to recover from persistent tool failures without escalation because standard retry cycles exhaust their limits, requiring contextual diagnostic handover to safely bypass the failure and maintain system reliability.