CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

learn-teach

Step-by-step explanation of a concept with progressive depth

Quality

71%

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 ./examples/skills/learn-teach/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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, highly actionable instruction set: the numbered steps, complete response template, depth modes, and adaptation rules give Claude everything needed to execute unambiguously. Its main weakness is token efficiency — the worked useEffect example and the topics table largely restate knowledge Claude already has and could be trimmed or moved to a reference file.

Suggestions

Trim the Example session to a skeleton or short excerpt (or move it to references/example.md) — the full useEffect walkthrough mostly demonstrates knowledge Claude already has.

Drop or shrink the 'Topics well-suited' table; the categories and examples (React hooks, closures, SOLID) are padding Claude does not need.

Consider splitting the response-format template into a reference file if the skill grows, keeping SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

The core sections (Instructions, Response format, Depth modes, Adaptation rules) are efficient, but the ~47-line useEffect Example session re-derives content Claude already knows and the Topics well-suited table lists concepts (React hooks, closures, SOLID) Claude obviously knows. This is 'mostly efficient but includes some unnecessary explanation or could be tightened' (anchor 3) rather than 2, since the padded sections are a minority and the example does demonstrate the output format.

3 / 5

Actionability

Guidance is fully concrete for an instruction-only skill: seven numbered instruction steps, a complete copy-paste-ready response format template with placeholders, three defined depth modes (--deep, --quick, default), and adaptation rules per audience level. The scoring note confirms instruction-only skills are not penalized for lacking code when guidance is this actionable; this matches the anchor 5 'specific examples cover the common cases' standard.

5 / 5

Workflow Clarity

The seven-step sequence is explicit, ordered, and mirrored one-to-one by the Response format sections, with depth modes and adaptation rules as clearly signaled variants. No validation checkpoints are needed since this is non-destructive content generation, and the single action is unambiguous — matching the simple-skill exception for a clear, complete workflow.

5 / 5

Progressive Disclosure

The body has good structure with clear, well-organized ## sections and no nested or buried references (no bundle files exist, and none are referenced, so there are no broken paths). It falls short of 5 because at ~186 lines the full Example session and Topics table are inline where a one-level-deep references/ file could hold them; this is 'good structure; most content appropriately placed; minor organization gaps' (anchor 4).

4 / 5

Total

17

/

20

Passed

Description

50%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 communicates a clear single capability but is minimal: it answers 'what' adequately while completely omitting 'when', and it lacks the natural trigger terms (teach, learn, explain) users would most likely say. All dimensions cluster at the midpoint because the description is one short generic-ish sentence.

Suggestions

Add an explicit 'Use when...' clause (e.g., "Use when the user asks to learn, be taught, or have a concept explained") to raise completeness.

Include natural trigger terms and synonyms such as "teach me", "explain", "learn", and "tutorial" to improve trigger term quality.

Enumerate a few concrete capabilities (e.g., minimal and practical examples, line-by-line breakdowns, common mistakes, depth modes) to increase specificity and distinctiveness.

DimensionReasoningScore

Specificity

"Step-by-step explanation of a concept with progressive depth" names the domain (concept explanation) and one concrete action mode (step-by-step with progressive depth), but coverage is minimal — no mention of examples, common mistakes, or depth variants. It matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive); score 4 would require several specific listed actions.

3 / 5

Completeness

The 'what' is clear (step-by-step explanation of a concept with progressive depth), but the 'when' is entirely absent — there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 2 because the 'what' is specific rather than vague.

3 / 5

Trigger Term Quality

Relevant keywords like "explanation", "step-by-step", and "concept" are present and map to phrases users naturally say ("explain X step by step"), but common variations such as "teach me", "learn", "tutorial", or "how does X work" are missing. This fits anchor 3 (some relevant keywords, missing common variations or synonyms) rather than 4 (good coverage).

3 / 5

Distinctiveness Conflict Risk

"explanation of a concept" is somewhat specific to teaching/tutoring skills, but 'concept' is unbounded and the description lacks distinct triggers, so it could overlap with other educational or explanatory skills. This matches anchor 3 (somewhat specific but could still overlap with similar skills); 4 would require mostly distinct triggers with only minor overlap risk.

3 / 5

Total

12

/

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

FlorianBruniaux/claude-code-ultimate-guide

Path

examples/skills/learn-teach/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.