CtrlK
BlogDocsLog inGet started
Tessl Logo

pua-p9

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

48

Quality

50%

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

57%

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

The body is appropriately concise and well-structured for a simple alias skill, but its guidance is abstract rather than executable and the config-mutation workflow lacks an explicit validation checkpoint. Strengthening actionability and adding a verification step would materially improve it.

Suggestions

Add concrete, executable guidance for the destructive config operation, e.g. an explicit sequence with the exact config field(s) to set and a command/snippet showing the write.

Insert a validation checkpoint for the ~/.pua/config.json mutation (e.g., 'read back the file and confirm unknown fields are preserved before reporting completion') to lift workflow clarity.

Provide a minimal concrete example of a task prompt and how P8 execution is delegated, so the 'operate as a P9 tech lead' instruction is actionable rather than abstract.

DimensionReasoningScore

Conciseness

The body is lean (a handful of short lines), assumes Claude's competence, and contains no padding or explanation of concepts Claude already knows, matching the score-3 anchor of lean, efficient content where every token earns its place.

3 / 3

Actionability

Guidance is abstract ('Load and follow the p9 skill/protocol', 'write task prompts, manage P8 execution') with no concrete commands, code, or copy-paste-ready examples, matching the score-1 anchor of vague direction that describes rather than instructs.

1 / 3

Workflow Clarity

Steps are implied (load protocol, act as P9, mutate config, report evidence) but the destructive config write lacks an explicit validation/checkpoint step; per the guidelines, missing validation for destructive operations caps workflow clarity at 2.

2 / 3

Progressive Disclosure

The skill is under 50 lines with no bundle files and a single clear purpose, organized into short labeled sections; per the scoring notes this satisfies progressive disclosure at score 3 for a simple skill.

3 / 3

Total

9

/

12

Passed

Description

42%

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 identifies a clear, distinctive niche but relies on internal jargon instead of natural user trigger terms and omits an explicit 'Use when' clause. It conveys what the alias is but not when a user would invoke it.

Suggestions

Add an explicit 'Use when...' clause naming the natural user situations that should activate this skill (e.g., 'Use when the user wants to run the pua:p9 protocol via Codex').

Replace jargon like 'Codex subcommand mapping' with phrasings a user would naturally say, and include common variations of the trigger term.

List the concrete actions the alias performs (e.g., 'maps /pua:p9 to the p9 tech-lead protocol, writes task prompts, manages P8 execution') to lift specificity from 2 to 3.

DimensionReasoningScore

Specificity

It names the domain ('Codex subcommand mapping for Claude Code /pua:p9') and one concrete action ('invoke with $pua-p9'), but does not enumerate multiple specific capabilities, matching the score-2 anchor of naming domain and some actions without being comprehensive.

2 / 3

Completeness

It states what the skill is ('PUA P9 alias for Codex') but provides no explicit 'Use when...' trigger, so 'when' is only implied; per the guidelines a missing explicit trigger clause caps completeness at 2.

2 / 3

Trigger Term Quality

The keywords are internal jargon ('Codex subcommand mapping', '$pua-p9') rather than natural phrases a user would say when needing the skill; no common variations are covered, matching the score-1 anchor of technical jargon with no natural keywords.

1 / 3

Distinctiveness Conflict Risk

The '/pua:p9' alias is a narrow, specific niche with distinct triggers unlikely to be confused with other skills, matching the score-3 anchor of a clear niche with distinct triggers.

3 / 3

Total

8

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
tanweai/pua
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.