tutorial-outline-creator
Tutorial Outline Creator - Auto-activating skill for Technical Documentation. Triggers on: tutorial outline creator, tutorial outline creator Part of the Technical Documentation skill category.
33
0%
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
0%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 title and category label with no substantive content. It lacks concrete actions, meaningful trigger terms, explicit usage guidance, and any distinguishing details that would help Claude select it appropriately from a pool of skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates structured tutorial outlines with learning objectives, prerequisites, step-by-step sections, and code examples 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 technical walkthrough, or organize documentation into a step-by-step format.'
Include distinct keywords and file/format references to reduce conflict risk, e.g., mentioning 'tutorial structure', 'lesson outline', 'how-to guide skeleton', 'documentation planning'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('Technical Documentation') and a vague action ('Tutorial Outline Creator') but does not describe any concrete actions like 'generates structured outlines', 'organizes topics into sections', or 'creates step-by-step tutorial plans'. It is essentially just a title repeated. | 1 / 3 |
Completeness | The description barely answers 'what does this do' beyond restating the skill name, and there is no explicit 'when should Claude use it' clause. The 'Triggers on' line is just the skill name repeated, not meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'tutorial outline creator' repeated twice. There are no natural keyword variations a user might say, such as 'create a tutorial', 'outline for a guide', 'how-to structure', 'lesson plan', 'documentation outline', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so generic ('Technical Documentation' category with no specific actions or file types) that it could easily conflict with any other documentation, writing, or outlining skill. Nothing distinguishes it clearly. | 1 / 3 |
Total | 4 / 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 essentially a placeholder with no substantive content. It repeatedly restates that it helps with 'tutorial outline creator' without ever providing any actual guidance, templates, examples, or actionable instructions for creating tutorial outlines. It fails on every dimension of the rubric.
Suggestions
Add a concrete tutorial outline template or example (e.g., a markdown outline for a specific tutorial topic) that Claude can use as a starting point.
Provide a clear step-by-step workflow for creating a tutorial outline: identify audience, define learning objectives, structure sections, add code examples, validate completeness.
Include at least one fully worked example showing input (topic/requirements) and output (complete tutorial outline) so the skill is actionable.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill abstractly and replace them with actual instructional content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual instructions, techniques, or content that Claude doesn't already know. Every section restates the same vague information. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no examples of tutorial outlines, no templates, no specific steps for creating a tutorial outline. The content only describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The 'Capabilities' section vaguely mentions 'step-by-step guidance' but provides none. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive document with no meaningful structure. There are no references to detailed materials, no examples, and no navigation to supplementary content. The sections are superficial headers over vacuous content. | 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 | |
- Commit
c8a915c
- 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.