CtrlK
BlogDocsLog inGet started
Tessl Logo

learn

Use this skill when the user wants intellectual understanding — learning how or why something works, not getting a task done or soliciting Claude's judgment. Trigger for: - Explicit learning requests: teach, explain, ELI5, walk me through, quiz me, flashcards, "I'm rusty on"; definitions ("what is X") - Terse concept names implying "help me understand this": "Galois theory," "transformers, from scratch" - Confusion signals: "won't stick," "keep mixing these up," "not getting it" - Learning-path questions: prerequisites, sequencing, what to study before X - Conceptual questions about mechanisms, causes, or dynamics Don't trigger for: - Tasks: coding, writing, calculation, translation, factual lookup, news updates - Personal troubleshooting; resource/textbook recommendations - Claude's evaluative verdict: opinion prompts ("do you think X", "settle this", "honest take", "is X dead / still taken seriously") and interpretive takes ("was X really as harsh as people say")

72

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A high-quality instructional skill body: actionable, well-sequenced, and well-organized. Its only real weakness is conciseness — the closing recap section duplicates earlier guidance and could be tightened.

Suggestions

Trim the 'What consistently goes wrong' section where it restates earlier points (over-questioning, hidden answers, jargon-as-skip-signal, overdelivering visuals); keep only anti-patterns not already covered to remove redundancy.

Consolidate 'Showing, not just telling' with the visual guidance already in 'A toolkit of moves' to reduce re-explanation of the same scaffold idea.

DimensionReasoningScore

Conciseness

The body is information-dense and avoids explaining basics Claude already knows, but the 'What consistently goes wrong' recap restates points made earlier (over-questioning, hidden answers, jargon-as-skip-signal, overdelivering visuals), adding length that could be trimmed.

2 / 3

Actionability

Concrete, specific guidance throughout: example calibrating questions ('Is it the setup or the mechanics that's throwing you?'), named moves with examples, an explicit widget-call sequence (read_me then show_widget with prose outside the call), and ready-to-use response lines.

3 / 3

Workflow Clarity

Clear sequenced flow — diagnose first, one-step-per-turn rhythm, then detect completion — with explicit checkpoints (a diagnosis gate, done-signals like 'explains it back correctly') and branch handling for stuck vs impatient learners.

3 / 3

Progressive Disclosure

Self-contained and well-organized into clear headed sections with an overview opening paragraph; no external references are needed and none are nested, so the single-file structure is appropriate for a skill of this size.

3 / 3

Total

11

/

12

Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-structured description: it states purpose, gives rich natural triggers, and explicitly fences off non-triggering cases for distinctiveness. The only weakness is that capabilities are implied through trigger terms rather than enumerated as concrete actions.

Suggestions

Add a brief capability clause that enumerates concrete actions the skill performs (e.g., 'Diagnoses where the learner is stuck, guides with hints and worked parallel examples, creates flashcards and quizzes, and signals when understanding is solid') so capabilities are stated, not just implied by triggers.

Lead the 'what it does' sentence with verbs naming the skill's pedagogical moves, keeping the strong trigger and don't-trigger lists as supporting context.

DimensionReasoningScore

Specificity

Names the domain clearly ('intellectual understanding — learning how or why something works') but frames capabilities as trigger terms (teach, explain, quiz, flashcards) rather than enumerating the concrete pedagogical actions the skill performs, so the capability list is implied rather than comprehensive.

2 / 3

Completeness

Explicitly states what the skill is for and when to use it via a 'Use this skill when...' clause supported by detailed 'Trigger for' and 'Don't trigger for' lists, answering both 'what' and 'when'.

3 / 3

Trigger Term Quality

Rich, natural phrases users actually say ('teach, explain, ELI5, walk me through, quiz me, flashcards', 'I'm rusty on', 'what is X', 'won't stick', 'keep mixing these up') plus a 'Don't trigger for' list gives broad coverage of real-world phrasings.

3 / 3

Distinctiveness Conflict Risk

Carves a clear niche (learning/understanding) and explicitly excludes adjacent cases (coding, writing, calculation, translation, factual lookup, recommendations, opinion/evaluative prompts), making conflicts with other skills unlikely.

3 / 3

Total

11

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
UnicomAI/wanwu
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.