Progressive concept teaching through three depth levels (Core → Mechanics → Deep Dive). Creates diagrams, provides annotated code walkthroughs from the current codebase, and builds explanations from fundamentals to production internals. Triggers: "teach me about [pattern/concept]", "how does [architecture/pattern] work", "walk me through [this implementation]", "tutorial on [concept]", "deep dive into [system/pattern]", "help me understand [this design]" Use when: user requests multi-level learning about code patterns, architecture, or implementation mechanics with checkpoint-based progression. Not for: quick answers, single-sentence explanations, code fixes, or "what does this line do" questions—those are standard assistance.
98
100%
Does it follow best practices?
Impact
97%
1.44xAverage score across 5 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels across all dimensions. It clearly articulates a unique teaching methodology with specific depth levels, provides natural trigger phrases users would actually say, and explicitly defines both when to use it and when not to use it. The 'Not for' clause is particularly valuable for disambiguation.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Progressive concept teaching through three depth levels', 'Creates diagrams', 'provides annotated code walkthroughs', 'builds explanations from fundamentals to production internals'. Clear methodology with named levels (Core → Mechanics → Deep Dive). | 3 / 3 |
Completeness | Explicitly answers both what (progressive teaching with diagrams, code walkthroughs, three depth levels) AND when ('Use when: user requests multi-level learning about code patterns, architecture, or implementation mechanics'). Also includes helpful 'Not for' clause to clarify boundaries. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger phrases users would say: 'teach me about', 'how does X work', 'walk me through', 'tutorial on', 'deep dive into', 'help me understand'. These are realistic user phrasings with good variation. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche with distinct methodology (three-level progression, checkpoint-based). The 'Not for' clause explicitly distinguishes from standard code assistance, reducing conflict risk with general coding skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that efficiently teaches a structured pedagogical approach. It excels at providing concrete examples, clear workflow sequencing with checkpoints, and appropriate progressive disclosure through external file references. The scope constraints (local codebase only, no external URLs, credential redaction) add important safety boundaries.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, using bullet points and structured formatting without explaining concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides concrete, executable guidance with specific format examples, checkpoint dialogue samples, and clear file:line reference conventions. The three-level workflow is fully specified with copy-paste ready templates. | 3 / 3 |
Workflow Clarity | The multi-step teaching workflow is clearly sequenced (Level 1 → Checkpoint → Level 2 → Checkpoint → Level 3 → Exit) with explicit validation checkpoints after each level and clear exit conditions. | 3 / 3 |
Progressive Disclosure | Excellent structure with a quick reference at top, main content appropriately scoped, and clear one-level-deep references to supporting files (trigger-reference.md, examples.md, visualization-guide.md) for detailed content. | 3 / 3 |
Total | 12 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents