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

83%

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 course-guide in rohitg00/ai-engineering-from-scratch

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 highly actionable, well-structured router with concrete commands, paths, URLs, and an explicit verification step in its workflow. Its main weakness is redundancy: routing rules for MCP, Agent Skills, and certifications are restated across three or four sections and could be consolidated.

Suggestions

Consolidate the recurring MCP, Agent Skills, and certification routing rules into the Routing table section alone; the How to route steps, answer-shape guidance, and closing command list each restate them, costing roughly 15-20 lines that could be trimmed.

Make the confirmation-failure path explicit in step 2: state that if a shortlisted lesson's `docs/en.md` does not cover the failing concept, it is dropped and the next shortlist entry is checked, turning the implicit check into a closed verification loop.

Consider moving the per-route source-of-truth paths and state-file rules (e.g. `learning-paths/*.json`, `*-LEARNING.md`) into a compact reference table so each route is specified exactly once.

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows and is mostly dense routing specifics, but the same routing rules repeat across sections: MCP routing appears in the Routing table ("route to `learn-mcp`"), How to route ("route directly to `learn-mcp`. Do not place the learner in the generic phase sequence"), the answer shape ("make `learn-mcp` the next skill"), and the closing command list ("Use `learn-mcp` for the focused MCP route"); Agent Skills and certification rules similarly recur. Consolidating these would tighten the body noticeably.

3 / 5

Actionability

Guidance is fully executable for a router skill: a copy-paste raw URL ("https://raw.githubusercontent.com/rohitg00/ai-engineering-from-scratch/main/README.md"), exact source paths ("learning-paths/model-context-protocol.json", "glossary/terms.md"), concrete commands (`learn`, `check-understanding <phase>`, `start-learning`), an exact output link template, the explicit lesson order "22, 24, 25, 26, 27", and a "~12 lines" output constraint. Example asks ("attention", "my agent loops forever", "loss goes to NaN") cover the common input shapes.

5 / 5

Workflow Clarity

A clear four-step sequence (interpret the ask across six enumerated shapes → scan Contents tables → answer in a defined shape → handle no match) with an explicit verification checkpoint ("fetch each shortlisted lesson's `docs/en.md` ... and confirm it actually covers the failing concept before recommending it") and a no-match fallback ("If nothing matches, say so plainly"). What to do when a shortlisted lesson fails confirmation is only implicit, and there is no explicit loop-back, leaving minor validation gaps.

4 / 5

Progressive Disclosure

No bundle files exist, and the body is well organized into clearly headed sections (Host invocation contract, Routing table, How to route) with all referenced paths (README, glossary, learning-paths manifests, per-lesson docs) exactly one level deep and signaled with a consistent local-first/raw-fallback rule. The ~130-line body is slightly over what the simple-skill exception covers, and the routing table could arguably be split out, leaving minor organization gaps.

4 / 5

Total

16

/

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 with an explicit, natural trigger-phrase list and a clear statement of what the skill does. Its main gaps are a thin enumeration of concrete capabilities and mild second-person phrasing ("a bug you are fighting").

DimensionReasoningScore

Specificity

The description names the domain ("Topic router for the AI Engineering from Scratch curriculum") and 1-2 concrete actions ("points at the exact lessons that teach it, plus the right next command"), but does not enumerate a broader set of specific capabilities. The primary voice is third person ("it points at"), though the clause "a bug you are fighting" drifts into second person.

3 / 5

Completeness

It clearly answers both questions: the "what" ("points at the exact lessons that teach it, plus the right next command") and an explicit "when" via a concrete trigger-phrase list introduced by "Trigger phrases:". This matches the anchor for both what and when with concrete trigger phrases.

5 / 5

Trigger Term Quality

It lists eight explicit natural trigger phrases users would actually say: "where do I learn", "which lesson covers", "I'm stuck on", "what should I do next", "teach me MCP", "teach me Agent Skills", "where do I prepare for a Claude certification". Coverage spans topic, struggle, meta, and certification intents with synonym-level variation.

5 / 5

Distinctiveness Conflict Risk

The niche is clear (routing within one specific curriculum, "AI Engineering from Scratch"), minimizing conflict with unrelated skills. However, triggers like "teach me MCP" and "what should I do next" intentionally overlap the sibling skills it routes to (learn-mcp, start-learning), creating minor overlap risk with closely related skills in the same suite.

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

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