CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pua-p9

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

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./codex/pua-p9/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

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

The content is a tight, well-organized instruction-only alias skill that gives concrete behavioral directives and a config-safety rule. It would benefit from a brief explicit step for loading the p9 protocol and a small validation checkpoint before claiming completion.

DimensionReasoningScore

Conciseness

Lean ~6-line body that assumes Claude's competence and adds only what is not already known; every token earns its place.

5 / 5

Actionability

Concrete directives ("write task prompts, manage P8 execution", "preserve unknown fields and create ~/.pua/ if missing", "do not claim completion without command/output evidence") but no executable code/commands and minor gaps such as how to load the p9 protocol.

4 / 5

Workflow Clarity

Single-purpose alias skill with an implicit but coherent sequence (load p9, operate as P9, manage P8, preserve config); not a destructive/batch operation so no cap applies, though explicit checkpoints are absent.

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references and well-organized heading + paragraphs, satisfying the simple-skill exception for full marks.

5 / 5

Total

18

/

20

Passed

Description

65%Weight 40%Scale 1-5

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 communicates a specific niche and good trigger terms, but it lacks an explicit "when to use" clause and comprehensive capability listing. Adding a concrete trigger condition would lift completeness and specificity.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user invokes /pua:p9 or asks for P9 tech-lead orchestration via Codex."

List concrete actions more comprehensively (e.g. "writes task prompts, delegates to P8, manages config") instead of just "subcommand mapping".

Keep third-person voice (currently good) but avoid the first-person-tinged "invoke with" phrasing in favor of a clear trigger phrase.

DimensionReasoningScore

Specificity

"PUA P9 alias for Codex. Codex subcommand mapping" names the domain and one concrete action (subcommand/alias mapping) but lacks comprehensive coverage of capabilities.

3 / 5

Completeness

Has a clear "what" (alias/subcommand mapping) but the "when" is only weakly implied by the invocation note rather than an explicit "Use when..." clause, capping completeness at 3.

3 / 5

Trigger Term Quality

Includes several natural trigger terms ("Codex subcommand mapping", "/pua:p9", "invoke with $pua-p9") that a user would naturally say, with only minor terms missing.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (P9 alias for Codex, `/pua:p9`, `$pua-p9`) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

15

/

20

Passed

Validation

100%

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-p9/SKILL.md

Reviewed

Table of Contents

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.