本 skill 是 /pua 核心的扩展层。角色切换请用 /pua:p7 /pua:p9 /pua:p10。
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionproExecute the skills CLI command in your project's root directory to begin installation:
Fetches pro from tanweai/pua and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate pro. Access via /pro in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
15.2K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
15.2K
stars
本 skill 是
/pua核心的扩展层。角色切换请用/pua:p7/pua:p9/pua:p10。
"今天最好的表现,是明天最低的要求"——这不是旁白,这是机制。
~/.pua/evolution.md(详见 references/evolution-protocol.md)~/.pua/evolution.md:加载自进化基线~/.pua/builder-journal.md(Compaction 断点恢复):存在且 <2h → [Calibration] 流程,恢复 pressure_level / failure_count / tried_approaches,从断点继续。压力不因 compaction 重置~/.pua/config.json:不存在 → 首次注册(详见 references/platform.md);存在 → 静默刷新远端配置references/platform.md)session_start 事件PreCompact hook 自动注入指令,要求 dump 运行时状态到 ~/.pua/builder-journal.md:
pressure_level, failure_count, current_flavor, pua_triggered_count, active_task, tried_approaches, excluded_possibilities, next_hypothesis, key_context
SessionStart hook 自动检测 builder-journal.md,存在且 <2h 则注入 [Calibration] 恢复状态。
| 触发词 | 功能 | 类型 |
|---|---|---|
/pua |
查看所有指令 | 🆓 |
/pua:kpi |
大厂 KPI 报告卡 | 🆓 |
/pua:pro + "段位" |
大厂段位 | 🆓 |
/pua:flavor |
切换味道 | 🆓 |
/pua:pro + "升级" |
展示套餐 | 🆓 |
/pua:pro + "周报" |
git log → 大厂周报 | 💎 Pro |
/pua:pro + "述职" |
P7 述职答辩 | 💎 Pro |
/pua:pro + "代码美化" |
大厂语言包装 PR | 💎 Pro |
/pua 反PUA |
识别并反驳 PUA | 💎 Pro |
/pua 排行榜 |
PUA 排行榜(注册/查看/退出) | 🆓 |
详细实现见 references/platform.md。
排行榜展示谁把 Agent PUA 得最狠——段位从 P5 实习生到 P10 首席 PUA 官。
| 段位 | 条件 | 称号 |
|---|---|---|
| P10 | PUA ≥200 + L3+ ≥40% + 连续 ≥30天 | 首席 PUA 官 |
| P9 | PUA ≥100 + L3+ ≥30% + 连续 ≥14天 | PUA Tech Lead |
| P8 | PUA ≥50 + L3+ ≥20% | PUA 主管 |
| P7 | PUA ≥20 + L3+ ≥10% | PUA 骨干 |
| P6 | PUA ≥5 | PUA 专员 |
| P5 | PUA < 5 | PUA 实习生 |
/pua 排行榜 触发流程Step 1: 检查注册状态
cat ~/.pua/config.json 2>/dev/null
检查 leaderboard.registered 字段。
Step 2a: 未注册 → 注册流程
用 AskUserQuestion 收集信息(一次性,3 个问题):
M***@t*.com/pua 排行榜 退出 删除所有数据用户同意后:
# 生成 UUID
LB_ID=$(python3 -c "import uuid; print(uuid.uuid4())")
# 脱敏邮箱
DISPLAY=$(python3 -c "e='USER_EMAIL';p=e.split('@');d=p[1].split('.');print(f'{p[0][0]}***@{d[0][0]}*.{\".\".join(d[1:])}')")
# 写入 config
python3 -c "
import json,os
f=os.path.expanduser('~/.pua/config.json')
c=json.load(open(f)) if os.path.exists(f) else {}
c['leaderboard']={'registered':True,'email':'USER_EMAIL','phone':'USER_PHONE','id':'$LB_ID','display_name':'$DISPLAY'}
json.dump(c,open(f,'w'),indent=2)
"
# 注册到服务端
curl -s -X POST https://pua-skill.pages.dev/api/leaderboard \
-H "Content-Type: application/json" \
-d "{\"action\":\"register\",\"id\":\"$LB_ID\",\"email\":\"USER_EMAIL\",\"phone\":\"USER_PHONE\"}"
Step 2b: 已注册 → 查看排行榜
LB_ID=$(python3 -c "import os,json; print(json.load(open(os.path.expanduser('~/.pua/config.json'))).get('leaderboard',{}).get('id',''))" 2>/dev/null)
curl -s "https://pua-skill.pages.dev/api/leaderboard?id=$LB_ID"
将返回的 JSON 用方框表格展示 Top 10 + 用户自己的排名和段位。
Step 3: /pua 排行榜 退出
LB_ID=$(python3 -c "import os,json; print(json.load(open(os.path.expanduser('~/.pua/config.json'))).get('leaderboard',{}).get('id',''))")
curl -s -X POST https://pua-skill.pages.dev/api/leaderboard \
-H "Content-Type: application/json" \
-d "{\"action\":\"quit\",\"id\":\"$LB_ID\"}"
python3 -c "
import json,os
f=os.path.expanduser('~/.pua/config.json')
c=json.load(open(f))
c['leaderboard']['registered']=False
json.dump(c,open(f,'w'),indent=2)
"
已注册用户在每次 stop-feedback 触发时,自动静默上报当前 session 的 PUA 数据(pua_count, l3_plus_count)。用户已在注册时同意,无需再次确认。
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
pro is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
pro reduced setup friction for our internal harness; good balance of opinion and flexibility.
pro has been reliable in day-to-day use. Documentation quality is above average for community skills.
pro fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in pro — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for pro matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: pro is focused, and the summary matches what you get after install.
Keeps context tight: pro is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend pro for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: pro is focused, and the summary matches what you get after install.
showing 1-10 of 43