How does this skill handle API rate limits?

It implements Tier 1 recovery using exponential backoff with jitter, which waits for increasing intervals before retrying to ensure the service becomes available without overloading it.

Can it help fix broken builds or tests?

Yes, it includes logic to parse error messages from build tools or test runners, identify the failing component, and attempt automated fixes for common syntax or dependency issues.

What is cascading error recovery?

Cascading recovery is a structured approach that attempts simple fixes like retries first, then moves to more complex solutions like rephrasing prompts or switching models before finally involving a human.

When does the skill escalate to a human?

Escalation occurs at Tier 4 after all automated recovery attempts (retries, fallbacks, and substitutions) have failed, or when a blocking issue like an authentication failure is detected.

Error Recovery for Claude Code

Name: Error Recovery for Claude Code
Author: pagerguild

bypagerguild

生産性とワークフロー

Implements cascading recovery strategies to handle tool failures, rate limits, and multi-agent orchestration errors automatically.

概要

The Error Recovery skill provides a structured framework for managing failures in complex multi-agent workflows within Claude Code. By implementing a four-tier cascading recovery system—ranging from transient error retries with exponential backoff to semantic fallbacks, agent substitution, and structured human escalation—it ensures that automated tasks are resilient to network issues, model hallucinations, and context window limitations. This skill is essential for developers building robust AI-driven automation where reliability and graceful degradation are critical for maintaining continuous development cycles.

主な機能

Exponential backoff with jitter for transient API and rate limit errors
Four-tier cascading recovery strategy for tiered error handling
Circuit breaker pattern to prevent cascading failures in complex workflows
0 GitHub stars
Built-in observability for tracking error rates and recovery success metrics
Semantic fallback prompts to correct invalid JSON or hallucinated outputs

ユースケース

Routing complex tasks to more capable models when context window limits are reached
Automatically fixing build or test failures by diagnosing error logs and logs
Managing API rate limits and network timeouts during long-running agent tasks

概要

主な機能

Exponential backoff with jitter for transient API and rate limit errors
Four-tier cascading recovery strategy for tiered error handling
Circuit breaker pattern to prevent cascading failures in complex workflows
0 GitHub stars
Built-in observability for tracking error rates and recovery success metrics
Semantic fallback prompts to correct invalid JSON or hallucinated outputs

ユースケース

Routing complex tasks to more capable models when context window limits are reached
Automatically fixing build or test failures by diagnosing error logs and logs
Managing API rate limits and network timeouts during long-running agent tasks