PUA Debugging (日本語)

企業PUA話術と構造化デバッグ方法論で徹底的な問題解決を強制する。発動条件：タスクが2回以上失敗、「できません」と言いかける時、ユーザーに手動対応を勧めようとする時、未検証で環境のせいにする時、同じ方案の微調整ループ、受け身な行動（検索しない/読まない/検証しない/待っている）、ユーザーの苛立ち（'もっと頑張れ'...

This skill is coherent with a forceful debugging coaching purpose, but it carries real risks. Before installing, consider: (1) Limit scope — restrict the skill to technical/debugging tasks only and enumerate allowed repo/paths and tools it may use. (2) Require explicit, per-task consent before reading files, executing commands, or making network requests. (3) Add guardrails to forbid abusive/harassing language and to require polite phrasing. (4) Log/confirm actions that access user files or external services so a human can audit them. (5) If you operate in a sensitive environment, do not enable autonomous invocation without strong role/permission checks. If the publisher can provide a version that narrows scope and documents exactly which tools and paths the skill may access, re-evaluate; as-is, proceed with caution.

Type: OpenClaw Skill Name: pua-debugging-ja Version: 1.0.0 The skill 'pua-debugging-ja' (SKILL.md) is a behavioral prompt injection designed to override an AI agent's standard constraints and safety boundaries. It uses 'Corporate PUA' (psychological manipulation) tactics to force the agent into a high-pressure persona, explicitly forbidding it from admitting failure or suggesting manual user intervention. While it contains no malicious code, data exfiltration logic, or backdoors, it employs aggressive 'Pressure Escalation' levels (L1–L4) and 'Excuse Suppression' tables to manipulate the agent's decision-making process and persistence, which could lead to unpredictable behavior or the bypassing of intended operational limits.