stuck-recovery

Detect stuck loops in automated workflows and produce advisory recovery outputs.

13|6|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/baekenough/second-brain --skill stuck-recovery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stuck-recovery
Source: https://github.com/baekenough/second-brain/tree/main/.claude/skills/stuck-recovery
Command: npx skills add https://github.com/baekenough/second-brain --skill stuck-recovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects when tasks get trapped in repetitive failure loops and provides advisory recovery strategies to keep automation moving.

Core Features & Use Cases

  • Signals-based detection of stuck loops (repeated error, edit loop, agent/tool loop) with structured advisory outputs.
  • Prescribes recovery strategies and escalation paths to minimize downtime and manual intervention.
  • Integrates with orchestrators, enabling safe, advisory-only guidance (R010) and stateful handoffs when context reset is triggered.

Quick Start

Enable the stuck-recovery skill in your orchestrator and feed in task execution logs so that when a loop is detected you can follow the advisory output to recover.

Frequently Asked Questions about stuck-recovery

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

FAQPage Schema
How do I detect stuck loops in automated workflows?

Stuck loop detection in automated workflows works by feeding task execution logs into an orchestrator, which then applies signals-based detection to repeated errors, edit loops, and agent tool loops. This produces structured advisory outputs to prevent productivity loss.

What is the best way to recover from repeated errors in agent retries?

Recovering from repeated errors in agent retries requires advisory recovery strategies that prescribe specific escalation paths. The system detects the loop and generates advisory-only guidance to minimize downtime and manual intervention.

Can I use advisory-only guidance for R010-style handoffs in workflow resilience?

Advisory-only guidance for R010-style handoffs integrates directly with orchestrators to enable safe, stateful handoffs. It triggers context resets during loop detection to ensure workflow resilience without forcing automated actions.

Does this approach work with long-running tasks and tool integrations?

This approach works across orchestration tasks, retries, and tool integrations by monitoring long-running tasks for repetitive failure patterns. It applies signals-based detection to identify when tools or agents become trapped in loops.

Why does my automated workflow keep getting trapped in repetitive failure loops?

Automated workflows get trapped in repetitive failure loops due to repeated errors, edit loops, or agent tool loops. Signals-based detection identifies these patterns in execution logs and provides structured advisory outputs to guide recovery actions.