CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

explain

Show one settled thing so the user holds it. Use when the user does not hold something already settled.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./hope/skills/explain/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 extremely lean, behavior-only instruction set with a discernible multi-phase workflow, explicit wait checkpoints, and a built-in feedback loop for follow-up questions. Its main weakness is the absence of any worked example of its central concept, the 'view', which leaves the otherwise concrete guidance without a concrete referent.

Suggestions

Include one small worked example of a view (e.g. a 5-line call-tree code fence with captions and a `# comment`), since 'view' is the skill's central artifact and is currently only described, never shown.

Show a brief sample exchange for the "I still don't get it" case — a wrong view and the redrawn view that replaces it — to make the change-the-view feedback loop concrete.

Add minimal section headers (e.g. 'Flow', 'Views', 'Follow-ups', 'When it ends') so the dense prose can be scanned without re-reading.

DimensionReasoningScore

Conciseness

The body is 10 lines of pure instruction with zero padding and no explanation of concepts Claude already knows; every clause prescribes behavior. It fully assumes the model's competence, matching the lean-and-efficient anchor.

5 / 5

Actionability

Concrete rules exist ("quote the reason given there, and mark your own inference as one", "code fence tagged with its language", "Mark undecided parts [open]"), but the central artifact — a "view" — is never shown by example, and no worked sample of any view shape (call tree, diff, SVG) is given. Guidance is specific yet incomplete, sitting between hint-level (2) and mostly-executable (4).

3 / 5

Workflow Clarity

A clear sequence is present (retrieve first → explain what it holds → name gaps → wait; answer each pull on the pulled part alone; end when the user says it back) with explicit checkpoints ("Then wait") and a feedback loop ("'I still don't get it' means the view was wrong: change the view, never add words"). It falls short of 5 because there is no explicit recovery checklist for a failed retrieve or a wrong first view.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references, and no bundle files exist; the paragraphs are logically ordered (main flow, view formats, follow-up pulls, ending, routing). It scores 4 rather than 5 because there are no section headers or signposting to aid navigation of the dense prose.

4 / 5

Total

16

/

20

Passed

Description

46%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 explicit 'Use when' trigger and states its purpose, but the language is abstract and self-referential rather than concrete. It lacks natural trigger phrases users would actually say and enumerates no concrete capabilities, making it hard to distinguish from general explanation behavior.

Suggestions

Add natural trigger phrases users would actually say, e.g. "Use when the user asks to explain how something works, says 'I don't get it', or asks why a piece of code or design is the way it is."

Name concrete actions, e.g. "Explains one settled thing at a time using views (call trees, pseudocode, file trees, diffs, SVG diagrams) built from the actual source and commit history."

State the concrete conditions that distinguish this from related skills (e.g. general Q&A, elicit, judge) in the description itself rather than only in the body.

DimensionReasoningScore

Specificity

"Show one settled thing so the user holds it" names the domain (explaining) with a single abstract action and no concrete, enumerable capabilities. It is not entirely vague (score 1) since it states what it does, but it lacks the 1-2 concrete actions needed for score 3.

2 / 5

Completeness

Both parts are present: the what ("Show one settled thing so the user holds it") and an explicit when ("Use when the user does not hold something already settled"). The when clause is explicit but expressed abstractly without concrete trigger phrases, matching anchor 4 rather than 5.

4 / 5

Trigger Term Quality

The trigger "Use when the user does not hold something already settled" describes an internal state rather than phrases a user would naturally say; natural terms like "explain", "how does X work", or "I don't understand" are absent. A trigger condition exists (above score 1), but there are essentially no natural keywords (below score 3).

2 / 5

Distinctiveness Conflict Risk

"One settled thing" and "already settled" carve out a somewhat specific niche, but the description would match nearly any request to explain or teach something, creating real overlap with general answering skills. It sits between high overlap risk (2) and minor overlap risk (4).

3 / 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

saadshahd/moo.md

Path

hope/skills/explain/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.