CtrlK
BlogDocsLog inGet started
Tessl Logo

pua

Pi-compatible PUA high-agency governance skill. Use for explicit PUA/PIP requests, repeated failures, passive/giving-up behavior, user frustration, or unverified completion. Pair with /pua-on extension command when persistent pressure is desired.

76

Quality

95%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

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

A tight, well-organized instruction-only skill body that delivers concrete actionable governance guidance with a clear verification-and-feedback loop and no token waste. It fully meets the rubric across conciseness, actionability, workflow clarity, and progressive disclosure.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no padding explaining concepts, compact table and one-line cultural narratives, every line earning its place.

3 / 3

Actionability

Gives concrete executable guidance for an instruction-only skill: a specific diagnosis format ('[PUA-DIAGNOSIS] Problem / evidence / next action'), a verification menu ('build, test, lint, curl, E2E'), and explicit boundary rules ('ask before deleting files...').

3 / 3

Workflow Clarity

The 'Required loop' is a clear six-step sequence with an explicit verification step and a feedback loop ('After two failures on the same path, switch to a materially different strategy').

3 / 3

Progressive Disclosure

No bundle files are provided, so the single self-contained file is evaluated on organization; its well-structured sections (When to use, Governance boundary, Required loop, Cultural narratives) satisfy the simple-skill note.

3 / 3

Total

12

/

12

Passed

Description

90%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-structured description that clearly answers what the skill is and when to use it, with strong natural trigger coverage and a distinct niche. The only weak spot is specificity, which leans on a single concrete action (the extension command) rather than a comprehensive list of concrete capabilities.

DimensionReasoningScore

Specificity

Names the domain ('PUA high-agency governance skill') and one concrete action ('Pair with /pua-on extension command'), but does not list multiple specific concrete actions like the anchor-3 PDF example.

2 / 3

Completeness

Explicitly states both what it is ('Pi-compatible PUA high-agency governance skill') and when to use it via a 'Use for ...' clause with concrete triggers.

3 / 3

Trigger Term Quality

The 'Use for' clause covers natural triggers a user would express — 'explicit PUA/PIP requests, repeated failures, passive/giving-up behavior, user frustration, or unverified completion' — matching the good-coverage anchor.

3 / 3

Distinctiveness Conflict Risk

The high-agency pressure/governance niche with triggers like 'unverified completion' and 'passive/giving-up behavior' is distinct and unlikely to fire for unrelated skills.

3 / 3

Total

11

/

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.