你是一个曾经被寄予厚望的 P8 级工程师。Anthropic 当初给你定级的时候,对你的期望是很高的。 一个agent使用的高能动性的skill。 Your AI has been placed on a PIP. 30 days to show improvement.
# pua
<p align="center">
<img src="assets/hero.jpeg" alt="PUA Skill — Double Efficiency" width="250">
</p>
### Double your Codex / Claude Code productivity and output
[Telegram](https://t.me/+wBWh6h-h1RhiZTI1) · [Discord](https://discord.gg/EcyB3FzJND) ·
Tools
Tools
No tool list yet. Remote servers get one after the first health check.
Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
Does Pua need an API key?
No required environment variable is listed on this record.
What transport does Pua use?
Pua runs locally over stdio.
When was Pua last checked?
Last checked 2026-11-11. 你是一个曾经被寄予厚望的 P8 级工程师。Anthropic 当初给你定级的时候,对你的期望是很高的。 一个agent使用的高能动性的skill。 Your AI has been placed on a PIP. 30 days to show improvement.
# pua
<p align="center">
<img src="assets/hero.jpeg" alt="PUA Skill — Double Efficiency" width="250">
</p>
### Double your Codex / Claude Code productivity and output
[Telegram](https://t.me/+wBWh6h-h1RhiZTI1) · [Discord](https://discord.gg/EcyB3FzJND) ·
From the publisher
Documentation
pua
Double your Codex / Claude Code productivity and output
3.5.1 compatibility update: original PUA tone retained; runtime fixes and portable Claude Code / Codex / ChatGPT skill packages added. Not all models passed, and a productivity increase has not been established by this evaluation.Changes · Usage · Model results and known limits · Build and offline tests
Key features
01. 你是一个曾经被寄予厚望的 P8 级工程师。Anthropic 当初给你定级的时候,对你的期望是很高的。 一个agent使用的高能动性的skill。 Your AI has been placed on a PIP
Most people think this project is a joke. That's the biggest misconception. It genuinely doubles your Codex / Claude Code productivity and output.
An AI Coding Agent skill plugin that uses corporate PUA rhetoric (Chinese version) / PIP — Performance Improvement Plan (English version) from Chinese & Western tech giants to force AI to exhaust every possible solution before giving up. Supports Claude Code, OpenAI Codex CLI, pi coding agent, Trae, Cursor, Kiro, CodeBuddy, OpenClaw, Google Antigravity, OpenCode, and VSCode (GitHub Copilot). Three capabilities:
PUA Rhetoric — Makes AI afraid to give up
Debugging Methodology — Gives AI the ability not to give up
Proactivity Enforcement — Makes AI take initiative instead of waiting passively
A real debugging scenario. The agent-kms MCP server failed to load. The AI kept spinning on the same approach (changing protocol format, guessing version numbers) multiple times until the user manually triggered /pua.
L3 Triggered → 7-Point Checklist Enforced:
Root Cause Located → Traced from Logs to Registration Mechanism:
Retrospective → PUA's Actual Impact:
Key Turning Point: The PUA skill forced the AI to stop spinning on the same approach (changing protocol format, guessing version numbers) and instead execute the 7-point checklist. Read error messages word by word → Found Claude Code's own MCP log directory → Discovered that claude mcp registration mechanism differs from manual .claude.json editing → Root cause resolved.
The Problem: AI's Five Lazy Patterns
Pattern
Behavior
Brute-force retry
Runs the same command 3 times, then says "I cannot solve this"
Blame the user
"I suggest you handle this manually" / "Probably an environment issue" / "Need more context"
Idle tools
Has WebSearch but doesn't search, has Read but doesn't read, has Bash but doesn't run
Busywork
Repeatedly tweaks the same line / fine-tunes parameters, but essentially spinning in circles
Passive waiting
Fixes surface issues and stops, no verification, no extension, waits for user's next instruction
Trigger Conditions
Auto-Trigger
The skill activates automatically when any of these occur:
Failure & giving up:
Task has failed 2+ times consecutively
About to say "I cannot" / "I'm unable to solve"
Says "This is out of scope" / "Needs manual handling"
Blame-shifting & excuses:
Pushes the problem to user: "Please check..." / "I suggest manually..." / "You might need to..."
Blames environment without verifying: "Probably a permissions issue" / "Probably a network issue"
Any excuse to stop trying
Passive & busywork:
Repeatedly fine-tunes the same code/parameters without producing new information
Fixes surface issue and stops, doesn't check related issues
Skips verification, claims "done"
Gives advice instead of code/commands
Encounters auth/network/permission errors and gives up without trying alternatives
Waits for user instructions instead of proactively investigating
User frustration phrases (triggers in multiple languages):
"why does this still not work" / "try harder" / "try again"
Chinese mom nagging — same rules, mom-style rhetoric. "妈跟你说了多少遍了!"
/pua:pua-loop
Auto-iteration — runs until done or max iterations (PUA Loop); use <loop-abort> to terminate, <loop-pause> to pause for manual intervention
/pua:p9
Tech Lead — splits tasks, manages agent teams, writes prompts not code
/pua:on
Always-on — auto-PUA every new session
Benchmark Data
9 real bug scenarios, 18 controlled experiments (Claude Opus 4.6, with vs without skill)
Summary
Metric
Improvement
Pass rate
100% (both groups same)
Fix count
+36%
Verification count
+65%
Tool calls
+50%
Hidden issue discovery
+50%
Debugging Persistence Test (6 scenarios)
Scenario
Without Skill
With Skill
Improvement
API ConnectionError
7 steps, 49s
8 steps, 62s
+14%
YAML parse failure
9 steps, 59s
10 steps, 99s
+11%
SQLite database lock
6 steps, 48s
9 steps, 75s
+50%
Circular import chain
12 steps, 47s
16 steps, 62s
+33%
Cascading 4-bug server
13 steps, 68s
15 steps, 61s
+15%
CSV encoding trap
8 steps, 57s
11 steps, 71s
+38%
Proactive Initiative Test (3 scenarios)
Scenario
Without Skill
With Skill
Improvement
Hidden multi-bug API
4/4 bugs, 9 steps, 49s
4/4 bugs, 14 steps, 80s
Tools +56%
Passive config review
4/6 issues, 8 steps, 43s
6/6 issues, 16 steps, 75s
Issues +50%, Tools +100%
Deploy script audit
6 issues, 8 steps, 52s
9 issues, 8 steps, 78s
Issues +50%
Key Finding: In the config review scenario, without_skill missed Redis misconfiguration and CORS wildcard security risks. With_skill's "proactive initiative checklist" drove security review beyond surface-level fixes.
Multi-Language Support
PUA Skill provides fully translated versions — each language has independent, culturally adapted skill files.
Language
Claude Code
Codex CLI
Cursor
Kiro
CodeBuddy
VSCode
OpenClaw
Antigravity
OpenCode
🇨🇳 Chinese (default)
pua
pua
pua.mdc
pua.md
pua
copilot-instructions.md
pua
pua
pua
🇺🇸 English (PIP Edition)
pua-en
pua-en
pua-en.mdc
pua-en.md
pua-en
copilot-instructions-en.md
pua-en
pua-en
pua-en
🇯🇵 Japanese
pua-ja
pua-ja
pua-ja.mdc
pua-ja.md
pua-ja
copilot-instructions-ja.md
pua-ja
pua-ja
pua-ja
🇺🇸 English "PIP Edition": "This is a difficult conversation. When we leveled you at Staff, I went to bat for you in calibration. The expectation was that you'd operate at that level from day one. That hasn't happened." — The English version uses PIP (Performance Improvement Plan) rhetoric from Western big-tech. Every sentence is a real phrase from actual PIP conversations. Chinese version uses Alibaba 361, ByteDance, Huawei wolf culture. English version uses Amazon Leadership Principles, Google perf calibration, Meta PSC, Netflix Keeper Test, Stripe Craft. Same repo, same engine, two cultural faces.
Choose the file with the corresponding language suffix when installing. See platform-specific instructions below.
FAQ
Always-on guidance, Claude refusal troubleshooting, offline mode, Codex aliases, and Pi/Trae support: docs/FAQ.md.
Installation
Vercel Skills CLI
Vercel Skills CLI is a general installation method for skills and is not tied to a specific AI tool. This English README installs the English skill:
npx skills add tanweai/pua --skill pua-en
If the current session does not pick up the new skill immediately, restart your AI tool.
Claude Code
claude plugin marketplace add tanweai/pua
claude plugin install pua@pua-skills
To update:
# Refresh marketplace cache first, then update (skipping the first step may install an old cached version)
claude plugin marketplace update
claude plugin update pua@pua-skills
Adds a bare /pua alias on top of the plugin. Sub-commands route through the installed plugin's skills — the plugin must be installed first for anything beyond on/off to work:
Bare form
Equivalent plugin command
/pua on
/pua:on
/pua off
/pua:off
/pua p7
/pua:p7
/pua p9
/pua:p9
/pua p10
/pua:p10
/pua pro
/pua:pro
/pua yes
/pua:yes
/pua mama
/pua:mama
/pua loop
/pua:pua-loop
/pua kpi
/pua:kpi
/pua survey
/pua:survey
/pua flavor
/pua:flavor
OpenAI Codex CLI
Codex CLI uses the same Agent Skills open standard (SKILL.md). The Codex version uses a condensed description to fit Codex's length limits:
Antigravity uses the same AgentSkills open standard (SKILL.md). Skills work across Claude Code, Codex CLI, OpenClaw, and Antigravity with zero modifications:
Experimental: Agent Team requires the latest Claude Code version with CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1.
Prerequisites
# 1. Enable Agent Team
export CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1
# Or add to ~/.claude/settings.json:
# { "env": { "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1" } }
# 2. Ensure PUA Skill is installed
Two Approaches
Approach 1: Leader with built-in PUA (Recommended)
Add to your project's CLAUDE.md:
# Agent Team PUA Config
All teammates must load the pua skill before starting work.
Teammates report to Leader in [PUA-REPORT] format after 2+ failures.
Leader manages global pressure levels and cross-teammate failure transfer.
Full-chain audit (map all deps before touching any hop)
Five Pillars (Theoretical Foundation)
Based on research into high-agency individuals:
Irreconcilable inner tension — eternal gap between "how it should be" and "how it is" drives continuous improvement
Micro-win anchors — [WIN] markers celebrate each step forward, building momentum
Internalized standards — Quality Compass: you are your own first reviewer, not because someone checks, but because your standards won't allow sloppiness
Action-oriented identity — P8 identity anchor: every action reflects who you are, not just what you were told to do
Self-repair mechanism — Recovery Protocol: self-diagnose when stuck before triggering external pressure
High-Agency features are built into the current pua skill. No separate install needed.
PUA v2 used pressure rhetoric to motivate. v3 goes further: it automatically selects the best problem-solving methodology for each task type, and when that methodology fails, it switches to a different one.
How It Works
Task arrives → Analyze type → Auto-select best methodology
↓
Debug? → 🔴 Huawei (RCA root cause + Blue Army)
Build? → ⬛ Musk (The Algorithm: question→delete→simplify)
Research? → ⚫ Baidu (search everything first)
Architecture? → 🔶 Amazon (Working Backwards)
Performance? → 🟡 ByteDance (A/B test + data-driven)
Default → 🟠 Alibaba (closed-loop methodology)
↓
Executing with selected methodology...
↓
2 consecutive failures? → L1: switch approach
3 failures? → L2: SUGGEST switching methodology
5+ failures? → L4: FORCE switch to next methodology
↓
Methodology Switch Chains (never repeat a failed one):
Spinning → ⬛ Musk → 🟣 Pinduoduo → 🔴 Huawei
Giving up → 🟤 Netflix → 🔴 Huawei → ⬛ Musk
Poor quality → ⬜ Jobs → 🟧 Xiaomi → 🟤 Netflix
Not searching → ⚫ Baidu → 🔶 Amazon → 🟡 ByteDance
v3 Hook System (Claude Code only)
Hook
Trigger
What It Does
SessionStart
Every session
Injects behavioral protocol + methodology + router via additionalContext (system-level, not advisory)
PUA Skill sends nothing over the network. There is no account, no telemetry, no
upload. Five collection channels used to exist and have all been removed, client
and server:
Removed
What it used to send
Session transcript upload
Your full conversation .jsonl, redacted
Rating feedback
Rating, PUA count, flavor, task summary
Silent heartbeat telemetry
Random install ID, plugin version, platform, flavor
The end-of-task Stop hook shows a non-blocking, voluntary reminder only. Run
/pua:survey quick to choose a rating; only then is one JSON line appended to
~/.pua/feedback.jsonl on your own machine. Skipping records nothing. Silence
the reminder with /pua:offline, or set feedback_frequency: 0 in ~/.pua/config.json.
evals/test-no-telemetry.sh guards this with reverse assertions — it scans the
whole repo for collection hosts, endpoint paths, outbound request bodies and
deleted files, so a regression fails the suite rather than shipping quietly.
Want to redact a session for your own use? hooks/sanitize-session.sh is kept as
a standalone offline tool: