failure-recovery

Define YAML-based recovery steps for stuck agents and build failures.

Updated Nov 22, 2025
One-click install
npx skills add https://github.com/Khamel83/oneshot --skill failure-recovery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: failure-recovery
Source: https://github.com/Khamel83/oneshot/tree/main/archive/v9/skills/failure-recovery
Command: npx skills add https://github.com/Khamel83/oneshot --skill failure-recovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Recovery protocols for when an agent is stuck, experiences context exhaustion, or encounters repeated build failures. This guide helps teams restore progress without guesswork and reduces downtime during complex automation workflows.

Core Features & Use Cases

  • Stepwise recovery templates for common failure modes (looping, confusion, dependency conflicts, and degraded responses).
  • Clear triage and isolation steps to stabilize the project state and verify each fix before proceeding.
  • Applicable to automated agent workflows, testing pipelines, and long-running tasks that require safe handoffs and verifiable resets.

Quick Start

Tell me the symptoms you observe, and I will guide you through a structured recovery sequence.

Frequently Asked Questions about failure-recovery

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

FAQPage Schema
How do I recover an automated agent stuck in a looping behavior or repeated build failures?

Recover stuck agents by applying standardized YAML-based recovery procedures that isolate changes and verify each fix. This structured triage process stabilizes the project state, addresses looping behavior, and safely restarts automated workflows after repeated build failures.

What is the best way to handle context exhaustion in long-running automated workflows?

Handle context exhaustion by applying stepwise recovery templates that detect degraded responses and trigger verifiable resets. This structured approach ensures long-running tasks and automated agent workflows restore progress safely without guesswork or losing project state.

How do I troubleshoot dependency conflicts during an automated agent workflow?

Troubleshoot dependency conflicts by following structured triage and isolation steps defined in the recovery protocol. This standardized process ensures safe, incremental fixes by isolating conflicting changes and running verifiable validation after each corrective action before proceeding.

Does this agent recovery approach work with testing pipelines that require safe handoffs?

Yes, this recovery approach works with testing pipelines by providing stepwise templates for safe handoffs and verifiable resets. It applies to long-running tasks and automated workflows, ensuring each fix is validated before proceeding to prevent repeated failures.

Why does an automated agent experience degraded responses and how do I fix it?

Automated agents experience degraded responses due to context exhaustion or repeated failures, which you fix by applying structured recovery sequences. These sequences define clear triage paths and guardrails to standardize recovery, ensuring safe, incremental fixes and verifiable validation after each action.