troubleshoot-and-continue

Enforce a step-by-step troubleshooting protocol before user intervention.

Updated Dec 15, 2025
One-click install
npx skills add https://github.com/OpenSourceSam/v2_heras_garden --skill troubleshoot-and-continue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: troubleshoot-and-continue
Source: https://github.com/OpenSourceSam/v2_heras_garden/tree/main/.claude/skills/troubleshoot-and-continue
Command: npx skills add https://github.com/OpenSourceSam/v2_heras_garden --skill troubleshoot-and-continue

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents premature task abandonment by enforcing a rigorous troubleshooting protocol, ensuring all available resources are exhausted before seeking user intervention.

Core Features & Use Cases

  • Exhaustive Troubleshooting: Guides the agent through a multi-step process including self-correction, sub-agent delegation, and resource review before considering a stop.
  • Resource Management: Explicitly lists and mandates the use of internal tools, external sub-agents (MiniMax), and documentation.
  • Use Case: When faced with a complex coding error in Godot, the agent will first attempt self-correction, then consult two MiniMax sub-agents for research and sanity checks, review relevant documentation, and only then, if still blocked, document the attempts and consider asking the user for help.

Quick Start

When blocked, follow the 'Golden Path' troubleshooting protocol before considering user interruption.

Frequently Asked Questions about troubleshoot-and-continue

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

FAQPage Schema
How do I prevent my AI agent from stopping early when it hits a runtime error?

Yes, you can delegate complex debugging by routing research and sanity checks to sub-agents. This troubleshooting protocol mandates using sub-agents to verify solutions and review internal and external documentation before considering a task blocked.

What is the best way to manage agent resources when troubleshooting API failures?

The best way to manage resources during API failures is following an exhaustive protocol: attempt self-correction, delegate research to sub-agents, review relevant documentation, and only document attempts and seek help if still blocked.

How do I enforce a strict troubleshooting protocol for code bugs before escalating?

Enforce a strict troubleshooting protocol by mandating agents exhaust all available resources. The process requires self-correction, sub-agent sanity checks, and thorough review of internal tools and external documentation before escalating blockers to the user.

Does this troubleshooting approach work for resolving errors in game development environments like Godot?

Yes, this troubleshooting approach works for game development environments like Godot. When facing complex coding errors, the protocol guides agents through self-correction, sub-agent consultation, and documentation review before considering a stop.

Why does my agent protocol terminate tasks before exhausting all available debugging resources?

Agent protocols terminate tasks early when they lack a rigorous troubleshooting enforcement mechanism. Implementing a multi-step protocol ensures agents attempt self-correction, delegate to sub-agents, and review documentation before abandoning the task.