Tutorial Outline Creator - Auto-activating skill for Technical Documentation. Triggers on: tutorial outline creator, tutorial outline creator Part of the Technical Documentation skill category.
36
3%
Does it follow best practices?
Impact
97%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/17-technical-docs/tutorial-outline-creator/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a placeholder that restates the skill name without providing any meaningful detail about capabilities, actions, or usage triggers. It lacks concrete actions, natural trigger terms, and explicit guidance on when Claude should select this skill. It would be nearly indistinguishable from other documentation-related skills in a large skill library.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates structured tutorial outlines with learning objectives, prerequisites, step-by-step sections, and summary checkpoints for technical documentation.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a tutorial outline, structure a how-to guide, plan a walkthrough, or organize instructional content.'
Remove the duplicated trigger term and replace with diverse natural phrases users might say, such as 'tutorial structure', 'how-to outline', 'lesson plan', 'step-by-step guide outline', 'instructional outline'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('Technical Documentation') and a label ('Tutorial Outline Creator') but does not describe any concrete actions. There are no specific capabilities listed such as 'generates structured outlines', 'organizes topics into sections', or 'creates step-by-step tutorial plans'. | 1 / 3 |
Completeness | The description fails to clearly answer 'what does this do' beyond the name itself, and there is no explicit 'when should Claude use it' clause. The 'Triggers on' line merely repeats the skill name rather than providing meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'tutorial outline creator' repeated twice. These are not natural phrases users would say — users are more likely to say 'create a tutorial outline', 'outline for a how-to guide', 'structure a tutorial', etc. There is no coverage of common variations. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'Tutorial Outline Creator' is somewhat specific and narrows the scope to tutorial outlines within technical documentation, which provides some distinctiveness. However, the lack of concrete detail means it could overlap with general documentation or outline-creation skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell with no substantive content. It consists entirely of generic boilerplate that describes what the skill would do without actually providing any instructions, examples, templates, or actionable guidance for creating tutorial outlines. It fails on every dimension of the rubric.
Suggestions
Add a concrete tutorial outline template with specific sections (e.g., Prerequisites, Learning Objectives, Step-by-step sections, Summary) and an example of a completed outline for a sample topic.
Include actionable steps for creating a tutorial outline: e.g., 1. Identify target audience and skill level, 2. Define learning objectives, 3. Break content into logical sections, 4. Add time estimates and prerequisites—with concrete examples for each step.
Provide at least one complete input/output example showing a user request (e.g., 'Create a tutorial outline for building a REST API with Express.js') and the expected structured outline output.
Remove all generic boilerplate text ('This skill provides automated assistance...', 'Provides step-by-step guidance...') and replace with actual domain-specific instructions and constraints for tutorial outline creation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats the trigger phrase 'tutorial outline creator' excessively, and provides zero domain-specific information or instructions. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no code, no commands, no examples of actual tutorial outlines, no templates, no specific steps. Every section is vague and abstract, describing capabilities rather than instructing. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic placeholder text with no references to supporting files, no structured navigation, and no meaningful content organization. There are no bundle files to reference either, but the body itself lacks any useful structure. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
3a2d27d
Table of Contents
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.