skills.rest
codebytes
codebytesCOMMUNITY
Explore all skills by this author →
Website𝕏@chris_l_ayersGitHub

error-recovery

Applies structured recovery patterns to agent failures including retries, fallbacks, and escalation.

Updated Jun 2, 2026
Search Tags:#error recovery#escalation#fallback#graceful degradation#agent reliability#failure handling#retry backoff
One-click install
npx skills add https://github.com/codebytes/btt --skill error-recovery-codebytes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: error-recovery
Source: https://github.com/codebytes/btt/tree/main/.copilot/skills/error-recovery
Command: npx skills add https://github.com/codebytes/btt --skill error-recovery-codebytes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When automated agents encounter failures such as API timeouts, build errors, or missing dependencies, they often stop and simply report the error. This Skill provides standard recovery patterns so agents adapt, retry, and escalate with context instead of stalling. ## Core Features & Use Cases - Five Recovery Patterns: Retry with Backoff, Fallback Alternatives, Diagnose-and-Fix, Escalate with Context, and Graceful Degradation. - Failure-Type Selection Guide: A mapping table that pairs common failure types (network, build, auth, missing data) with the appropriate primary and fallback pattern. - Use Case: An agent's API call returns 429 Too Many Requests. Instead of failing, it waits 2 seconds, retries with exponential backoff up to 3 attempts, and escalates with full error context if still failing. ## Quick Start Apply the error-recovery patterns to handle any failure you encounter during this task instead of stopping at the first error.

Frequently Asked Questions about error-recovery

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

FAQPage Schema
How do I handle API rate limit errors in an automated agent?▼

Use the Retry with Backoff pattern: wait 2 seconds, retry, then double the wait each attempt up to 3 retries. If the API still returns 429 Too Many Requests, escalate with the full error context and a summary of attempts.

What should an agent do when a build or test fails?▼

Apply the Diagnose-and-Fix pattern: read the full error output, identify the root cause, attempt a targeted fix, and re-run to verify. Limit this to 3 fix-retry cycles before escalating to a human with context.

When should an agent escalate an error instead of retrying?▼

Escalate after exhausting recovery attempts, typically 3 retries, or when the failure requires human judgment such as design flaws or unknown errors. Include exact error messages, what was attempted, the suspected root cause, and suggested next steps.

Can a task still succeed if one step fails?▼

Yes, through Graceful Degradation. If the failed step is non-critical, log the failure, continue the task, deliver partial results with a clear note of what was skipped, and offer to retry the skipped step separately.

What is the difference between fallback alternatives and graceful degradation?▼

Fallback Alternatives replace a failed tool or method with another that achieves the same intent, such as switching from a CLI to a direct API call. Graceful Degradation skips a non-critical step entirely and delivers partial results.

Related Skills

Explore More Software Engineering Skills→
jlawsjlaws
2

cmd-architecture-workflow-spec

Map execution paths, failure modes, and handoff contracts before implementation.

Community
Advanced
usepowershellusepowershell
9

error-recovery

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

Community
Advanced
WingedGuardianWingedGuardian
90

obstacle-resolution

Classify obstacle types and execute fallback chains from fallback_chains.py.

Community
Advanced
orenmagidorenmagid

cabinet-debugger

Validate dependency chains and environment prerequisites before executing code.

Community
Advanced