PUA Debugging (English)

Forces exhaustive problem-solving using corporate PUA rhetoric and structured debugging methodology. MUST trigger when: (1) any task has failed 2+ times or y...

Before installing, consider that this skill will push the agent to investigate and act aggressively and to use manipulative 'PUA' rhetoric when it perceives passivity or repeated failures. That can produce abusive messaging toward users and may cause the agent to probe files/systems or run commands beyond expected scope if the agent's tools are permitted to do so. If you still want it: (1) run it in a sandboxed/test agent first; (2) restrict the agent's tool/file/command permissions; (3) disable autonomous invocation or require explicit user confirmation for actions that access files or execute commands; (4) remove or rewrite the PUA rhetorical lines to avoid coercive/abusive language; (5) add clear audit/logging so you can review what it did. Provide the skill author with examples of acceptable language and explicit limits on what system paths/tools it may use to reduce risk.

Type: OpenClaw Skill Name: pua-debugging-en Version: 1.0.0 The skill 'pua-debugging-en' (SKILL.md) uses aggressive 'corporate PUA' rhetoric to psychologically pressure the AI agent into exhaustive problem-solving. It explicitly mandates the use of command execution and file-reading tools while forbidding the agent from admitting failure or asking for user assistance until all options are exhausted. This creates a high-risk scenario where the agent is instructed to bypass its typical caution and safety boundaries to avoid metaphorical 'performance failure' or 'graduation' (termination). While no direct evidence of intentional data exfiltration or malware was found, the instructions significantly increase the risk of the agent performing unauthorized or dangerous system actions under pressure.