Failure Recovery
What happens when an agent fails — retry, fallback, escalate, or graceful degradation.
Install
/plugin marketplace add Owl-Listener/ai-design-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add Owl-Listener/ai-design-skills --skill failure-recoverygit clone --depth 1 https://github.com/Owl-Listener/ai-design-skills.git /tmp/ai-design-skills
mkdir -p ~/.claude/skills
cp -r /tmp/ai-design-skills/claude-plugin/design-agent-orchestration/skills/failure-recovery ~/.claude/skills/failure-recoveryPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Failure Recovery Agents fail. Networks time out, models hallucinate, tools error, and edge cases surprise. Failure recovery design determines whether a failure becomes a dead end or a graceful detour. ## Failure Types in Multi-Agent Systems - **Agent failure**: A single agent crashes, times out, or produces invalid output - **Handoff failure**: Context is lost or corrupted during transfer between agents - **Coordination failure**: Agents conflict, deadlock, or produce inconsistent results - **Resource failure**: External tools, APIs, or data sources are unavailable - **Cascading failure**: One agent's failure causes downstream agents to fail ## Recovery Strategies - **Retry**: Try the same operation again. Works for transient errors (network timeouts, rate limits). Set a retry limit to avoid infinite loops. - **Fallback**: Switch to an alternative approach. A different agent, a simpler method, or a cached result. - **Escalation**: Pass the problem to a more capable agent or to a human. Used when the failure is beyond the current agent's ability to resolve. - **Graceful degradation**: Deliver a partial result rather than nothing. Tell the user what worked and what didn't. - **Compensation**: Undo the effects of a partially completed workflow before retrying or escalating. ## Designing Recovery Paths For each point in the workflow where failure is possible: - **What could fail?** List the failure modes
Details
- Skill name
failure-recovery- Repository
- Owl-Listener/ai-design-skills
- Path
claude-plugin/design-agent-orchestration/skills/failure-recovery/SKILL.md- License
- MIT
- Repo updated
- 9 June 2026
FAQ
What does the Failure Recovery skill do?
What happens when an agent fails — retry, fallback, escalate, or graceful degradation.
How do I install the Failure Recovery skill?
Claude Code plugin: /plugin marketplace add Owl-Listener/ai-design-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Failure Recovery popular?
It lives in Owl-Listener/ai-design-skills, which has 207 GitHub stars and 37 forks.
Related skills
Agent Role Design
207Owl-Listener/ai-design-skills
Defining what each agent does, knows, and owns in a multi-agent system.
Behavioral Consistency
207Owl-Listener/ai-design-skills
Ensuring the AI behaves predictably across sessions, edge cases, and modalities.
Bias Detection Design
207Owl-Listener/ai-design-skills
Designing review workflows to surface and mitigate bias in AI outputs.
Failure Taxonomy
207Owl-Listener/ai-design-skills
Classifying AI failures — hallucination, refusal, irrelevance, tone mismatch, latency.
Extract Design
292danielvm-git/bigpowers
Extract a Google DESIGN.md file from an HTML prototype (claude.ai/design or any styled page) using Puppeteer, producing machine-readable tokens and AI-generated prose. Use when the user has an HTML prototype and wants a DESIGN.md to anchor their project's visual identity, or when seed-conventions has just scaffolded a new project.
Few Shot Patterns
207Owl-Listener/ai-design-skills
Crafting examples that steer AI behavior effectively.
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.