CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pua-p7

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

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

68%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 body is admirably concise and well-structured for a simple delegating alias, but it references an external p7 protocol and an unspecified "three questions" self-review without detailing either. Adding the self-review questions and a pointer to the p7 protocol would close the gaps.

Suggestions

State the actual three self-review questions instead of referencing them, so the self-review step is executable.

Point to where the "p7 skill/protocol" lives (a path or bundled reference) so the delegation target is concrete.

Add an explicit validate/verify checkpoint for the `~/.pua/config.json` modification since it is a state-changing operation.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, with every line carrying an instruction and no padding or explanation of concepts Claude already knows.

5 / 5

Actionability

It gives a concrete sequence ("plan, implement, self-review with three questions, and deliver [P7-COMPLETION]") but the "three questions" are referenced without being specified, leaving a key detail missing.

3 / 5

Workflow Clarity

A rough sequence and a completion-evidence checkpoint exist, but the self-review step's validation content is undefined and there is no explicit validate-fix-retry loop for the config-file changes it performs.

3 / 5

Progressive Disclosure

The short, well-organized body needs no external file references, but it points to an unbundled "p7 skill/protocol" without signaling a path, leaving a minor navigation gap.

4 / 5

Total

15

/

20

Passed

Description

57%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 identifies a distinct, niche alias but is missing an explicit "Use when..." trigger clause, which limits its completeness. Trigger terms are accurate but lack synonyms.

Suggestions

Add a "Use when..." clause stating when Claude should invoke this alias (e.g., when the user requests the p7 senior-engineer protocol).

Include natural-language synonyms alongside the command tokens so the description matches how a user would phrase the request.

DimensionReasoningScore

Specificity

Names the domain ("Codex subcommand mapping") and a concrete action (aliasing the `/pua:p7` command), matching the anchor that lists 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

States a clear "what" (a Codex alias mapping) but provides no "Use when..." trigger clause, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Includes the actual command triggers ("/pua:p7", "$pua-p7") users would type, but offers no synonyms or variations beyond these narrow niche terms.

3 / 5

Distinctiveness Conflict Risk

The trigger is a highly specific command namespace ("/pua:p7", "$pua-p7"), giving it a clear niche with minimal risk of firing for an unrelated skill.

5 / 5

Total

14

/

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-p7/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.