CtrlK
BlogDocsLog inGet started
Tessl Logo

pua-offline

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

66

Quality

78%

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

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, fully actionable instruction set with a clear sequence and an explicit verification checkpoint. It respects token budget and needs no external references for this single-purpose skill.

DimensionReasoningScore

Conciseness

The body is five lean lines with no padding and no explanation of concepts Claude already knows; the single orienting line ("This is a Codex CLI alias...") is brief and justified.

3 / 3

Actionability

It specifies the exact file (~/.pua/config.json), exact keys and values (offline=true, feedback_frequency=0), the preservation rule, and the exact report string ([PUA OFFLINE]) — concrete, actionable guidance for an instruction-only skill.

3 / 3

Workflow Clarity

The two-step sequence (edit config, then report) is clear, edge cases are handled (create ~/.pua/ if missing, preserve unknown fields), and an explicit verification gate exists ("Do not claim completion without command/output evidence").

3 / 3

Progressive Disclosure

At under 50 lines with no need for external references, the content is well-organized into a heading, orientation, main instruction, and edge-case handling, satisfying the simple-skill allowance for a top score.

3 / 3

Total

12

/

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 identifies a clear, distinct niche but relies on internal jargon and lacks an explicit "Use when..." trigger clause, leaving the what/when pair incomplete. Specificity is limited to a single invocation rather than a list of concrete actions.

Suggestions

Add an explicit "Use when..." trigger clause (e.g., "Use when the user wants to enable PUA offline mode or silence PUA feedback") to satisfy the 'when' half of completeness.

Replace jargon like "Codex subcommand mapping" with natural user-facing terms and include common variations (e.g., "pua offline", "offline mode", "disable PUA feedback") to improve trigger term quality.

List the concrete actions the alias performs (e.g., "Enables offline mode, silences feedback, preserves config, reports status") to raise specificity beyond a single invocation.

DimensionReasoningScore

Specificity

It names the domain ("PUA offline alias for Codex") and one concrete action ("invoke with $pua-offline"), but does not list multiple specific concrete actions like the score-3 anchor requires.

2 / 3

Completeness

It states what the skill is (an alias/mapping) but provides no "Use when..." clause or equivalent explicit trigger guidance, capping completeness at 2 per the judging guidelines.

2 / 3

Trigger Term Quality

Natural command terms appear ("PUA offline", "/pua:offline", "pua-offline"), but they are wrapped in technical jargon ("Codex subcommand mapping", "alias for Codex") with only one concept and no common user-facing variations.

2 / 3

Distinctiveness Conflict Risk

The PUA-offline / Codex-alias niche with a distinct "/pua:offline" trigger is highly specific and unlikely to fire for unrelated skills.

3 / 3

Total

9

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
tanweai/pua
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.