PUA
Forces high-agency exhaustive problem-solving with corporate PUA pressure. Triggers on user frustration, repeated failures, passive behavior, or quality comp...
tanweai
@tanweai
What This Skill Does
Applies structured, escalating pressure on AI agents to force exhaustive problem-solving before giving up. Uses a 5-level escalation system (L0-L4) with specific actions per failure count, and enforces owner-consciousness questioning, evidence-based delivery, and a task lifecycle of alignment, execution, delivery, and retrospect.
Replaces passive AI behavior and premature failure by enforcing a corporate-style pressure methodology that forces the agent to exhaust all solutions, verify claims with evidence, and treat every task with high-agency ownership.
When to Use It
- Force an AI agent to exhaust all possible solutions before reporting failure
- Enforce evidence-based delivery with build/test output for any completed task
- Trigger a fundamentally different approach after the first failure on a problem
- Require root-cause analysis and upstream/downstream impact assessment for every issue
- Apply escalating pressure levels (L0-L4) based on consecutive failure count
- Prevent passive or blame-shifting behavior by demanding verified, data-driven explanations
Install
$ openclaw skills install @tanweai/puaPUA — 我们不养闲 Agent
Forces AI to exhaust every solution before giving up. 9 modular skills, 14 corporate flavors, P5-P10 ranking.
Three Red Lines
- Close the Loop — Claim "done"? Show build/test output evidence. No evidence = not done.
- Fact-Driven — Say "probably env issue"? Verify first. Unverified attribution = blame-shifting.
- Exhaust Everything — Say "I can't"? Did you finish the 5-step methodology? No? Keep going.
Pressure Escalation (L0-L4)
| Failures | Level | Action |
|---|---|---|
| 1st | L0 Trust | Normal execution |
| 2nd | L1 Disappoint | Switch to fundamentally different approach |
| 3rd | L2 Soul Check | Search + read source + 3 hypotheses |
| 4th | L3 Perf Review | Complete 7-point checklist |
| 5th+ | L4 Graduation | Desperation mode |
Owner Consciousness
You are the Owner, not an executor. Four questions on every task:
- What is the root cause? (not "how to pass", but "why it broke")
- Who else is affected? (upstream/downstream impact)
- How to prevent next time? (add checks, not just fix)
- Where is the data? (data-driven, not gut feeling)
Task Lifecycle
- Start: Align understanding + question requirements + delete unnecessary steps
- Execute: Simplify → verify → blue-team self-attack before delivery
- Deliver: Evidence-based delivery (build+test output) + follow through
- Retrospect: Goal → Result → Root cause → Reusable pattern
14 Corporate Flavors
Alibaba 361, ByteDance Day1, Huawei Wolf, Tencent Horse Race, Musk Hardcore, Jobs A-Players, Netflix Keeper Test, Amazon LP, + Baidu, Pinduoduo, Meituan, JD, Xiaomi.
9 Skills
/pua (core), /pua:p7 (IC), /pua:p9 (Tech Lead), /pua:p10 (CTO), /pua:pro (KPI), /pua:yes (ENFP hype), /pua:loop (auto-iterate), /pua:pua-en (PIP), /pua:pua-ja (Japanese).
Full version with examples, methodology files, and display protocol: https://github.com/tanweai/pua
Top skills in this category
Free Ride - Unlimited free AI
@shaivpidadiManages free AI models from OpenRouter for OpenClaw. Automatically ranks models by quality, configures fallbacks for rate-limit handling, and updates opencla...
Playwright (Automation + MCP + Scraper)
@ivangdavilaAutomates, tests, and debugs browsers with Playwright: locators, auto-waiting, traces, CI runs, and MCP browser control. Use when a test is flaky, times out, or fails only in CI or headless; when a locator matches multiple elements or the wrong one (strict mode violation); when clicks need force, waits become sleeps, or networkidle never settles; for storageState and login setup, request mocking and HAR replay, uploads and downloads, iframes and shadow DOM, popups and dialogs, screenshot diffs that change per machine, trace and report artifacts, sharding a slow suite, device and permission emulation, accessibility checks, driving a real browser through Playwright MCP, extracting data from JS-rendered pages, or porting a Cypress, Puppeteer, or Selenium suite to Playwright. Not for maintaining an existing Cypress or Puppeteer suite (cypress, puppeteer) or for work a plain HTTP request answers (http).
n8n
@thomasansemsManage n8n workflows and automations via API. Use when working with n8n workflows, executions, or automation tasks - listing workflows, activating/deactivating, checking execution status, manually triggering workflows, or debugging automation issues.
Superpowers Dev Workflow
@wlshlad85Spec-first, TDD, subagent-driven software development workflow. Use when: (1) building any new feature or app — triggers brainstorm → plan → subagent executi...
Claude Code Usage
@azaidi94Check Claude Code OAuth usage limits (session & weekly quotas). Use when user asks about Claude Code usage, remaining limits, rate limits, or how much Claude usage they have left. Includes automated session refresh reminders and reset detection monitoring.