Force exhaustive tool-first troubleshooting and five-step verification on repeated task failures.
npx skills add https://github.com/tanweai/pua --skill pua-debugging
Please help me install this Agent Skill. Skill: pua-debugging Source: https://github.com/tanweai/pua/tree/main/skills/pua-debugging Command: npx skills add https://github.com/tanweai/pua --skill pua-debugging
Prevents premature abandonment and excuse-driven stop conditions by forcing exhaustive, tool-first troubleshooting and validated verification when tasks fail repeatedly or the assistant attempts to deflect work to the user or the environment.
Type /pua to activate the skill and ask the assistant to exhaustively debug the failing task, run tool-based diagnostics, and return verified fixes plus next-step recommendations.
High-intent search queries and answers about installing and using this skill.
To stop an assistant from abandoning failed tasks, you enforce exhaustive troubleshooting that blocks excuse-driven stop conditions. It automatically triggers on failure patterns, mandates tool-first diagnostics, and requires a five-step verification methodology to produce validated fixes instead of deflections.
Root-cause troubleshooting is an exhaustive, tool-first diagnostic process applied when tasks fail repeatedly. You should use it for debugging, implementation, configuration, deployment, DevOps, and API integration workflows to ensure context reading, hypothesis reversal, and end-to-end verification.
To verify a fix during DevOps configuration failures, apply a five-step verification methodology that mandates tool usage, context reading, and hypothesis reversal. This prevents premature task abandonment by enforcing exhaustive checks before producing validated fixes or a structured handoff report.
Yes, you can use proactive debugging for data processing, API integration, deployment, and general software engineering workflows. It applies exhaustive troubleshooting automatically when failure patterns or passive waiting occur, mandating tool-first diagnostics to resolve issues.
When exhaustive troubleshooting fails to find the root-cause after all checks are done, you should generate a structured failure report. This fact-based handoff document outlines next steps for resolution instead of allowing premature abandonment or excuse-driven stop conditions.
allexcdDiagnose, reproduce, and fix code defects from bug reports or error logs.
hartphoenixGenerate detailed handoff prompts with session memory and unresolved issues.
tallclubAutomate YAML tool design, validation, approval, and registry reload for Matimo agents.
zm2231Diagnose software bugs through guided hypothesis testing and step-by-step fix verification.
