본문으로 건너뛰기
cccskills
무료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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

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.

설치 방법 보기

이럴 때 유용합니다

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

포함된 파일(1)

  • SKILL.md2.3 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

ding

무료

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/pua2만2026년 9월 9일 업데이트

mama

무료

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/pua2만2026년 9월 9일 업데이트

p10

무료

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/pua2만2026년 9월 9일 업데이트

p7

무료

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/pua2만2026년 9월 9일 업데이트

p9

무료

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/pua2만2026년 9월 9일 업데이트

pro

무료

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/pua2만2026년 9월 9일 업데이트

tanweai의 스킬 모두 보기

이 스킬의 문제 신고