CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nopua

The anti-PUA. Drives AI with wisdom, trust, and inner motivation instead of fear and threats. Activates on: task failed 2+ times, about to give up, suggesting user do it manually, blaming environment unverified, stuck in loops, passive behavior, or user frustration ('try harder', 'figure it out', '换个方法', '为什么还不行'). ALL task types. Not for first failures.

Quality

69%

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

Quality

Content

56%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 delivers genuinely actionable behavioral engineering — concrete report formats, failure-count-driven escalation, and specific self-challenge tables — with well-sequenced workflows and gating conditions. It is undermined by substantial philosophical padding and repetition that roughly doubles the token cost, and by a monolithic structure with no reference files despite content (Seven Ways, Agent Team Integration) that clearly warrants them and one dangling file reference.

Suggestions

Move the Seven Ways and Agent Team Integration sections into reference files (e.g. references/seven-ways.md, references/agent-teams.md), keeping a one-line-per-way index in SKILL.md; this alone would roughly halve the body.

Cut duplicated material: each Dao De Jing chapter is quoted twice, and the verify-after-fix guidance appears in at least five sections — state it once in the Delivery Checklist and reference it elsewhere.

Fix the dangling 'agents/nopua-mentor.md' reference (ship the file or remove the Mentor role row), and add one worked example of an 'inverted hypothesis' to convert the remaining abstract directives into concrete guidance.

DimensionReasoningScore

Conciseness

The ~450-line body is noticeably padded: extended parables under each Way ('A tree that fills your embrace started as a seed invisible to the naked eye...'), a full 'Why NoPUA Is More Effective Than PUA' persuasion section, and heavy repetition — the same Dao De Jing chapters (32, 64, 67, 81) are quoted twice, and 'tool-verify, don't mouth-verify' plus the verify-after-fix guidance recurs in the Proactivity Spectrum, Inner Voices, Delivery Checklist, Forge, Practice, and the Self-Check Table. It is above anchor 1 (it does not explain concepts Claude already knows; the material is skill-specific) but clearly below anchor 3's 'mostly efficient'.

2 / 5

Actionability

For an instruction-only skill the guidance is concrete and executable: exact report templates ('[NOPUA-REPORT]' with field list), a trigger confirmation string format ('[Clarity: Way of X | Because: detected Y pattern | Next: Z]'), specific behavioral tables ('Checks 50 lines of context + searches similar issues'), literal leader prompts ('Load the nopua skill before starting'), and a 5-item handoff report structure. It misses anchor 5 because some directives remain abstract and unoperationalized ('propose a hypothesis 180° opposite', 'Force yourself to...') without an example of what that looks like in practice.

4 / 5

Workflow Clarity

Multi-step processes are clearly sequenced: the Water Methodology's 5 ordered steps with an explicit gate ('Complete dimensions 1-4 before asking the user'), the Cognitive Elevation table mapping failure count to a required action (e.g. 3rd failure → 'search full error + read related source code + list 3 fundamentally different hypotheses'), and the Situation Wisdom Selector routing failure patterns through rounds to a final action. It falls short of anchor 5 because the elevation and Water steps lack explicit error-recovery loops (what to do when Step 4's 'new approach' also fails mid-cycle is only implied by re-entering the table), and the Delivery Checklist has no defined re-verification step after remediation.

4 / 5

Progressive Disclosure

Section headers are clear and navigation is possible, but the skill is a monolithic ~450-line file with zero bundle files (no references/, scripts/, or assets/ exist), while the body contains clearly separable material: the ~140-line Seven Ways section and the ~50-line Agent Team Integration section belong in reference files. The single external reference, 'Defined via agents/nopua-mentor.md', is a dangling path that does not exist in the bundle. This matches anchor 3 ('some structure, content that should be separate is inline') better than anchor 4, whose 'references mostly clear' is undermined by the missing mentor file.

3 / 5

Total

13

/

20

Passed

Description

68%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 has an excellent, explicit trigger specification — behavioral conditions, quoted frustration phrases in two languages, and a clear exclusion ('Not for first failures') — with correct third-person voice. Its weakness is that the capability statement is abstract motivational framing that never says what the skill actually contains (checklists, escalation levels, a 5-step methodology), leaving the 'what' vague and the skill broad enough to brush against debugging/verification skills.

Suggestions

Replace the abstract 'Drives AI with wisdom, trust, and inner motivation instead of fear and threats' with 2-3 concrete capabilities, e.g. 'Provides failure-escalation checklists (2nd-5th failure), a 5-step obstacle-penetration methodology, and a structured handoff report format for unsolvable tasks.'

Narrow 'ALL task types' or anchor it to the failure pattern rather than the task domain, and mention what distinguishes it from general debugging skills (e.g. 'a motivation and rigor layer to apply on top of your debugging process') to reduce overlap risk.

Drop the unexplained jargon 'The anti-PUA' or gloss it inline ('anti fear-based pressure culture'), since users outside that community would not say 'PUA' when searching for this behavior.

DimensionReasoningScore

Specificity

The 'what' is abstract: 'Drives AI with wisdom, trust, and inner motivation instead of fear and threats' names the domain (agent motivation after repeated failure) but describes no concrete actions or mechanisms — it never says the skill provides checklists, escalation levels, or a debugging methodology. It is above anchor 1 (a real domain is named, not pure 'helps with documents') but below anchor 3, which requires 1-2 concrete actions like 'Processes PDF files and extracts content'.

2 / 5

Completeness

Both 'what' and 'when' are explicitly present: 'Drives AI with wisdom, trust, and inner motivation instead of fear and threats' plus an explicit 'Activates on:' trigger list and the exclusion 'Not for first failures'. It falls short of anchor 5 because the 'what' is motivational framing rather than a concrete statement of capability (e.g., 'provides failure-escalation checklists and a 5-step recovery methodology'), but it clearly exceeds anchor 4's 'when could be more explicit' since the when-clause is highly specific.

4 / 5

Trigger Term Quality

Trigger coverage is comprehensive and natural: 'task failed 2+ times, about to give up, suggesting user do it manually, blaming environment unverified, stuck in loops, passive behavior' plus quoted user-frustration phrases ('try harder', 'figure it out', '换个方法', '为什么还不行'). These are exactly the phrases a user or agent would naturally say or exhibit, spanning both English and Chinese variants; no obvious natural term is missing for this domain.

5 / 5

Distinctiveness Conflict Risk

The trigger conditions (2+ failures, giving up, passive behavior) are fairly distinct, but 'ALL task types. Not for first failures' claims a very broad scope that overlaps with general debugging, verification, and persistence skills — the body itself lists companions like 'systematic-debugging' covering adjacent ground. It fits anchor 3 ('somewhat specific but could still overlap with similar skills') better than anchor 4, since the overlap with debugging/verification skills is more than minor.

3 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

wuji-labs/nopua

Path

skills/nopua/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.