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.

63

Quality

74%

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 ./pi/package/skills/pua/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 a lean, well-structured governance contract with an explicit verification-and-switch workflow and a clear boundary table, earning high marks; only the bilingual table and cultural-narrative list add slight non-essential tokens.

DimensionReasoningScore

Conciseness

The body is lean, assumes Claude's competence, and avoids re-explaining known concepts; the bilingual governance table and six cultural-narrative bullets are minor instances that could be trimmed.

4 / 5

Actionability

The 'Required loop' gives concrete numbered steps and the governance table maps each power to a concrete implementation ('write SELF-REVIEW, evidence, residual risk'), yielding actionable guidance with only minor gaps.

4 / 5

Workflow Clarity

A clear six-step sequence with an explicit verification checkpoint (step 4) and a failure-driven feedback loop (step 5 'switch to a materially different strategy'), though error-recovery detail is light.

4 / 5

Progressive Disclosure

Under 50 lines with no bundle files needed and well-organized sections (When to use, Governance boundary, Required loop, Cultural narratives), satisfying the simple-skill exception for full marks.

5 / 5

Total

17

/

20

Passed

Description

70%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 gives a clear, well-triggered 'when' clause with natural user phrasing and a distinct niche, but the 'what' stays abstract ('high-agency governance skill') without naming concrete actions the skill performs.

Suggestions

Replace or augment 'high-agency governance skill' with 1-2 concrete actions the skill takes (e.g. 'diagnoses failures, runs verification, and accounts for residual risk before declaring completion').

Add a synonym or file/extension trigger variation (e.g. 'try-harder mode') to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

Names the domain ('PUA high-agency governance skill') and several concrete trigger behaviors but does not enumerate the specific actions the skill performs, leaning abstract on the 'what'.

3 / 5

Completeness

Explicitly answers both what ('PUA high-agency governance skill') and when ('Use for...') with concrete triggers, but the 'what' is terse and governance-abstract rather than fully explicit.

4 / 5

Trigger Term Quality

Includes natural trigger phrases users would actually say ('explicit PUA/PIP requests', 'repeated failures', 'passive/giving-up behavior', 'user frustration', 'unverified completion') plus '/pua-on', though a few synonym/extension variations are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear PUA/PIP niche with distinct, specific triggers and minimal overlap risk with unrelated skills.

4 / 5

Total

15

/

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.

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.