CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pua-teardown-all

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

Quality

53%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./codex/pua-teardown-all/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

51%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 concise and uncluttered, but it is an instruction-only skill whose guidance stays abstract: no executable commands, no concrete state/file targets, and no validate-then-retry loop for a destructive teardown operation.

Suggestions

Add concrete, executable steps with specific commands/paths, e.g. the exact files and directories to remove and the config-preservation command for ~/.pua/config.json.

Insert an explicit validation checkpoint (e.g. verify state was released and confirm config still parses) with a fix-and-retry loop before declaring completion.

Tighten the opening line by removing the alias restatement, since the description already conveys it.

DimensionReasoningScore

Conciseness

The body is lean and does not explain concepts Claude already knows; the only minor trim is the opening restatement that 'This is a Codex CLI alias for the Claude Code /pua:teardown-all command.'

4 / 5

Actionability

It gives high-level direction ('Release all active PUA agent state and loop state according to the teardown protocol') with no concrete commands, code, or specific file/state identifiers to execute against.

2 / 5

Workflow Clarity

This destructive skill (deleting files, modifying ~/.pua/config.json) has a rough implied sequence but no explicit validation/verify-retry feedback loop, so it falls well below the destructive-skill checkpoint requirement.

2 / 5

Progressive Disclosure

A short, single-purpose skill under 50 lines with no external references needed; the brief sections are well-organized, meeting the simple-skill exception.

5 / 5

Total

13

/

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 clear niche but reads as an alias-mapping statement rather than a capability description, with no concrete actions and no 'Use when' trigger guidance. It uses technical jargon instead of natural user phrases.

Suggestions

Add a 'Use when ...' clause naming the natural trigger phrases a user would say when they need to tear down PUA state (e.g. 'Use when the user wants to release or reset PUA agent and loop state').

Replace the alias-mapping framing with concrete actions, e.g. 'Releases active PUA agent state and loop state, explains destructive cleanup, and deletes files according to the teardown protocol.'

Include common user synonyms (e.g. 'reset', 'clean up', 'stop agents') alongside the technical tokens to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain ('Codex subcommand mapping for Claude Code /pua:teardown-all style usage') but lists no concrete actions — it describes an alias mapping rather than what the teardown actually does.

2 / 5

Completeness

It states a vague 'what' (alias mapping) but provides no 'Use when...' or equivalent trigger clause, which the guidelines cap at 3 and the near-absence of 'when' pushes lower.

2 / 5

Trigger Term Quality

Keywords like 'PUA teardown', 'Codex subcommand mapping', and '$pua-teardown-all' are technical jargon; users would not naturally say these phrases when they need this skill.

2 / 5

Distinctiveness Conflict Risk

The PUA teardown niche with specific tokens like '/pua:teardown-all' is mostly distinct from other skills with only minor overlap risk.

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-teardown-all/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.