pua-debugging-pro
PassAudited by ClawScan on May 1, 2026.
Overview
This is an instruction-only debugging workflow that encourages evidence-based troubleshooting and includes clear bounded stop conditions.
This skill appears safe to install as a debugging aid. It may make the agent more persistent and tool-oriented during coding failures, so use it when you want structured troubleshooting and continue to require review for any risky commands or environment-changing actions.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent may keep troubleshooting longer before asking for help or stopping.
This changes the agent's stopping behavior by requiring a debugging escalation process before giving up; however, the same artifact also defines bounded escalation and stop conditions.
Do not conclude "cannot solve" before completing escalation checklist.
Use this skill when persistent debugging is desired, and override it if time, cost, or safety constraints require an earlier stop.
The agent may inspect relevant project context, run tests or commands, or perform a documentation lookup as part of debugging.
The protocol encourages tool-based diagnosis, external documentation checks, and validation commands or requests. This is expected for a coding debugging workflow, but users should be aware it may cause the agent to run checks where tools are available.
Use available tools first. ... one external lookup or doc check ... Ran validation (test/command/request) and recorded result
Keep normal approval boundaries for risky commands, production changes, network requests, or actions that could modify data.