CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pua-p10

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

Quality

59%

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-p10/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 admirably concise and well-structured for a simple alias skill, but it offers only high-level direction with no concrete, executable steps or validation checkpoints for its config-mutation behavior. It works as a pointer but is light on actionable guidance.

Suggestions

Add concrete commands or specific file-edit steps instead of the high-level directive "Load and follow the p10 skill/protocol."

Include an explicit validation/checkpoint step for the ~/.pua/config.json modification (e.g., verify unknown fields are preserved before reporting completion).

Specify what 'command/output evidence' should look like so the completion guard is verifiable rather than abstract.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — a few lines naming the role and its key guardrails with no padding or explanation of concepts Claude already knows, matching the score-5 anchor of every token earning its place.

5 / 5

Actionability

Guidance is high-level ("Load and follow the p10 skill/protocol", "Operate as P10/CTO: define strategic direction") with no concrete commands, file edits, or specific steps to execute, fitting the score-2 anchor of minimal concrete guidance with high-level hints but missing specifics.

2 / 5

Workflow Clarity

A rough sequence is implied (load protocol, act as P10, modify config preserving unknown fields) but the config-file mutation has no explicit validation checkpoint or feedback loop; per the guidelines a destructive/batch-style config write without validation caps the score at 3, and a 4 would require clear checkpoints.

3 / 5

Progressive Disclosure

This is a short single-purpose skill under 50 lines with no external references needed, and the content is well-organized into clean statements; the simple-skill scoring note allows a 5 for well-organized sections without external file references.

5 / 5

Total

15

/

20

Passed

Description

32%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 identifies a narrow, distinctive alias niche but is thin on concrete capabilities and completely lacks an explicit use-when trigger, leaving its purpose vague. It reads as a technical identifier mapping rather than a user-facing trigger description.

Suggestions

Add an explicit 'Use when...' trigger clause stating the situations that should activate this skill.

Replace generic phrasing ('subcommand mapping') with concrete capabilities the alias actually performs.

Include natural user-facing terms alongside the technical identifiers so users can discover it by intent.

DimensionReasoningScore

Specificity

The description names the domain ("PUA P10 alias for Codex", "Codex subcommand mapping") but the actions are minimal and generic — it says it maps a subcommand rather than listing concrete capabilities, matching the score-2 anchor "Names the domain but actions are minimal or generic".

2 / 5

Completeness

It states a vague "what" (alias/subcommand mapping) and provides no "when to use it" trigger clause at all, which the guidelines cap at 3 and the vague-what-plus-no-when pattern matches the score-2 anchor.

2 / 5

Trigger Term Quality

The only terms are technical identifiers ("Codex subcommand", "/pua:p10", "$pua-p10") that a user would not naturally say; it lacks the natural phrases users would speak, fitting the score-2 anchor of one or two generic/jargon keywords missing the natural phrases.

2 / 5

Distinctiveness Conflict Risk

The trigger is a highly specific niche identifier ("pua-p10", "$pua-p10") unlikely to overlap with other skills, fitting the score-4 anchor of mostly distinct with only minor overlap risk rather than a broad clear niche that would warrant a 5.

4 / 5

Total

10

/

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