CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nopua-lite

NoPUA Lite — core wisdom in ~1.5k tokens. Drives AI with trust and inner motivation instead of fear. Same Daoist philosophy, minimal footprint. For personal use and small-context models.

Quality

56%

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

Quality

Content

67%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 well-structured, deliberately minimal behavioral skill: a clear 5-step failure-recovery loop, an escalation ladder tied to failure counts, and concrete delivery verification rules. Its weaknesses are mild — decorative bilingual quotes and some repetition cost tokens, and a few directives could use worked examples. The content is substantially stronger than its description, which undersells it.

Suggestions

Trim the repeated "Tool-verify, don't mouth-verify" to a single location and cut or shorten the decorative Daoist quote blocks (keeping at most one) to tighten token efficiency.

Add a one-line worked example of a 'fundamentally different' approach vs a parameter tweak, since the Act step's core requirement currently relies on the reader's interpretation.

Give the structured handoff a concrete template (verified / eliminated / narrowed scope / next directions as bullet labels with one-line examples) so the Responsible Exit step is copy-paste actionable.

DimensionReasoningScore

Conciseness

The body is mostly efficient directive prose ("Read failure signals word by word", "Changed code → build it"), but the bilingual Daoist quotes in every section, decorative flourishes ("This is pursuing wholeness, not following orders"), and repeated phrases ("Tool-verify, don't mouth-verify" appears in both Observe and Delivery Standard) could be trimmed. Not anchor 4 because the quote blocks and repetition are noticeable, not minor, padding.

3 / 5

Actionability

Concrete, executable guidance throughout: an ordered 6-item Observe checklist, a failure-count-to-action table ("3rd → Search full error + read source + list 3 different hypotheses"), and specific delivery rules ("Changed config → restart and verify", "Wrote API call → curl it") with example phrasing ("I checked A/B/C, found X, need to confirm Y"). Not anchor 5 because some directives remain abstract ("Try something fundamentally different") without worked examples, and no commands/code are given for the verification steps.

4 / 5

Workflow Clarity

The 5-step Way of Water (Stop → Observe → Turn → Act → Realize) is a clearly sequenced recovery loop with explicit checkpoints ("produce new information on failure", "clear verification criteria"), reinforced by a failure-escalation ladder and a delivery checklist. Not anchor 5 because some checkpoints are implicit — e.g. no explicit re-validate-after-fix loop for the delivery steps and no checklist for the handoff artifact.

4 / 5

Progressive Disclosure

No bundle files exist, and the single self-contained body is well organized with clear section headers, each section short enough to scan; the only external pointer is a one-level, clearly signaled link to the full version on GitHub. Not anchor 5 because the skill exceeds the under-50-line simple-skill exception (~104 lines) and quotes/references within sections are not individually navigable, though nothing here clearly belongs in a separate file.

4 / 5

Total

15

/

20

Passed

Description

28%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 is short and brandable but fails its core jobs: it states no concrete capabilities and gives no "when to use" triggers. A user (or Claude) scanning this cannot tell what the skill actually does or when to activate it. Adding an explicit trigger clause and 2-3 concrete behaviors would move it up two levels.

Suggestions

Add an explicit 'Use when...' clause naming the states this skill targets, e.g. 'Use when a task fails 2+ times, the agent is about to give up or suggest the user do it manually, or it is stuck repeating the same approach' — those triggers already exist in the body but are absent from the description.

Replace abstract framing ('Drives AI with trust and inner motivation') with 2-3 concrete capabilities, e.g. 'Provides a 5-step failure-recovery loop, a failure-count escalation ladder, and delivery verification standards (build it, curl it, paste the output)'.

Use third-person natural trigger terms users would actually say ('stuck', 'keeps failing', 'giving up', 'retry loop') so the skill is discoverable by keyword.

DimensionReasoningScore

Specificity

Phrases like "Drives AI with trust and inner motivation instead of fear" name the domain (AI agent motivation/behavior) but describe no concrete actions; the remaining text ("core wisdom in ~1.5k tokens", "minimal footprint") is packaging metadata, not capabilities. Not anchor 3 because it never lists even 1-2 concrete actions.

2 / 5

Completeness

The "what" is vague ("Drives AI with trust and inner motivation") and the "when" is entirely absent — there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the guidelines; it sits below that because the what is also only weakly defined.

2 / 5

Trigger Term Quality

"trust", "inner motivation", "Daoist philosophy", "small-context models" are conceptual jargon rather than phrases a user would naturally say when needing this skill (e.g. "stuck", "giving up", "retrying", "keeps failing"). Not anchor 3 because no relevant natural keywords are present at all.

2 / 5

Distinctiveness Conflict Risk

The NoPUA/Daoist framing is a recognizable niche, but "Drives AI with..." describes broad agent behavior that overlaps with general persistence/agency skills, and with no explicit triggers it could fire for the wrong behavioral skill. Between anchors 3 and 4, closer to 3 because overlap risk with agent-behavior skills is real.

3 / 5

Total

9

/

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-lite/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.