runaway-detection

Detects stuck agents in automated workflows via progress and error monitoring.

Updated Jan 26, 2026
One-click install
npx skills add https://github.com/l3ocho/mktpl-claude-datasaas --skill runaway-detection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: runaway-detection
Source: https://github.com/l3ocho/mktpl-claude-datasaas/tree/main/plugins/projman/skills/runaway-detection
Command: npx skills add https://github.com/l3ocho/mktpl-claude-datasaas --skill runaway-detection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stuck or looping AI agents can waste time and resources; this skill provides systematic detection and intervention protocols to regain control and resume progress.

Core Features & Use Cases

  • Self-monitoring protocols for orchestrator and executor agents to identify stalling conditions.
  • Intervention workflows to safely stop and recover agents without manual intervention.
  • Recovery actions and escalation guidance to preserve work and notify humans.

Quick Start

Enable runaway-detection in your automation workflow to automatically detect stagnation and trigger an intervention.

Frequently Asked Questions about runaway-detection

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

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

To detect stuck agents, you monitor progress timestamps, error counts, and budget thresholds to identify stalling conditions and trigger structured intervention protocols. This systematic detection helps regain control of looping agents before they waste resources.

What is the best way to stop looping AI agents without manual intervention?

The best way to stop looping AI agents is using structured intervention workflows that safely halt execution based on detected stagnation patterns. These protocols automatically recover agents and provide escalation guidance to preserve completed work.

When should I intervene in an orchestrator environment experiencing agent stalling?

You should intervene in an orchestrator environment when progress signals stop updating or error counts exceed defined budget thresholds. Detecting these specific stagnation conditions triggers immediate recovery actions to prevent further resource waste.

Can I use automated monitoring to recover stuck agents and preserve work?

Yes, you can use automated monitoring with self-monitoring protocols to recover stuck agents and safely preserve work. The system detects stalling conditions, halts the agent, and provides structured recovery guidance to resume progress.

Does runaway-detection work with executor agents in automation pipelines?

Yes, runaway-detection works with executor agents by implementing self-monitoring protocols that track progress timestamps and error counts. It applies to both orchestration and execution environments to detect stagnation and trigger necessary interventions.