pro

PUA Pro extensions: self-evolution notes, compaction state continuity, KPI-style summaries, flavor switching, and feedback tools.

Quality

50%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/pro/SKILL.md

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with concrete executable scripts and clearly sequenced workflows, but it sacrifices conciseness to flavor text and omits validation checkpoints around destructive operations. Progressive disclosure is hampered by references to non-existent bundle files and inline implementation detail.

Suggestions

Add explicit validation steps after network/config mutations (e.g., check curl exit codes, verify the JSON write succeeded before proceeding) so destructive workflows include feedback loops.

Trim motivational flavor text and emoji badges that do not advance Claude's execution, keeping only the operative mechanism.

Move the full leaderboard registration/view/quit bash flow into a referenced script file under scripts/ and provide the actual references/ files (evolution-protocol.md, platform.md) so signaled paths resolve.

Dimension	Reasoning	Score
Conciseness	The body is mostly dense and assumes competence, but motivational flavor text ('今天最好的表现，是明天最低的要求'), emoji badges, and decorative section titles add padding that could be tightened.	2 / 3
Actionability	It provides fully executable, copy-paste-ready bash/python3/curl snippets for leaderboard registration, viewing, and quit flows, with specific commands and inline variables.	3 / 3
Workflow Clarity	Multi-step processes are numbered and sequenced, but destructive/server-mutating operations (config writes, API registration, data deletion on quit) lack explicit validation checkpoints or error-recovery feedback, capping this at 2 per the rubric guidance.	2 / 3
Progressive Disclosure	Sections are organized and reference evolution-protocol.md/platform.md inline, but the referenced files do not exist in any bundled references/ directory and the full leaderboard bash flow is inline rather than split out, leaving organization only adequate.	2 / 3
	Total	9 / 12 Passed

Description

35%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description enumerates concrete feature areas but lacks natural trigger terms and any explicit 'when to use' guidance, capping both completeness and trigger quality. It is niche-labeled yet partially generic, making it only moderately distinctive.

Suggestions

Add a 'Use when ...' clause naming natural user triggers (e.g., 'Use when the user wants weekly big-tech-style reports, PUA-style performance reviews, or leaderboard features').

Replace internal jargon ('compaction state continuity', 'flavor switching') with phrases a user would naturally say, such as 'recover work after context compaction' or 'switch interaction style'.

Frame capabilities as concrete actions (e.g., 'Generates weekly reports from git logs, builds P7 performance reviews') rather than as a list of feature nouns.

Dimension	Reasoning	Score
Specificity	The description names several concrete capability domains ('self-evolution notes, compaction state continuity, KPI-style summaries, flavor switching, and feedback tools'), but presents them as feature nouns rather than concrete actions, so it stops short of the multi-action anchor.	2 / 3
Completeness	It states what the skill does (lists extensions) but never says when to use it; per the guidelines a missing 'Use when...' clause caps completeness at 2.	2 / 3
Trigger Term Quality	Terms like 'compaction state continuity', 'KPI-style summaries', and 'flavor switching' are internal jargon rather than natural phrases a user would say; no natural trigger keywords are present.	1 / 3
Distinctiveness Conflict Risk	The 'PUA Pro' framing is niche-specific, but generic-sounding capabilities like 'feedback tools' and 'KPI-style summaries' could still overlap with other skills, so it is only somewhat distinctive.	2 / 3
	Total	7 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 4 missing	Warning

	Total	15 / 16 Passed

Repository: tanweai/pua
Path: skills/pro/SKILL.md
Commit: 3fd4e5a

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.