CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

learn

Interactive lesson tutor for the AI Engineering from Scratch curriculum. Reads LEARNING.md, fetches the next lesson, teaches it section by section in the terminal, quizzes at the end, and records progress. Works cloned or entirely over raw.githubusercontent.com — no setup required. Trigger phrases: "next lesson", "teach me", "continue the course", "let's learn", "resume learning"

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

The canonical home for this skill is learn in rohitg00/ai-engineering-from-scratch

SKILL.md
Quality
Evals
Security

Quality

Content

70%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 delivers an unusually well-sequenced interactive workflow with explicit branching, validation, and feedback loops, and its guidance is consistently concrete. Its weaknesses are repetition and bulk: near-identical handoff sections, overlapping lesson-screen bullets, and route-specific routing detail that belongs in reference files all inflate the always-loaded token cost.

Suggestions

Consolidate the three Focused handoff sections (MCP, Agent Skills, Reverse Engineering) into a single table or one shared pattern plus per-route rows, eliminating the repeated "Do not choose the next numeric Phase 13 lesson / do not copy state into LEARNING.md" boilerplate.

Move the seven-entry resume-routing table and per-route handoff detail into a references/ file (e.g., ROUTING.md) and keep only the dispatch rule and a one-line route list in SKILL.md, since that detail is only needed on resume or handoff invocations.

Tighten the lesson-screen section by merging its overlapping condition bullets, and add a one-line example of a LEARNING.md progress row and a quiz.json question so the tutor does not have to infer those formats.

DimensionReasoningScore

Conciseness

The body is dense instructional prose with no tutorials on concepts Claude already knows, but it could be tightened: the three handoff sections repeat near-identical boilerplate ("Do not choose the next numeric Phase 13 lesson and do not copy X state into LEARNING.md"), the named and unnamed routing rules both repeat "invoke that owner and stop this skill", and the lesson-screen section spans six bullets with overlapping conditions. Mostly efficient but with real consolidation opportunities fits the 3 anchor better than the minor-trimming 4 anchor.

3 / 5

Actionability

Guidance is concrete throughout: the exact fetch URL pattern, exact paths ("phases/<phase-dir>/<lesson-dir>/docs/en.md", "quiz.json"), an exact reply format ("Reply with one letter: <A|B|C|D>."), and explicit thresholds (70% to Review queue, score as N/M). This is mostly executable guidance with minor gaps — no example of a LEARNING.md progress row or quiz.json shape is given, so the tutor must infer those formats — which fits the 4 anchor rather than fully copy-paste-ready 5.

4 / 5

Workflow Clarity

Steps 0-5 are clearly sequenced, each with explicit branches (Found / no eligible lesson / Missing), and validation plus feedback loops are present: the quiz verdict after each answer, the offer to re-do the lesson when both warm-up answers are wrong, the sub-70% Review queue rule, and the screen-failure fallback ("If the server fails, say so in one line and continue"). Clear sequence with explicit validation and error recovery matches the 5 anchor; checkpoint coverage is too complete for 4.

5 / 5

Progressive Disclosure

There is no bundle (no references/, scripts/, or assets/), so everything lives in a single ~220-line SKILL.md. Section headers are clear, but roughly 80 lines of per-route handoff detail (MCP, Agent Skills, Reverse Engineering) and the seven-entry routing table are only needed when a handoff actually occurs and are strong candidates for a reference file inlined in the always-loaded body. Since this is not a sub-50-line simple skill, "content that should be separate is inline" fits the 3 anchor; good sectioning keeps it above 2.

3 / 5

Total

15

/

20

Passed

Description

88%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.

A strong description: concrete end-to-end action list plus an explicit trigger-phrase clause that satisfies both the what and when requirements. The main weaknesses are slightly incomplete synonym coverage in the trigger list and residual overlap risk with the closely related learn-* route skills in the same curriculum family.

Suggestions

Add a few natural trigger variants such as "start learning", "study", or direct topic requests (e.g., "teach me backprop") to broaden keyword coverage.

Disambiguate the resume triggers from sibling route skills, e.g., note that MCP or Agent Skills resume requests route to their own skills so "resume learning" does not fire the wrong tutor.

DimensionReasoningScore

Specificity

"Reads LEARNING.md, fetches the next lesson, teaches it section by section in the terminal, quizzes at the end, and records progress. Works cloned or entirely over raw.githubusercontent.com" lists five-plus concrete actions covering the full operation including both delivery modes, matching the comprehensive-coverage anchor; there are no meaningful gaps that would drop it to 4.

5 / 5

Completeness

The description explicitly answers what ("teaches it section by section in the terminal, quizzes at the end, and records progress") and when via the explicit "Trigger phrases: 'next lesson', 'teach me', 'continue the course', 'let's learn', 'resume learning'" clause, which is equivalent explicit trigger guidance. Both halves are concrete, matching the 5 anchor; the when clause is explicit rather than merely present, so 4 does not fit.

5 / 5

Trigger Term Quality

The listed triggers "next lesson", "teach me", "continue the course", "let's learn", "resume learning" are all phrases a learner would naturally say, but common variations are missing (e.g., "start learning", "study", direct topic requests like "teach me backprop", mentions of the course name). Good coverage with a few natural terms missing fits the 4 anchor rather than comprehensive synonym coverage at 5.

4 / 5

Distinctiveness Conflict Risk

The description is pinned to the "AI Engineering from Scratch curriculum" and "LEARNING.md", making it mostly distinct, but the sibling learn-mcp / learn-agent-skills / learn-reverse-engineering family shares "resume learning"-style resume triggers and "teach me" is broadly generic. Minor overlap risk with closely related skills matches the 4 anchor; it is not 5 given that family overlap, and not 3 since the named curriculum and state file clearly disambiguate.

4 / 5

Total

18

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

rohitg00/ai-engineering-from-scratch

Path

.claude/skills/learn/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.