CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

learning-path

Run the local Claude Code learning path, record evidence, and schedule evidence-based reviews.

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./examples/skills/learning-path/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

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

The body is a well-structured, highly actionable overview: copy-paste ready commands, an explicit completion gate with enumerated failure conditions, and clean offloading of module data to assets/path.yaml and logic to scripts/progress.py. The only notable weaknesses are a slightly unnecessary "Validation boundary" section and the lack of explicit recovery steps for the error conditions it enumerates.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — a mapping table for tracks, an executable command block, and terse gate/review sections — but the "Validation boundary" section explaining PyYAML imports and the quick_validate.py validator's internals is unnecessary explanation that could be trimmed. This matches "efficient; minor instances of over-explanation" rather than 5, and is well above the verbosity of level 3's padding.

4 / 5

Actionability

The Commands section provides copy-paste ready bash commands covering the common cases (init, status, next, complete with a concrete example evidence note, due), each parameterized with ${CLAUDE_SKILL_DIR} and --root "$PWD". Guidance like running /self-assessment quick and the track-mapping table is equally concrete, fully matching the anchor for executable, copy-paste ready commands covering common cases.

5 / 5

Workflow Clarity

The sequence is clear (diagnostic → map result → choose track → init → completion gate → next → due) with an explicit numbered completion checklist and enumerated error conditions (empty note, unmet prerequisite, unknown module, out-of-track module, corrupt state) that fail closed. It falls short of 5 because feedback loops for error recovery are not spelled out — the skill says state "remains untouched for inspection or recovery" but never instructs what to do when a command errors, such as when init refuses an existing state file.

4 / 5

Progressive Disclosure

The body is a clear overview that appropriately offloads detail: full module definitions, prerequisites, and review intervals live in assets/path.yaml (a real bundled file, linked with an explicit description of its contents), and implementation lives in scripts/progress.py, referenced only through executable commands. References are one level deep and well signaled, matching the top anchor; inline content (track summary table) is rightly kept as overview.

5 / 5

Total

18

/

20

Passed

Description

62%Weight 40%Scale 1-5

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 specific and distinctive, clearly stating what the skill does with three concrete actions and occupying a well-defined niche. Its main weakness is the absence of explicit "when to use" trigger guidance and thin natural-keyword coverage, which limits discoverability when a user asks to learn or practice Claude Code.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to learn Claude Code, follow the learning-path curriculum, or track learning progress with evidence."

Include natural keyword variations users would actually say — "learn Claude Code", "training", "tutorial", "modules", "progress tracking" — to broaden trigger-term coverage.

Optionally mention the track selection (Beginner to Maintainer) to round out capability coverage without adding fluff.

DimensionReasoningScore

Specificity

The description lists several concrete actions in the Claude Code domain — "Run the local Claude Code learning path, record evidence, and schedule evidence-based reviews" — going beyond naming the domain. It falls short of 5 because coverage has minor gaps (e.g., track selection and the spaced-review cadence are core capabilities left unmentioned), and it is not merely 3 since three distinct concrete actions are named rather than 1-2.

4 / 5

Completeness

The "what" is clear (run the learning path, record evidence, schedule evidence-based reviews), but there is no "Use when..." clause or any equivalent explicit trigger guidance, which the judging guidelines cap at 3. It is not level 4 because the "when" is only weakly implied by the topic itself, not stated.

3 / 5

Trigger Term Quality

Some relevant natural keywords are present ("learning path", "evidence", "reviews"), but common variations a user would naturally say — such as "learn Claude Code", "training", "curriculum", "modules", or "progress tracking" — are missing. This matches the anchor for some relevant keywords without common variations or synonyms, and is not level 4 because keyword coverage is thin rather than merely missing a few terms.

3 / 5

Distinctiveness Conflict Risk

"Run the local Claude Code learning path" carves out a clear niche with a distinct trigger phrase ("learning path") that is unlikely to match unrelated skills, and the evidence/review framing further separates it from generic educational or tracking skills. This matches the anchor for a clear niche with distinct triggers and minimal conflict risk.

5 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

FlorianBruniaux/claude-code-ultimate-guide

Path

examples/skills/learning-path/SKILL.md

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.