stuck-detection
From the author
Detect agent loops (repeated topics or repeated tool failures) and emit a self-reflection nudge. Use as an orchestrator guard against token-burning loops. Use when you say "check stuck loop", "detect repetition", "agent looping", "check failure loop", or "reset stuck history". Do NOT use for semantic similarity checks or multi-turn intent tracking; use a richer evaluation tool for those.
Install
npx skills add rjmurillo/ai-agents --skill stuck-detection -a claude-code
Installs to .claude/skills/stuck-detection/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
- Ships scripts we have not reviewedLow
Why 76
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- pattern-detecthoangsonww/Claude-Code-Agent-MonitorDetect recurring patterns using the Agent Monitor's workflow intelligence — toolFlow transitions (tool A → B frequency matrices), recurring workflow patterns, agent co-occurrence pairs, model delegation habits, error propagation paths by agent depth, and compaction triggers. Use to discover habitual usage patterns and anti-patterns.Productivity★ 1.1K
- loop-libraryadriannoes/awesome-agentic-aiDiscover, find, compare, audit, repair, adapt, and design repeatable AI-agent loops with explicit triggers, actions, verification, stopping conditions, guardrails, and handoffs. Use when a user asks to analyze a codebase for potential loops, mine coding-thread history for work done more than once, turn repeated engineering work into a loop, find or recommend a published loop, create a recurring agent workflow or automation cadence, turn an outcome into a bounded copy-ready loop, or review an existing loop for weak checks, unsafe authority, unbounded repetition, stale state, or unclear stopping behavior.Design★ 95
- agent-loop-testingnaodeng/awesome-qa-skillsUse this skill when you need evidence-bounded loop state, plan/action/observation cycles, stop conditions, budgets, repetition, and trace evidence; triggers include Agent 循环 and Agent loop.Testing★ 297
- agent-introspection-debuggingJasonxzWen/harness-hubLoad when a task needs agent run, tool loop, context drift, or recoverable harness/tool failure debugging; use diagnose for product/runtime bugs.Engineering★ 69
- agent-loopjmagly/aiwgDetect requests for iterative autonomous agent loops and route to the appropriate loop executorOther★ 228
- llm-observabilitynahid-sparktales/agent-dispatcherSee what an agent actually did — one trace per run with nested model, tool and retrieval spans, token and latency accounted per step, and failures clustered by mechanism instead of read one at a time. Use when an agent misbehaves in ways you cannot reproduce, when cost or latency is unexplained, when "it sometimes fails" is the whole bug report, or before writing evals when you do not yet know which failures exist. Not for judging whether an output is correct (agent-evals), and not a replacement for the application's own monitoring.DevOps★ 58
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in