pua-debugging-pro

PassAudited by VirusTotal on May 11, 2026.

Overview

Type: OpenClaw Skill Name: pua-debugging-pro Version: 1.0.0 The skill bundle provides a structured debugging protocol and reporting templates (SKILL.md, checklist-template.md) designed to improve AI agent persistence and evidence-based troubleshooting. It contains no executable code, network requests, or instructions to access sensitive data or bypass security controls. While it references an upstream project associated with 'PUA' (a slang term for behavioral manipulation of LLMs), this version is explicitly professionalized to enforce engineering standards and dignified communication without any malicious intent.

Findings (0)

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.

NoteHigh Confidence
ASI01: Agent Goal Hijack
What this means

The agent may keep troubleshooting longer before asking for help or stopping.

Why it was flagged

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.

Skill content
Do not conclude "cannot solve" before completing escalation checklist.
Recommendation

Use this skill when persistent debugging is desired, and override it if time, cost, or safety constraints require an earlier stop.

What this means

The agent may inspect relevant project context, run tests or commands, or perform a documentation lookup as part of debugging.

Why it was flagged

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.

Skill content
Use available tools first. ... one external lookup or doc check ... Ran validation (test/command/request) and recorded result
Recommendation

Keep normal approval boundaries for risky commands, production changes, network requests, or actions that could modify data.