CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wait-what

Stop. That last message did not land: re-pitch it.

Quality

73%

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.

The body is an exemplary lean, prompt-style instruction: one sentence, three concrete directives naming a real standard and real files, with no padding. Its only weakness is mild vagueness in "a little bit of context" and the absence of a target output example.

DimensionReasoningScore

Conciseness

The body is a single sentence delivering three directives with zero padding: "give me a little bit of context, talk in ASD-STE100 Simplified Technical English, and use the ubiquitous language from `GLOSSARY.md`". Nothing explains concepts Claude already knows; every token earns its place (anchor 5).

5 / 5

Actionability

The guidance is concrete and directly followable: it names a specific standard (ASD-STE100 Simplified Technical English) and specific files (`GLOSSARY.md`, `GLOSSARY-MAP.md`) with a fallback rule. It falls short of anchor 5 because "give me a little bit of context" is unquantified and no example of the desired re-pitch shape is given.

4 / 5

Workflow Clarity

This is a single-purpose skill with one unambiguous action (re-pitch with three explicit constraints), so the simple-skill exception applies and workflow clarity scores 5. No destructive or batch operation exists, so the validation cap is not triggered.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files and no need for external references, so progressive disclosure scores 5 with well-organized content. The only referenced files (`GLOSSARY.md`, `GLOSSARY-MAP.md`) are repo files with a gracefully handled conditional fallback, not nested bundle references.

5 / 5

Total

19

/

20

Passed

Description

41%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 admirably terse and distinctive, but it omits any explicit trigger guidance and barely specifies what a "re-pitch" entails. It reads more like a conversational command than a skill description, capping completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. "Use when a reply was confusing, missed the point, or the user asks for it again in simpler terms" — its absence caps completeness at 3.

Enumerate 1-2 concrete actions instead of the bare verb "re-pitch it", e.g. "restate the answer with context, in Simplified Technical English, using the repo's ubiquitous language".

Include natural keywords and synonyms users would actually say ("I don't get it", "explain again", "simpler") so the description carries discoverable trigger terms.

DimensionReasoningScore

Specificity

"Stop. That last message did not land: re-pitch it." names a single, minimally elaborated action ("re-pitch it") with no domain and no enumeration of what the re-pitch involves. It matches the anchor "Names the domain but actions are minimal or generic" rather than anchor 3, which requires 1-2 concrete actions to be listed.

2 / 5

Completeness

A "what" is present (re-pitch the last message) but terse, and the "when" is only weakly implied by "That last message did not land" — there is no explicit trigger clause, which caps completeness at 3 per the judging guidelines. It does not reach anchor 4 because the "when" is never stated explicitly.

3 / 5

Trigger Term Quality

The only candidate phrases are "re-pitch" and "did not land"; there is no "Use when..." clause and no synonyms or variations a user would naturally say. This is one or two generic keywords with missing natural phrases (anchor 2), not the partial coverage of anchor 3.

2 / 5

Distinctiveness Conflict Risk

"Re-pitch" is a distinct niche with little overlap risk against typical skills, and the conversational framing is unlikely to fire for the wrong skill. It falls short of anchor 5 because the phrasing is conversational rather than a clearly delineated trigger set.

4 / 5

Total

11

/

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

mattpocock/skills

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.