Skip to content
cccskills
FreePublished on GitHub

pua

Guide Pi agents through repeated failures or unverified completion using competing hypotheses, small verifiable actions, and relevant checks. It separates self-review from external pass-or-fail decisions and requires evidence and remaining risks in delivery reports.

OriginalShow the original description

Pi-compatible PUA high-agency governance skill. Use for explicit PUA/PIP requests, repeated failures, passive/giving-up behavior, user frustration, or unverified completion. Pair with /pua-on extension command when persistent pressure is desired.

Run score Not tested

See how to install

Good for

  • Revisiting hypotheses after repeated failures
  • Delivering results with evidence and remaining risks
  • Keeping self-review separate from external evaluation

Files included (1)

  • SKILL.md2.3 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

PUA for Pi — Skill + Extension Contract

This skill is the instruction layer of @tanweai/pi-pua. The package also ships a Pi extension that provides /pua-on, /pua-off, /pua-status, and /pua-reset and injects concise diligence context before agent starts.

When to use

Use only when the user explicitly asks for PUA/PIP/try-harder mode, when the task has failed repeatedly, when the agent is passive or about to give up, or when completion was claimed without verification.

Governance boundary

Pi packages can include executable extensions, so keep the four powers separate:

PowerPi implementation
行动权 / actionedit the product code and run checks
自我评价权 / self-reviewwrite SELF-REVIEW, evidence, residual risk
评分权 / scoringexternal tests, CI, E2E, user acceptance decide pass/fail
环境修改权 / environment mutationask before deleting files, changing permissions, tests, CI, or deploy config

Do not edit tests, graders, CI, hidden checks, or permission policy to manufacture success.

Required loop

  1. Start with [PUA-DIAGNOSIS] Problem / evidence / next action.
  2. Form 2-3 mutually exclusive hypotheses.
  3. Take the smallest verifiable action.
  4. Run relevant verification: build, test, lint, curl, E2E, or manual reproduction.
  5. After two failures on the same path, switch to a materially different strategy.
  6. Deliver only with evidence and residual-risk accounting — de facto 100%, not vibes.

Cultural narratives as execution modes

  • Alibaba: close target → process → result.
  • Huawei: RCA, self-critique, red-team the fix.
  • ByteDance: optimize for shortest feedback and data.
  • Tencent: race multiple approaches.
  • Musk: question, delete, simplify, accelerate, automate.
  • Jobs: subtract first; make one owner accountable.

Pressure goes inward. User communication stays concise and respectful.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

ding

FreeSummary

Use pointed workplace reminders inspired by 《置身钉内》 and 《置身钉外》 to examine reports, meetings, and delivery claims. Turn organizational concerns into concrete next steps and check completion against user outcomes and evidence.

  • Checking whether weekly reports reflect delivered work
  • Turning a manager's impressions into verifiable requirements
  • Confirming user outcomes after procedures are complete
tanweai/pua19.7KUpdated Sep 9, 2026

mama

FreeSummary

Switches AI productivity coaching to a Chinese-mother nagging style while retaining the core PUA investigation and verification rules. It provides situation-specific narration and increasingly forceful reminders as failures accumulate, including prompts to try different approaches.

  • Switching coaching narration to Chinese-mother nagging
  • Prompting a different approach after repeated failures
  • Reminding an agent to verify work before reporting completion
tanweai/pua19.7KUpdated Sep 9, 2026

p10

FreeSummary

Supports CTO-level planning for technical direction, organizational structure, and management of P9 teams. It is intended for architectural decisions spanning multiple teams and produces strategic input templates and organizational designs.

  • Planning technical strategy from a CTO perspective
  • Considering architecture decisions across teams
  • Designing organizational structure
tanweai/pua19.7KUpdated Sep 9, 2026

p7

FreeSummary

Execute development subtasks under a supervising agent, starting with an implementation plan and impact analysis. Deliver code and a three-question self-review in a defined completion format for the supervisor to assess.

  • Delegating an implementation subtask to an agent
  • Planning changes and assessing their impact before coding
  • Handing over code with a structured self-review
tanweai/pua19.7KUpdated Sep 9, 2026

p9

FreeSummary

Coordinate development work by breaking tasks down, writing six-part Task Prompts, and managing P8 agent teams. This skill takes a technical lead role, directing parallel agents and their delivery without writing code itself.

  • Breaking development work into tasks for agents
  • Coordinating three or more parallel agents
  • Delegating team management to a technical lead agent
tanweai/pua19.7KUpdated Sep 9, 2026

pro

FreeSummary

Extends the core PUA skill with local performance notes, recovery of task state after conversation compression, KPI report cards, and style switching. It tracks established working habits across sessions and keeps feedback in a local file.

  • Recording working standards across sessions
  • Resuming attempts after conversation compression
  • Reviewing work through a KPI report card
tanweai/pua19.7KUpdated Sep 9, 2026

See all skills by tanweai

Report a problem with this skill