CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

course-guide

Topic router for the AI Engineering from Scratch curriculum. Give it a topic, a question, or a bug you are fighting, and it points at the exact lessons that teach it, plus the right next command. Trigger phrases: "where do I learn", "which lesson covers", "course guide", "I'm stuck on", "what should I do next", "teach me MCP", "teach me Agent Skills", "where do I prepare for a Claude certification"

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A dense, highly actionable router skill whose body consists almost entirely of non-inferable course-specific routing rules with concrete paths, commands, and link templates. Its one real weakness is redundancy: the six focused routes are each specified two or three times across the routing table, the 'How to route' steps, and the closing command-reference paragraph.

Suggestions

Merge the closing paragraph (lines 130-143) into the routing table: it repeats the learn-mcp, learn-agent-skills, claude-certification, and interview-prep routing rules and state-file assignments almost verbatim, so one authoritative table plus the command list would cut ~15 lines.

State each focused route's rule once — e.g. keep 'Do not place the learner from Lesson 22 to numeric Lesson 23; the manifest order is 22, 24, 25, 26, 27' in either the routing table or step 1 of 'How to route', not both — and cross-reference the other location instead.

Extend the docs/en.md verification checkpoint from struggles to topic asks as well (or state explicitly why title/phase matching is sufficient precision for them), which would also close the workflow_clarity validation gap.

DimensionReasoningScore

Conciseness

Every fact is course-specific and non-obvious (routes, state files, manifest orders), so nothing explains concepts Claude already knows, but each focused route is described three times — routing table ('For MCP clients, servers, JSON-RPC... route to learn-mcp'), again in 'How to route' step 1, and again in the closing paragraph ('Use learn-mcp for the focused MCP route') — and the Agent Skills manifest order (22, 24, 25, 26, 27) appears twice. This fits 'mostly efficient but could be tightened' rather than anchor 2, since the padding is redundancy of genuinely necessary routing rules, not unnecessary explanation.

3 / 5

Actionability

The guidance is fully executable for an instruction-only skill: a copy-paste raw GitHub URL, exact file paths (LEARNING.md, learning-paths/agent-skills.json, docs/en.md), exact commands (learn, check-understanding <phase>, start-learning), a concrete lesson-link template, and a bounded output shape ('keep it under ~12 lines'). Not anchor 4: there are no missing key details — even the failure mode ('Never invent a lesson that does not exist') is specified.

5 / 5

Workflow Clarity

A clear 4-step sequence (interpret ask → scan Contents → answer in shape → handle no-match) with an explicit checkpoint for the riskiest case ('fetch each shortlisted lesson's docs/en.md... and confirm it actually covers the failing concept') and an explicit failure branch ('If nothing matches, say so plainly'). Not anchor 5: verification is conditional (only struggles; plain topic asks rely on title/phase matching with no confirmation step) and there is no post-answer re-check loop, which fits 'clear sequence with most checkpoints present; minor validation gaps'.

4 / 5

Progressive Disclosure

The body is a lean, well-sectioned overview (host invocation contract, routing table, how to route) that appropriately keeps the 542-lesson catalog out of SKILL.md by delegating to the repo README ('Read README.md locally if the repo is cloned; otherwise fetch...') and per-route manifests, with local-first/raw-fallback clearly signaled. Nothing that belongs in a separate file is inlined, and navigation between sections is easy — no bundle files exist to verify, so scoring is on body structure and external reference hygiene.

5 / 5

Total

17

/

20

Passed

Description

86%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 that nails the hard parts: an explicit, natural trigger-phrase list and a crisp dual answer to 'what' and 'when', scoped to a distinct niche. Its only deduction is mechanical — the second sentence's imperative/second-person framing ('Give it a topic... a bug you are fighting') costs a specificity point under the rubric's third-person voice rule — plus slight trigger overlap with the focused sub-skills it routes to.

Suggestions

Rewrite the second sentence in third person to recover the voice penalty, e.g. 'Routes a given topic, question, or bug to the exact lessons that teach it, plus the right next command.'

Consider qualifying the overlapping triggers ('teach me MCP', 'teach me Agent Skills') with the routing context, e.g. 'teach me MCP' (routing to the learn-mcp path), to reduce conflict with the dedicated focused-route skills.

DimensionReasoningScore

Specificity

Concrete actions are named — 'points at the exact lessons that teach it, plus the right next command' with three input shapes (topic, question, bug) — which on content alone fits anchor 4. However, the rubric mandates a 1-point reduction for non-third-person voice, and the sentence 'Give it a topic, a question, or a bug you are fighting' is imperative with an explicit second-person 'you', so the score drops to 3; it is not anchor 2 because the domain and actions are specific, not minimal or generic.

3 / 5

Completeness

It explicitly answers both questions: what ('points at the exact lessons that teach it, plus the right next command') and when ('Trigger phrases: ...' with a concrete list), which is exactly the anchor-5 pattern of a clear capability statement plus explicit trigger phrases. The 'missing Use when clause' cap does not apply because explicit trigger guidance is present.

5 / 5

Trigger Term Quality

Eight natural phrases users would actually say, spanning the main intents: 'where do I learn', 'which lesson covers', 'I'm stuck on', 'what should I do next', 'teach me MCP', 'where do I prepare for a Claude certification' — comprehensive coverage including synonyms across learn/locate/stuck/next-step/teach/prepare shapes (file extensions are not applicable to a curriculum router). Not anchor 4: no significant natural variant of the router's core intents is missing.

5 / 5

Distinctiveness Conflict Risk

'Topic router for the AI Engineering from Scratch curriculum' is a clear niche with distinct triggers, but 'teach me MCP' and 'teach me Agent Skills' would also naturally trigger the dedicated learn-mcp and learn-agent-skills skills this router delegates to (confirmed by the body), creating minor overlap with closely related skills — anchor 4. Not anchor 5 because of that overlap, and not anchor 3 because the curriculum-scoped core is unambiguous.

4 / 5

Total

17

/

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

skills/course-guide/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.