pua-p10

PUA P10 alias for Codex. Codex subcommand mapping for Claude Code /pua:p10 style usage; invoke with $pua-p10.

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./codex/pua-p10/SKILL.md

Quality

Content

72%

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

The body is admirably concise and appropriately self-contained for a thin alias skill, with a useful verification checkpoint and concrete config-safety guards. Its weakness is that the substantive work is offloaded to an external skill and the CTO role-play direction is abstract, leaving actionability and workflow clarity at the middle anchor.

Suggestions

Make the delegated core concrete: instead of only 'Load and follow the p10 skill/protocol', summarize the key P10/CTO steps inline or link explicitly to the p10 skill so actionability is not purely external.

Turn the evidence requirement into an explicit validate-then-proceed step (e.g., 'Show command output as proof before reporting success') to give the single-action workflow a clear checkpoint and lift workflow_clarity.

If the p10 skill defines the real multi-step process, name it as a one-level reference with its trigger so navigation is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is a lean four paragraphs with no padding and no explanation of concepts Claude already knows; every sentence carries an instruction, matching the 'lean and efficient; every token earns its place' anchor.	3 / 3
Actionability	Concrete guards are present ('preserve unknown fields', 'create ~/.pua/ if missing', 'Do not claim completion without command/output evidence'), but the core task delegates to 'the p10 skill/protocol' and the role-play line ('define strategic direction, org topology, and P9 management boundaries') is abstract, fitting 'some concrete guidance but incomplete'.	2 / 3
Workflow Clarity	As a single-action alias it has one loose checkpoint (the evidence requirement), but there is no sequenced workflow and the actual procedure lives in the external p10 skill, matching 'steps listed but validation gaps; checkpoints missing or implicit'.	2 / 3
Progressive Disclosure	The skill is well under 50 lines, has no bundle files, and references only an external skill one level deep ('Load and follow the p10 skill/protocol'); for a simple self-contained skill this satisfies the simple-skills allowance for a 3.	3 / 3
	Total	10 / 12 Passed

Description

57%

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 clearly identifies the skill as a niche Codex alias with distinctive triggers, but it is more an identity statement than a capability statement: it lacks an explicit 'Use when...' clause and does not enumerate concrete actions. It reads as jargon-heavy internal shorthand rather than user-facing trigger guidance.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when the user invokes /pua:p10 or asks for P10/CTO strategic direction') to lift completeness above 2.

Replace the identity framing ('PUA P10 alias for Codex') with concrete capabilities (e.g., 'Defines strategic direction, org topology, and P9 management boundaries') so specificity reaches the multiple-actions anchor.

Soften internal jargon ('Codex subcommand mapping') in favor of natural terms a user would actually say.

Dimension	Reasoning	Score
Specificity	Names the domain ('Codex subcommand mapping', 'Claude Code /pua:p10 style usage') and an action ('invoke with $pua-p10'), but frames the skill by what it is (an alias) rather than listing multiple concrete actions, so it stops short of the anchor-3 'lists multiple specific concrete actions'.	2 / 3
Completeness	It states what the skill is (alias / subcommand mapping) but has no 'Use when...' clause; the when is only implied via 'invoke with $pua-p10', so per the guideline a missing explicit trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	Contains the literal trigger tokens ('/pua:p10', '$pua-p10') a user would type, but surrounds them with internal jargon ('PUA P10 alias', 'Codex subcommand mapping') and misses common natural-language variations, matching 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	The skill is bound to a distinct command namespace ('/pua:p10', '$pua-p10'), giving it a clear niche that is very unlikely to trigger for an unrelated skill.	3 / 3
	Total	9 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: tanweai/pua
Path: codex/pua-p10/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.