create-learning-path

Build a personalized learning roadmap with milestones and practice checkpoints

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./teaching/skills/create-learning-path/SKILL.md

Quality

Content

72%

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

The content is a clean, well-organized, token-efficient instruction skill, but its workflow steps are abstract rather than concrete and lack explicit validation checkpoints between phases. Grounding the steps with example outputs or specific criteria would push actionability and workflow clarity higher.

Suggestions

Make workflow steps more concrete by attaching example deliverables or criteria, e.g. for 'Define milestone projects' add a one-line example milestone and acceptance check.

Add an explicit validation/checkpoint between phases (e.g. 'Confirm milestones fit the schedule before sequencing practice exercises') to strengthen workflow clarity.

Specify how 'Use Ask user tool' should be applied — which questions to ask at which step — so the Tools section is actionable rather than a bare pointer.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient with no concept-padding or redundant explanation; every section (Trigger, Workflow, Tools, Guardrails, Output) carries only directive content, assuming Claude's competence throughout.	3 / 3
Actionability	Steps are sequenced and directive but remain high-level and abstract ('Assess baseline knowledge', 'Sequence topics', 'Define milestone projects') with no concrete examples, templates, or specific criteria — guidance that is actionable in shape but incomplete in detail.	2 / 3
Workflow Clarity	The five numbered steps form a clear sequence and step 5 ('Review progress and adjust pacing') acts as a feedback loop, but validation checkpoints are implicit rather than explicit and there is no checkpoint gating between phases.	2 / 3
Progressive Disclosure	The skill is under 50 lines with no external references and is organized into clearly labeled sections (Trigger, Workflow, Tools, Guardrails, Output); per the simple-skills scoring note this satisfies progressive disclosure.	3 / 3
	Total	10 / 12 Passed

Description

50%

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 is clear and reasonably specific about what the skill does, but it omits any explicit trigger guidance, which caps both completeness and trigger-term quality. Adding a 'Use when...' clause with natural user phrases would lift the description across all dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to build a study plan, learn a topic over time, or create a skill roadmap with milestones.'

Include natural user-facing variations like 'learning plan', 'study schedule', or 'skill roadmap' alongside 'learning roadmap' to improve trigger-term coverage.

Tighten distinctiveness by framing the niche more sharply (multi-session capability building with practice checkpoints) so it does not overlap with generic planning skills.

Dimension	Reasoning	Score
Specificity	The description names the domain ('learning roadmap') and a few actions ('Build', 'milestones', 'practice checkpoints'), but the action set is not comprehensive — it does not enumerate the multiple concrete actions a full scoring-3 example would.	2 / 3
Completeness	It answers 'what' (build a personalized learning roadmap with milestones and checkpoints) but never states 'when' to use it; per the judging guidelines, a missing 'Use when...' clause caps completeness at 2.	2 / 3
Trigger Term Quality	Phrases like 'learning roadmap', 'milestones', and 'practice checkpoints' are somewhat natural, but there is no 'Use when...' clause and no coverage of common variations users might say (e.g., 'study plan', 'learning plan', 'skill roadmap').	2 / 3
Distinctiveness Conflict Risk	The learning/education niche gives it some specificity, but it could still overlap with general planning, goal-setting, or roadmap skills without explicit triggers to disambiguate.	2 / 3
	Total	8 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: cursor/plugins
Path: teaching/skills/create-learning-path/SKILL.md
Commit: fe77e77

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.