pua-yes

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

Quality

61%

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-yes/SKILL.md

Quality

Content

65%

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 includes concrete config-preservation and verification guidance, but it depends on an external 'yes skill/protocol' that is neither bundled nor linked, leaving actionability and workflow underspecified. As a simple alias skill it is well-structured but not self-contained.

Suggestions

Bundle or link the referenced 'yes skill/protocol' so the alias's core behavior is self-contained and discoverable.

Make the workflow sequence explicit (number the steps: load yes skill -> switch to encouragement-first narration -> preserve config -> verify with command/output evidence).

Specify what 'verification red lines' and 'encouragement-first narration' concretely require so the guidance is copy-paste actionable rather than delegating to an undefined protocol.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient with no over-explanation of concepts Claude already knows; every line (config preservation, verification red line, narration switch) earns its place.	3 / 3
Actionability	Concrete guidance exists ('preserve unknown fields and create ~/.pua/ if missing', 'Do not claim completion without command/output evidence'), but 'Load and follow the yes skill/protocol' relies on an external protocol not defined here, leaving key details missing.	2 / 3
Workflow Clarity	Steps are present and a verification checkpoint is named, but the sequence is implicit rather than ordered, and the core actions depend on an undefined external 'yes skill/protocol', leaving checkpoints underspecified.	2 / 3
Progressive Disclosure	The body is short and organized under a heading, but it references an external 'yes skill/protocol' that is not bundled or linked, so navigation to the referenced material is unclear.	2 / 3
	Total	9 / 12 Passed

Description

57%

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, narrow niche and names the core action, but it is jargon-heavy and lacks an explicit 'when to use' trigger clause. It reads more as a technical mapping note than user-facing trigger guidance.

Suggestions

Add an explicit 'Use when ...' trigger clause (e.g., 'Use when running the /pua:yes command from Codex') to satisfy the completeness dimension.

Replace syntax like 'invoke with $pua-yes' with more natural phrasing a user would actually say.

Expand the action list beyond 'subcommand mapping' (e.g., 'maps the /pua:yes command, preserves config, switches to encouragement-first narration') to reach specificity level 3.

Dimension	Reasoning	Score
Specificity	The phrase 'Codex subcommand mapping' names the domain and a concrete action (mapping a subcommand), but it does not list multiple specific actions, so it falls short of the level-3 anchor.	2 / 3
Completeness	It states what the skill is (an alias/subcommand mapping for the yes command), but there is no 'Use when...' clause or explicit trigger guidance, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Terms like 'Codex', '/pua:yes', and 'pua-yes' are relevant and somewhat natural, but the syntax-heavy 'invoke with $pua-yes' is technical jargon and common variations are missing, matching the level-2 anchor.	2 / 3
Distinctiveness Conflict Risk	The very narrow niche of a Codex alias for a specific Claude Code command, with distinctive triggers like '/pua:yes' and '$pua-yes', makes it unlikely to conflict with other skills.	3 / 3
	Total	9 / 12 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-yes/SKILL.md
Commit: 3fd4e5a

Reviewed: 2 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.