tutorial-engineer

Creates step-by-step tutorials and educational content from code. Transforms complex concepts into progressive learning experiences with hands-on examples.

Quality

29%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/tutorial-engineer/SKILL.md

Quality

Content

23%Scale 1-5

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

This skill is severely over-engineered and verbose, reading more like a textbook on instructional design than an actionable skill for Claude. It extensively explains concepts Claude already understands (pedagogical theory, learning styles, cognitive load) while providing almost no concrete, executable examples. The placeholder values throughout tables ('+% vs reading', '- min') suggest the content was templated but never filled in with real data, further reducing its utility.

Suggestions

Reduce content by 70-80%: Remove all pedagogical theory explanations (learning retention, cognitive load, Bloom's taxonomy) and focus on the specific tutorial template, structure, and output format Claude should produce.

Replace placeholder values in all tables with actual numbers or remove the tables entirely — entries like '+% vs reading' and '- min' provide zero actionable information.

Add 1-2 concrete, complete examples of tutorial output (e.g., a short sample tutorial section) so Claude can see exactly what good output looks like rather than reading abstract descriptions.

Move detailed reference content (exercise types, visual aid recommendations, quality checklists) into separate bundle files and reference them from a concise SKILL.md overview.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~300+ lines. Extensively explains pedagogical concepts Claude already knows (what progressive disclosure is, Bloom's taxonomy, learning retention patterns, cognitive load theory). Tables with placeholder values ('+% vs reading', '- min') add bulk without actionable information. Much of this reads like a textbook on instructional design rather than a skill file.	1 / 5
Actionability	Despite its length, the skill provides almost no concrete, executable guidance. There are no actual code examples, no specific commands, and no real tutorial output to copy. The template structure uses placeholder brackets throughout. The tables contain placeholder ranges ('- min', '- min') instead of actual numbers. It describes what a tutorial should contain rather than showing how to create one.	2 / 5
Workflow Clarity	There is a rough 3-step tutorial development process (Learning Objective Definition → Concept Decomposition → Exercise Design) and a template structure, but validation steps are vague ('Test every snippet', 'Test all code examples before including them'). The 'Pre-Publish Audit' checklist provides some verification but lacks concrete validation commands or feedback loops for error recovery.	3 / 5
Progressive Disclosure	The skill references 'resources/implementation-playbook.md' but no bundle files are provided, making this a dead reference. All content is inlined in a single massive file with no meaningful separation. The extensive tables on exercise types, visual aids, tutorial formats, and quality scoring could easily be split into referenced files. The monolithic structure makes navigation difficult.	2 / 5
	Total	8 / 20 Passed

Description

36%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 communicates a general idea of creating educational content from code but lacks concrete actions, explicit trigger guidance, and natural user-facing keywords. It reads more like a tagline than a functional skill description, making it difficult for Claude to reliably select this skill over related ones like code documentation or code explanation skills.

Suggestions

Add an explicit 'Use when...' clause with trigger phrases like 'tutorial', 'walkthrough', 'teach me', 'explain this code step by step', 'create a guide', or 'learning material'.

List specific concrete actions such as 'breaks code into progressive steps, adds inline explanations, generates practice exercises, creates beginner-to-advanced progressions'.

Include distinguishing details that separate this from code documentation or explanation skills, e.g., 'Focuses on structured, multi-step pedagogical content rather than API docs or one-off explanations'.

Dimension	Reasoning	Score
Specificity	Names the domain (tutorials/educational content from code) but the actions are generic — 'creates tutorials' and 'transforms concepts' are high-level without specifying concrete actions like 'generates code snippets', 'adds explanations per step', or 'creates exercises'.	2 / 5
Completeness	Has a vague 'what' (creates tutorials and educational content from code) but completely lacks a 'when' clause. There is no explicit guidance on when Claude should select this skill, which per the rubric caps completeness at 3, and the weak 'what' brings it to 2.	2 / 5
Trigger Term Quality	Includes some relevant keywords like 'tutorials', 'educational content', 'learning experiences', and 'hands-on examples', but misses natural user phrases like 'teach me', 'explain this code', 'walkthrough', 'guide', 'lesson', or 'how-to'.	3 / 5
Distinctiveness Conflict Risk	Somewhat specific to tutorial/educational content creation from code, but could easily overlap with documentation skills, code explanation skills, or general teaching/mentoring skills. The lack of concrete boundaries increases conflict risk.	3 / 5
	Total	10 / 20 Passed

Validation

90%

Warnings & errors only

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

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/tutorial-engineer/SKILL.md
Commit: debb2ec

Reviewed: 11 hours ago

Table of Contents

Discovery Implementation Validation

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.