Build a personalized learning roadmap with milestones and practice checkpoints
40
37%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./teaching/skills/create-learning-path/SKILL.mdQuality
Discovery
32%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 conveys the core concept of building learning roadmaps but lacks the specificity and completeness needed for reliable skill selection. It is missing a 'Use when...' clause entirely, which is critical for Claude to know when to invoke this skill. The trigger terms are reasonable but incomplete, missing common synonyms users might naturally use.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to learn a new skill, asks for a study plan, learning path, curriculum, or wants structured guidance for skill development.'
Include more natural trigger terms users would say, such as 'study plan', 'learning path', 'curriculum', 'course plan', 'skill development', 'how to learn X'.
List more specific concrete actions, e.g., 'Assesses current skill level, sequences topics by difficulty, generates practice exercises, and sets milestone checkpoints to track progress.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (learning roadmaps) and mentions some components (milestones, practice checkpoints), but doesn't list multiple concrete actions like 'assess skill gaps, sequence topics, generate exercises, track progress'. | 2 / 3 |
Completeness | Describes what it does (builds a learning roadmap) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also only moderately detailed, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes some relevant terms like 'learning roadmap', 'milestones', and 'practice checkpoints', but misses common user phrases like 'study plan', 'learning path', 'curriculum', 'skill development', or 'course plan'. | 2 / 3 |
Distinctiveness Conflict Risk | The concept of a 'personalized learning roadmap' is somewhat specific, but could overlap with general planning skills, project management skills, or educational content creation skills without clearer boundaries. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable high-level structure for creating learning paths but lacks the concrete, actionable detail needed to guide Claude effectively. The workflow reads as a generic process description rather than specific instructions with examples, templates, or sample outputs. The organization is clean but the content needs substantial enrichment to be truly useful.
Suggestions
Add a concrete example of a completed learning path (e.g., a sample week-by-week plan for a specific topic) so Claude has a clear template to follow.
Include a specific output format or schema (e.g., markdown table with columns for Week, Topic, Practice Exercise, Milestone, Review Criteria) to make the output actionable.
Add explicit questions to ask the user during the baseline assessment step (e.g., 'What is your current experience level?', 'How many hours per week can you dedicate?') to make the workflow concrete.
Include a validation checkpoint after the initial plan is generated—e.g., present the plan to the user for confirmation before finalizing, with criteria for what to adjust.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief and doesn't over-explain concepts Claude already knows, but phrases like 'Building capability in a topic over multiple sessions' and some of the guardrails are somewhat generic and could be tightened. | 2 / 3 |
Actionability | The workflow is entirely abstract and descriptive—there are no concrete examples, templates, sample outputs, or specific formats. Steps like 'Assess baseline knowledge' and 'Sequence topics' describe rather than instruct, giving Claude no executable guidance on what a learning path should actually look like. | 1 / 3 |
Workflow Clarity | Steps are listed in a logical sequence and step 5 includes a review/adjustment step, but there are no validation checkpoints, no feedback loops for when assessments reveal gaps, and no concrete criteria for when to proceed between steps. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines with no need for external references, the content is well-organized into clear sections (Trigger, Workflow, Tools, Guardrails, Output) that are easy to navigate. | 3 / 3 |
Total | 8 / 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.
b8f2564
Table of Contents
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.