CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deep-learning-book

Use when studying or applying Goodfellow, Bengio and Courville's Deep Learning, or asking if its advice still holds. Indexes all 20 chapters with a 2016-to-2026 delta, plans reading paths with reading_path_planner.py and diagnoses training failures with training_diagnostics.py.

Quality

73%

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 ./engineering/deep-learning-book/skills/deep-learning-book/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

52%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 well-organized as a study companion — clear dispatch logic, dense chapter/topic indexes, and tool commands that match the real scripts — but its progressive-disclosure promise is broken: every chapter link and three of the supporting-file links point to nonexistent files, and the existing assets are never referenced. The core-frameworks section also re-explains material Claude already knows, costing conciseness.

Suggestions

Create the chapters/ch01–ch20 files the Chapter Index and the 'load that chapter's file' workflow depend on — or remove those links — since all 20 chapter references currently dead-end at nonexistent files.

Either add the missing glossary.md, patterns.md and cheatsheet.md or drop them from Supporting Files, and reference the existing assets/ files (chapter_worksheet.md, study_log_template.md, example_layer_spec.json) so the bundle's real content is discoverable from SKILL.md.

Replace the hardcoded script path 'engineering/deep-learning-book/skills/deep-learning-book/scripts' with a bundle-relative path (e.g. 'scripts/reading_path_planner.py') so the tool commands run wherever the skill is installed, and trim the Core Frameworks paragraphs that restate standard ML knowledge (KL asymmetry, backprop mechanics) down to the chapter pointers and delta notes.

DimensionReasoningScore

Conciseness

The indexes, dispatch table and tool commands are tight, but several Core Frameworks paragraphs re-explain concepts Claude already knows beyond what the chapter citation needs ('D(p‖q) ≠ D(q‖p). Forward KL is mode-covering... reverse KL is mode-seeking', 'Backprop is the chain rule scheduled well', the ViT-vs-ConvNet data aside), and time-stamped details ('companion compiled 2026-08-25', '2019–2020') sit outside any deprecation/delta framing. Not 4 because the re-explanations are more than minor trimming; not 2 because most of the body earns its place.

3 / 5

Actionability

The tool commands are concrete and match the actual scripts' flags ('--goal', '--background', '--hours-per-week', '--spec-sample'), and the how-to dispatch is specific. But the central instruction — 'that chapter file is read before answering' / 'load that chapter's file' — cannot be executed: all 20 chapter links plus glossary.md, patterns.md and cheatsheet.md point to files that do not exist, and $S hardcodes an install path ('engineering/deep-learning-book/skills/...') that does not match the bundle. Scored 3 rather than 4 because the primary navigation action is broken, not a minor gap; not 2 since the scripts and dispatch guidance are genuinely executable.

3 / 5

Workflow Clarity

'How to Use This Skill' gives an explicit decision dispatch (no argument → core frameworks; a topic → Topic Index → chapter file; chNN → that file; 'is this still true?' → delta layer; 'where do I start?' → planner), and Scope & Limits adds boundary routing ('say the book does not cover it and cite the delta reference'). Read-only study skill, so no validation checkpoints are required. Not 5 because the topic→chapter route dead-ends at the missing chapter files and the diagnostic flows offer no verify step; not 3 because the routing itself is explicit and coherent.

4 / 5

Progressive Disclosure

On paper the structure is excellent — overview, chapter and topic indexes, one-level-deep references — but scored against the actual bundle: 23 of the 27 referenced non-script targets (all 20 chapters/*.md plus glossary.md, patterns.md, cheatsheet.md) do not exist, while the 3 real assets/ files (chapter_worksheet.md, study_log_template.md, example_layer_spec.json) are never referenced and are undiscoverable. The primary disclosure layer is phantom and real bundle content is orphaned. Not 3 because this is worse than 'could be better organized' — following the main links fails outright; not 1 because there is no nesting and the section structure is present.

2 / 5

Total

12

/

20

Passed

Description

83%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: third-person voice, explicit 'Use when' triggers tied to a specific named book, and three concrete capabilities with named scripts. The only weaknesses are minor — it advertises 2 of the 4 tools and the book's title overlaps with the generic field name, creating slight conflict risk with general deep-learning questions.

DimensionReasoningScore

Specificity

Lists several concrete, tool-anchored actions — 'Indexes all 20 chapters with a 2016-to-2026 delta', 'plans reading paths with reading_path_planner.py', 'diagnoses training failures with training_diagnostics.py'. Not 5 because coverage has minor gaps (only 2 of 4 scripts and no hint of the glossary/cheatsheet/navigation use); not 3 because it clearly exceeds 1-2 concrete actions.

4 / 5

Completeness

Explicitly answers 'when' with an 'Use when' clause carrying three concrete trigger scenarios (studying, applying, asking whether its advice still holds), and 'what' with three named capabilities. Matches the 5 anchor structure (what + when with concrete trigger phrases); 4 would require the 'when' to be less explicit than it is.

5 / 5

Trigger Term Quality

Natural user phrasings are present: 'studying or applying Goodfellow, Bengio and Courville's Deep Learning' and 'asking if its advice still holds' — exactly how a reader would phrase the need. Not 5 because common synonyms and variations ('textbook', 'the DL book', chapter-number queries) are missing; not 3 because the most likely trigger phrases (authors, title, still-true) are covered.

4 / 5

Distinctiveness Conflict Risk

Anchoring to a single named book with its authors carves a clear niche with distinct triggers. Not 5 because the bare title 'Deep Learning' is also the generic field name, so broad deep-learning questions carry minor overlap risk; not 3 because the author attribution and 'advice still holds' framing distinguish it from general DL skills.

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

relative_links

Relative link issues: 23 missing

Warning

Total

15

/

16

Passed

Repository

alirezarezvani/claude-skills

Path

engineering/deep-learning-book/skills/deep-learning-book/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.