pua-flavor

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

Quality

53%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./codex/pua-flavor/SKILL.md

Quality

Content

48%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 includes a validation checkpoint for its config-writing operation, but it stops short of executable guidance (no commands/code for setting a flavor) and references a 'flavor reference' that is not present in the bundle. Structural organization is minimal.

Suggestions

Add concrete, executable steps or commands for listing and setting a flavor in ~/.pua/config.json so the guidance is copy-paste ready.

Either add the referenced 'flavor reference' file to a references/ bundle or remove the dangling reference and inline the essential flavor list.

Add light section headers (e.g., '## Usage', '## Guardrails') to give the simple body clearer organization.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: each of the ~6 lines names concrete files, paths, or guardrails with no padding or explanation of concepts Claude already knows. Not 4 because there is no noticeable over-explanation to trim.	5 / 5
Actionability	Names concrete targets (~/.pua/config.json, create ~/.pua/) and constraints (preserve unknown fields, don't claim completion without evidence) but provides no executable code, commands, or examples for actually setting a flavor. Not 4 because it lacks copy-paste-ready specifics; not 2 because the paths and constraints are concrete, not just high-level hints.	3 / 5
Workflow Clarity	An implicit choose/set sequence is present and a destructive config change is guarded by a validation checkpoint ('Do not claim completion without command/output evidence') plus safety rules (preserve unknown fields, mkdir if missing). Not 5 because the sequence is not explicitly enumerated and there is no fix/retry feedback loop; not 3 because a validation checkpoint is present rather than absent.	4 / 5
Progressive Disclosure	Minimal structure with no section headers, and 'Read the flavor reference' points to a reference file that does not exist in any bundle directory. Not 2 because it is not a monolithic wall of misfiled inline content; not 4 because references are neither clearly signaled nor real and there is no section organization.	3 / 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 identifies a distinct, narrowly-scoped Codex alias but is only moderately complete: it states what the skill is and how to invoke it while omitting explicit 'Use when...' trigger guidance. Specificity and trigger-term coverage are adequate rather than comprehensive.

Suggestions

Add an explicit 'Use when...' clause naming the natural situations a user would invoke this alias (e.g., 'Use when the user wants to pick or change a pua flavor').

Enumerate 1-2 more concrete actions the alias performs (e.g., 'lists available flavors, sets the active flavor') to lift specificity.

Include common trigger synonyms or variants beyond the exact '/pua:flavor' command name for better trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Codex alias for Claude Code /pua:flavor) and 1-2 concrete actions (subcommand mapping, invoke), but coverage is not comprehensive. Not 4 because it doesn't list several specific actions; not 2 because it does more than just name the domain.	3 / 5
Completeness	Gives a clear-ish 'what' (PUA flavor alias for Codex) but only weakly implies 'when' (when using /pua:flavor) with no explicit 'Use when...' clause, which caps completeness at 3 per the rubric guideline. Not 4 because no explicit trigger guidance; not 2 because the 'what' is more than vague.	3 / 5
Trigger Term Quality	Includes the specific command tokens 'Claude Code /pua:flavor' and '$pua-flavor' but offers no synonyms or common variants beyond the exact name. Not 4 because keyword coverage is thin (just the one exact command name), not 2 because the terms are specific rather than generic.	3 / 5
Distinctiveness Conflict Risk	Describes a clearly named, narrow niche (a specific alias for a specific command) with distinct triggers and minimal conflict risk. Not 4 because it is more than 'mostly distinct' — the alias name is uniquely scoped.	5 / 5
	Total	14 / 20 Passed

Validation

100%

Warnings & errors only

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-flavor/SKILL.md
Commit: ac50267

Reviewed: 10 days ago

Table of Contents

Discovery Implementation Validation

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.