Build a personalized learning roadmap with milestones and practice checkpoints
50
37%
Does it follow best practices?
Impact
Pending
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 a reasonable concept but is incomplete and insufficiently detailed. It lacks a 'Use when...' clause, misses common user trigger terms like 'study plan' or 'learning path', and doesn't enumerate enough concrete actions to clearly distinguish it from other planning or education-related skills.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks for a study plan, learning path, curriculum, or wants to learn a new skill or topic systematically.'
Include more natural trigger terms users would say, such as 'study plan', 'learning path', 'curriculum', 'skill development', 'course outline', or 'how to learn X'.
List additional concrete actions to improve specificity, e.g., 'Assesses current skill level, sequences topics by difficulty, generates practice exercises, and sets time-based milestones.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names a 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 | It describes what the skill 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, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also only moderately detailed. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords like 'learning roadmap', 'milestones', and 'practice checkpoints', but misses common user variations such as 'study plan', 'curriculum', 'learning path', 'skill development', or 'course outline'. | 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 framework for creating learning paths but lacks the concrete, actionable detail needed to guide Claude effectively. The workflow is entirely abstract with no examples of what a learning plan should look like, no templates, and no specific formats. The structure and conciseness are adequate, but the skill reads more like a checklist of ideas than executable instructions.
Suggestions
Add a concrete example of a completed learning roadmap (e.g., a sample week-by-week plan for learning Python) so Claude knows the expected output format and level of detail.
Include a template or schema for milestone definitions, practice assignments, and the progress review rubric mentioned in the Output section.
Add specific questions to ask the user during baseline assessment (e.g., 'What's your current experience level?', 'How many hours per week can you dedicate?') to make the Ask user tool usage actionable.
Include a validation/feedback loop: after presenting the plan, explicitly instruct Claude to ask the user to confirm feasibility and adjust before finalizing.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief and doesn't over-explain concepts Claude already knows, but some steps like 'Assess baseline knowledge and target outcomes' are generic enough to be unnecessary filler. It could be tighter with more specific guidance. | 2 / 3 |
Actionability | The skill provides only vague, abstract direction with no concrete examples, templates, or specific formats. There are no sample learning plans, no example milestone structures, no rubric templates—it describes rather than instructs. | 1 / 3 |
Workflow Clarity | Steps are listed in a logical sequence, but there are no validation checkpoints, no feedback loops for adjusting the plan if milestones aren't met, and no concrete criteria for when to move between steps. The 'Review progress and adjust pacing' step is too vague. | 2 / 3 |
Progressive Disclosure | For a simple, short skill under 50 lines with no need for external references, the content is organized into clear, well-labeled 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.
7dd9fea
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.