CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nopua-zh

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-zh/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 machinery — escalation ladders, checklists, report templates, and team protocols — but wraps it in heavy repetitive motivational prose that roughly doubles the token cost, and crams all of it into one monolithic file with an internal inconsistency (五道 heading over seven 道) and unreconciled escalation systems.

Suggestions

Consolidate the repeated verify/search/don't-stop directives (three beliefs, inner voice list, delivery checklist, honesty table) into one canonical section — the same instruction currently appears 4+ times, which is the main token waste.

Move the seven 道 sections and the Agent Team integration protocol into reference files (e.g. references/dao.md, references/team-protocol.md) and keep a one-line index plus the selector table in SKILL.md.

Fix the 五道/seven-道 mismatch and explicitly reconcile the 认知升级 failure-count ladder with the 情境智慧选择器 rounds and per-道 triggers into a single decision path.

DimensionReasoningScore

Conciseness

The same directives (verify with tools, search before asking, check for similar bugs) are restated across the 三个信念, 内在声音, 交付自检清单, 诚实自检表, and seven 道 sections, each burying 2-4 actionable bullets under Taoist quotes and metaphor ("水遇到石头不会硬碰。它绕过去…"). Several sections are padded redundancy, matching anchor 2; not 1 because concrete, distinct guidance is present throughout, and not 3 because the repetition is extensive rather than occasional.

2 / 5

Actionability

As an instruction-only skill, it supplies mostly executable guidance: the ordered 止-观-转-行-悟 methodology with per-step actions ("搜索完整报错信息", "出错文件上下文 50 行"), a 7-item checklist with per-task-type equivalents, a concrete [NOPUA-REPORT] message template, and specific Leader/Teammate protocols. Anchor 4 fits; not 5 because a sizable fraction of the body is abstract motivational prose rather than instruction, and not 3 because the concrete mechanisms (checklists, templates, escalation actions) are complete and specific.

4 / 5

Workflow Clarity

Multi-step processes are clearly sequenced with checkpoints: the 认知升级 table maps failure count to a level and required action, the 水的方法论 gives an ordered 5-step flow with a gate ("维度 1-4 完成前不要急于向用户提问"), and the 负责任的退出 section defines a 5-item handoff report; verification is repeatedly enforced ("用工具验证,不要用嘴验证") with feedback loops ("停下来,换方向"). Score 4 rather than 5 because the "五道" section actually lists seven 道 and three competing escalation systems (认知升级 table, 情境智慧选择器 rounds, per-道 triggers) are never reconciled into one governing sequence.

4 / 5

Progressive Disclosure

No references/, scripts/, or assets/ files exist — everything is inlined in a single ~450-line SKILL.md. Section headers and tables give it real structure, but clearly separable material (the seven 道 sections, the Agent Team integration protocol) is inlined rather than split into referenced files, matching anchor 3. Not 2 because the body is well-sectioned and navigable rather than minimally structured; not 4 because nothing is offloaded to separate files and the only file mentions (agents/nopua-mentor.md, superpowers skills) are external, not part of this bundle.

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 excellent, comprehensive trigger coverage with an explicit activation clause and a clear exclusion ("Not for first failures"), but the capability statement is abstract jargon ("The anti-PUA", "Drives AI with wisdom") that never says what the skill concretely does, and "ALL task types" invites conflict with other behavioral skills.

Suggestions

Replace "Drives AI with wisdom, trust, and inner motivation instead of fear and threats" with 2-3 concrete capabilities, e.g. "Provides a failure-escalation methodology (cognitive levels per failure count), a 7-item self-diagnostic checklist, and a structured handoff report format for unresolved problems."

Narrow "ALL task types" to the actual decision boundary, e.g. "Any task type after repeated failures or passive/give-up behavior" — this reduces overlap with general debugging or persistence skills.

State the key deliverable outcome explicitly, such as "produces a structured handoff report when 7-item checklist is exhausted", so users can distinguish it from the PUA skill it opposes.

DimensionReasoningScore

Specificity

"Drives AI with wisdom, trust, and inner motivation instead of fear and threats" names the domain but the action is generic; no concrete capability (checklists, methodology, escalation ladder) is stated. It matches anchor 2 rather than 3 because not even 1-2 concrete actions are named — the rest of the description is trigger conditions, not capabilities.

2 / 5

Completeness

The 'when' is fully explicit ("Activates on: … Not for first failures") but the 'what' ("Drives AI with wisdom, trust, and inner motivation") is abstract — both are present yet one could be more explicit, matching anchor 4. Not 5 because the 'what' states no concrete capability; not 3 because the 'when' clause is explicit and concrete rather than missing or implied.

4 / 5

Trigger Term Quality

"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', '换个方法', '为什么还不行')" covers natural user phrases comprehensively, including synonyms and both English and Chinese variants. Anchor 5 fits; it exceeds anchor 4 because synonyms and quoted frustration phrases are explicitly included.

5 / 5

Distinctiveness Conflict Risk

"ALL task types" plus broad behavioral triggers like "passive behavior" and "stuck in loops" create real overlap risk with general agent-behavior skills, but "The anti-PUA" positioning and the "Not for first failures" boundary add distinctiveness — somewhat specific yet overlapping, matching anchor 3. Not 2 because triggers like "suggesting user do it manually" are fairly distinctive signals; not 4 because the declared scope is maximally broad.

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