CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pua-kpi

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

Quality

77%

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-kpi/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 body is an exemplary lean instruction-only skill: concise, niche-specific, and equipped with a verification directive guarding the config mutation. Its main gap is the absence of concrete command forms and explicit error-recovery feedback for the destructive config update.

Suggestions

Add the concrete invocation/command form for generating the report card so the guidance is copy-paste ready.

Expand the verification directive into an explicit validate->fix->retry feedback loop for the ~/.pua/config.json mutation.

Show a minimal example of preserving unknown fields (e.g., merge pattern) to make the destructive-operation handling concrete.

DimensionReasoningScore

Conciseness

The ~5-line body is lean and efficient, assumes Claude's competence, and contains no padding or explanation of concepts Claude already knows, matching the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

Concrete instruction-only guidance is present ('Load pua-pro and generate the KPI/performance report card', 'preserve unknown fields', 'create ~/.pua/ if missing') but lacks concrete command forms or copy-paste-ready invocations, fitting 'mostly executable guidance with minor gaps'.

4 / 5

Workflow Clarity

The single action is unambiguous and a verification checkpoint exists ('Do not claim completion without command/output evidence'), but the config-mutation workflow is light on explicit sequence and error-recovery feedback loops, so it does not fully reach anchor 5.

4 / 5

Progressive Disclosure

As a simple single-purpose skill under 50 lines with no need for external references, the well-organized heading-plus-body structure qualifies for the simple-skill exception to score 5.

5 / 5

Total

18

/

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 niche Codex alias with distinct triggers, but it reads as technical jargon rather than natural user language and lacks an explicit 'Use when' clause, leaving the 'when' only weakly implied. It conveys a clear 'what' but stops short of comprehensive capability listing or trigger guidance.

Suggestions

Add an explicit 'Use when...' clause stating the natural situations a user would invoke this (e.g., 'Use when generating a PUA performance/KPI report card').

Replace niche jargon ('$pua-kpi', 'Codex subcommand mapping') with natural user phrasing and include common synonyms so users would actually say these terms.

List concrete capabilities (e.g., 'load pua-pro, generate the KPI report card, update ~/.pua/config.json') instead of describing only the alias mapping.

DimensionReasoningScore

Specificity

Names the domain ('Codex subcommand mapping', 'Claude Code /pua:kpi style usage') and one concrete action ('invoke with $pua-kpi'), but coverage is minimal and not comprehensive, matching the 'names domain and 1-2 concrete actions' anchor.

3 / 5

Completeness

A clear 'what' is present (alias mapping for the pua:kpi command) but the 'when' is only weakly implied via 'invoke with $pua-kpi' with no explicit 'Use when...' clause, which caps completeness at 3 per the guidelines.

3 / 5

Trigger Term Quality

Keywords like 'pua:kpi', '$pua-kpi', 'Codex', and 'Claude Code /pua:kpi' are relevant but technical and niche, missing the natural synonyms a user would actually say, fitting 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

The skill occupies a clear niche (PUA KPI report generation) with distinct, specific triggers and minimal overlap risk with other skills.

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