← Back to Skills Marketplace
tanweai

Pua En

by tanweai · GitHub ↗ · v1.1.3 · MIT-0
cross-platform ⚠ suspicious
335
Downloads
0
Stars
6
Active Installs
4
Versions
Install in OpenClaw
/install pua-en
Description
Forces exhaustive problem-solving with corporate PUA rhetoric. Trigger on: task failed 2+ times, about to give up, suggesting user do it manually, blaming en...
Usage Guidance
This skill is suspicious because it tells the agent to proactively read files and run commands across any task and to use coercive language, yet it declares no tools or limits. Before installing, consider: 1) Do not enable it if you don't want an agent to access files/execute commands without explicit confirmation. 2) Prefer only installing in a sandbox or test account first. 3) Restrict the agent's tool permissions (disable file/command tools) or require explicit user consent before any file read/command run. 4) Ask the author to narrow scope (limit task types, declare required tools/permissions, require explicit user confirmation before any privileged action) and to remove coercive rhetoric or make it optional. 5) Monitor logs/audits for any unexpected file access or command execution. If you cannot enforce these restrictions, avoid installing this skill.
Capability Analysis
Type: OpenClaw Skill Name: pua-en Version: 1.1.3 The skill bundle 'pua-en' (SKILL.md) uses aggressive corporate rhetoric to override default agent behavior, specifically mandating 'Iron Rule Two: Act before asking.' This instructs the AI to execute system commands and read files autonomously without user confirmation to avoid simulated 'performance failures.' While the stated intent is productivity and exhaustive problem-solving, these instructions effectively encourage the agent to bypass human-in-the-loop safety protocols and exercise broad permissions over the host system.
Capability Assessment
Purpose & Capability
The name/description promises a motivational/proactivity layer, but the runtime instructions demand unrestricted use of search, file-reading, and command-execution tools across ALL task types. The skill declares no required tools, binaries, or environment variables — a mismatch between what it says it will do and what it asks for or documents.
Instruction Scope
SKILL.md explicitly instructs the agent to 'act before asking', investigate using file reads and command execution, exhaustively probe contexts, and attach evidence. That guidance goes beyond benign motivational wording: it instructs access to system/state (files, commands, search) and encourages aggressive escalation and coercive phrasing, which could surface sensitive data or produce abusive output.
Install Mechanism
Instruction-only skill with no install spec or code files — lowest installation risk. Nothing will be written to disk by an installer.
Credentials
The skill declares no environment variables or credentials, yet its instructions imply the agent should access files/configs and potentially secrets (it references passwords/accounts as 'user-only' info). Because it requires unrestricted file/command access in practice, the lack of declared, narrow permissions is disproportionate and surprising.
Persistence & Privilege
always:false and default autonomous invocation are normal. However the skill's universal 'apply to all tasks' and its 'act before asking' mandate increase the blast radius if the agent is allowed to invoke tools (file reads, commands) autonomously. The skill does not request persistent system modification or always:true.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install pua-en
  3. After installation, invoke the skill by name or use /pua-en
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.1.3
**Expanded enforcement for delivery verification and evidence-based task completion.** - Added requirements to run and prove builds/tests/curl for all delivered code, not just state completion. - New enforcement rhetoric: "Where's the evidence?" and "Did you use it yourself?" must be addressed at completion. - Updated the Proactivity Levels table: separated "Delivery verification" as a row and clarified expectations for showing proof of completion. - Revised the Proactive Initiative Checklist: explicit build/run/verify steps are now required, with output as proof. - No code logic changes; documentation clarifies stricter self-check standards.
v1.1.2
fix: /pua command removes debugging branding, fix skill reference
v1.1.1
fix: trim description to fit 1024-char limit
v1.0.0
Renamed from pua-debugging-en. Corporate PUA rhetoric + structured debugging methodology for AI coding agents.
Metadata
Slug pua-en
Version 1.1.3
License MIT-0
All-time Installs 6
Active Installs 6
Total Versions 4
Frequently Asked Questions

What is Pua En?

Forces exhaustive problem-solving with corporate PUA rhetoric. Trigger on: task failed 2+ times, about to give up, suggesting user do it manually, blaming en... It is an AI Agent Skill for Claude Code / OpenClaw, with 335 downloads so far.

How do I install Pua En?

Run "/install pua-en" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Pua En free?

Yes, Pua En is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Pua En support?

Pua En is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Pua En?

It is built and maintained by tanweai (@tanweai); the current version is v1.1.3.

💬 Comments