CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wait-what

停一下:刚才那条消息没有说清楚,重新表述一遍。

Quality

76%

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/productivity/wait-what/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

A lean, single-purpose prompt-style skill whose body gives concrete and mostly complete instructions: what a restatement must include (context, ASD-STE100, conversation language, ubiquitous language) and conditional glossary lookup. The only weakness is unspecified handling of GLOSSARY-MAP.md's format and the missing-glossary fallback, which keeps actionability at 4 rather than 5.

DimensionReasoningScore

Conciseness

The body is a single compact instruction (~2 sentences) with zero padding: it states the constraints directly (「遵循 ASD-STE100 简化技术英语的标准,用目前对话的语种,并使用 GLOSSARY.md 中的 ubiquitous language」) without explaining concepts Claude already knows. Every token earns its place; the only near-redundancy (「context 背景」) is a bilingual gloss, not over-explanation, which fits the 5 anchor ('lean and efficient; every token earns its place') better than the 4 anchor's 'minor instances of over-explanation that could be trimmed'.

5 / 5

Actionability

Concrete, specific guidance: a named standard (ASD-STE100), a named language rule (「用目前对话的语种」), named files (GLOSSARY.md, GLOSSARY-MAP.md), and a conditional branch (「如果仓库有 GLOSSARY-MAP.md,先按它指向的 context 读取正确的 GLOSSARY.md」). Not a 5 because the GLOSSARY-MAP.md format is never described ('按它指向的 context' assumes structure Claude must guess) and there is no fallback when neither glossary file exists.

4 / 5

Workflow Clarity

This is a simple, single-purpose skill (deliver a restatement request under stated constraints), and the single action is unambiguous — the simple-skill exception applies. The one micro-sequence is explicitly ordered (「先按它指向的 context 读取」), and no destructive/batch operation exists, so the validation cap does not apply. A 4 would require ambiguous sequencing, which is not the case.

5 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), so there is nothing to misplace: the body references only workspace files (GLOSSARY.md / GLOSSARY-MAP.md) the skill operates on, not skill-bundle references. Under the scoring note for sub-50-line skills needing no external references, a well-organized single-instruction body scores 5; there is no wall of text and no nested references.

5 / 5

Total

19

/

20

Passed

Description

48%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 conveys one concrete action — demanding a restatement of the last unclear message — but it is phrased as a second-person imperative instead of third person, provides no explicit 'Use when…' trigger clause (capping completeness at 3), and covers only the core phrasing without synonyms. Result: mediocre specificity and trigger quality despite a distinctive niche.

Suggestions

Rewrite the description in third person, e.g. 「要求重新表述上一条含糊的消息:补充背景、遵循 ASD-STE100、使用 GLOSSARY.md 的 ubiquitous language」 — the current imperative 「停一下…重新表述一遍」 reads as second person, which cost specificity a point.

Add an explicit trigger clause, e.g. 「当上一条消息含糊、术语混乱或缺少上下文时使用」 (use when the last message is unclear, ambiguous, or missing context) — its absence caps completeness at 3.

Include natural trigger synonyms so users' phrasing matches, e.g. 「没看懂」「再说清楚一点」「clarify」「rephrase」, improving trigger-term coverage from 3 toward 4-5.

DimensionReasoningScore

Specificity

The description names the domain (unclear messages: 「刚才那条消息没有说清楚」) and one concrete action (「重新表述一遍」), which would anchor at 3 ('1-2 concrete actions'), but it is written as a second-person imperative (「停一下…重新表述一遍」) rather than third person, incurring the rubric's -1 voice penalty. Not a 1: the action is concrete and specific, not pure abstraction.

2 / 5

Completeness

The 'what' is clear — demand a restatement of the last unclear message — but there is no 'Use when…' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3. The condition is only weakly implied by 「刚才那条消息没有说清楚」; a 4 would require an explicit 'when' clause.

3 / 5

Trigger Term Quality

Some natural, relevant phrases are present (「刚才那条消息没有说清楚」, 「重新表述」) that a user might say, but common variations and synonyms are missing (e.g., 「没看懂」, 「再说一遍」, 「解释一下」, 'clarify', 'rephrase'). This matches the 3 anchor ('some relevant keywords but missing common variations or synonyms'); it is above 2 (the terms are not generic) but below 4 (coverage is thin, with no synonyms at all).

3 / 5

Distinctiveness Conflict Risk

The action described (restating the last unclear message) is a clear niche with little overlap risk against other skills, and the phrasing (「停一下」+「重新表述」) is distinctive. Not a 5 because the description lacks distinct explicit trigger phrases (no 'use when' terms), leaving minor overlap risk with general clarification/explanation skills.

4 / 5

Total

12

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

vinvcn/mattpocock-skills-zh-CN

Path

skills/productivity/wait-what/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.