CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pua-reap-orphans

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

Quality

65%

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

Quality

Content

72%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 skill, but as a destructive cleanup operation it lacks explicit validation checkpoints and concrete executable commands for the scan and removal steps. Adding an explicit verify-orphan-before-remove step and the actual commands would lift the weaker dimensions.

Suggestions

Add an explicit validation checkpoint before removal, e.g. 'For each candidate record, confirm it is orphaned (no referencing agent/process) and show the evidence before deleting', with a retry loop if validation fails.

Provide the concrete executable commands or code for scanning stale PUA state and removing confirmed orphans (e.g. the exact config/state paths to inspect and the delete operation) rather than describing the steps abstractly.

Sequence the workflow as an explicit numbered list (scan -> verify each orphan -> remove confirmed only -> report command/output evidence) so the destructive-operation validation is a visible checkpoint rather than implied.

DimensionReasoningScore

Conciseness

The body is lean and free of padding or explanations of concepts Claude already knows; every line (scan, confirm-only-orphans, report evidence, preserve unknown fields) earns its place.

5 / 5

Actionability

Concrete guardrails are present (preserve unknown fields, create ~/.pua/ if missing, report evidence, no completion without command/output evidence) but no executable scan or removal commands are given, so guidance is constraint-based rather than copy-paste runnable.

3 / 5

Workflow Clarity

A rough scan-confirm-remove-report sequence is implied and 'Report evidence' is a weak checkpoint, but validation is implicit rather than an explicit verify-before-removal step; because this is a destructive/batch operation, the missing explicit validation caps the score at 3.

3 / 5

Progressive Disclosure

This is a short (under-50-line) single-purpose skill with no bundle files and no need for external references; the well-organized heading-plus-paragraphs structure satisfies the simple-skill exception at the top of the scale.

5 / 5

Total

16

/

20

Passed

Description

41%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 is distinct and jargon-specific but lacks natural trigger terms and any 'when to use' guidance, leaving it with a vague 'what' and no 'when'. Adding a 'Use when...' clause with user-facing phrasing would substantially raise completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when ...' clause stating the natural situations in which this alias should be invoked (e.g. 'Use when stale PUA agent state has accumulated and orphaned records need cleanup').

Replace CLI-internal tokens in the description with natural user-facing phrasing (e.g. 'clean up stale agent state', 'remove orphaned PUA records') so the trigger terms match what a user would actually say.

List the concrete capabilities (scan for stale state, confirm orphans, remove records, report evidence) instead of describing only the alias/mapping, to lift specificity above level 3.

DimensionReasoningScore

Specificity

Names the domain (PUA reap-orphans alias) and one concrete action (Codex subcommand mapping) but offers no list of specific capabilities, matching the 'domain plus 1-2 actions, not comprehensive' anchor rather than the more detailed level 4.

3 / 5

Completeness

It states a vague 'what' (an alias for a command) with no 'when'/'Use when' trigger guidance at all, fitting the 'vague what and no when' anchor; not level 3 because the 'what' is not a clear list of actions.

2 / 5

Trigger Term Quality

The terms present ('Codex subcommand mapping', '$pua-reap-orphans', '/pua:reap-orphans') are CLI-internal jargon rather than natural phrases a user would actually say, missing the common request language; it has a recognizable task token but lacks natural-term coverage.

2 / 5

Distinctiveness Conflict Risk

The highly specific '/pua:reap-orphans' and 'pua-reap-orphans' tokens carve a clear niche with minimal overlap risk, making it unlikely to trigger for the wrong skill.

5 / 5

Total

12

/

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-reap-orphans/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.