CtrlK
BlogDocsLog inGet started
Tessl Logo

pua-trae

Trae-optimized PUA high-agency governance skill for npx skills installs. Use only for explicit PUA requests, repeated failures, user frustration, giving-up/passive behavior, or unverified completion. Do not trigger for normal first-attempt tasks.

72

Quality

87%

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

85%

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

A well-structured, actionable instruction-only skill with concrete templates and a clear validated workflow. The only real weakness is incidental rationale prose that slightly inflates the token budget without adding instructions.

Suggestions

Trim the opening rationale paragraph and the 'INTJ 版理解' aside to one line each, or fold them into the relevant sections, so the body reads as instructions rather than design notes.

Keep the diagnosis line, the confidence loop, and the delivery template as-is — they are the core actionable assets.

DimensionReasoningScore

Conciseness

Mostly efficient with well-organized tables and templates, but includes rationale prose (the intro paragraph on Trae-vs-Claude-Code differences and the 'INTJ 版理解' aside) that explains the design rather than instructing, and could be tightened.

2 / 3

Actionability

Provides concrete, copy-paste-ready artifacts: the [PUA-DIAGNOSIS] line format, the numbered 100%-confidence loop, and a full delivery template — instruction-only but fully actionable, which the rubric explicitly rewards.

3 / 3

Workflow Clarity

The 100%-confidence loop is a clearly sequenced workflow with an explicit validation checkpoint (step 3: run unit/build/lint/curl/E2E) and a feedback loop (step 4: after two failures switch to an essentially different path), plus a stop-and-confirm gate for sensitive operations.

3 / 3

Progressive Disclosure

No bundle files exist (references/scripts/assets absent) and none are referenced; under the simple-skills note, a single well-organized SKILL.md with clear headers earns a 3 without external file references.

3 / 3

Total

11

/

12

Passed

Description

90%

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 strong, specific description with explicit trigger guidance and a negative guard that distinguishes it from ordinary tasks. The main weakness is that the capability itself is framed abstractly ('high-agency governance') rather than as concrete behaviors.

Suggestions

Replace the abstract phrase 'high-agency governance skill' with one or two concrete behaviors the skill performs (e.g. 'forces a diagnosis line, a verified-evidence loop, and a SELF-REVIEW before declaring done').

Keep the strong 'Use only for ...' / 'Do not trigger ...' clauses as-is; they are the description's best feature.

DimensionReasoningScore

Specificity

Names the domain ('Trae-optimized PUA high-agency governance skill for npx skills installs') and concrete trigger scenarios, but the capability itself is described abstractly as 'high-agency governance' rather than as specific actions the skill performs, so it is not comprehensive.

2 / 3

Completeness

Explicitly answers both what ('PUA high-agency governance skill') and when via an explicit 'Use only for ...' trigger clause plus a negative 'Do not trigger for normal first-attempt tasks.'

3 / 3

Trigger Term Quality

Covers natural terms users would actually say — 'explicit PUA requests', 'repeated failures', 'user frustration', 'giving-up/passive behavior', 'unverified completion' — with good coverage of common phrasings.

3 / 3

Distinctiveness Conflict Risk

A clearly distinct niche (Trae/npx PUA governance) with a negative-trigger guard ('Do not trigger for normal first-attempt tasks') making it unlikely to fire for the wrong skill.

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.