Presentation Slide Outliner - Auto-activating skill for Visual Content. Triggers on: presentation slide outliner, presentation slide outliner Part of the Visual Content skill category.
36
3%
Does it follow best practices?
Impact
99%
1.08xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/18-visual-content/presentation-slide-outliner/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 repeats the skill name without providing any substantive information about capabilities or usage triggers. It lacks concrete actions, natural trigger terms, and explicit guidance on when Claude should select this skill. The duplicate trigger term suggests auto-generated content with no human refinement.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates structured slide outlines from topics, organizes content into logical slide sequences, creates speaker notes frameworks.'
Add an explicit 'Use when...' clause with natural trigger terms like 'outline a presentation', 'plan slides', 'slide deck structure', 'organize my talk', 'presentation outline', 'PowerPoint outline'.
Differentiate from general presentation skills by clarifying scope, e.g., 'Focuses on planning and structuring presentation content before full slide creation, not on visual design or formatting.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('presentation slide outliner') but does not describe any concrete actions. There are no specific capabilities listed like 'creates outlines', 'organizes slide content', or 'generates slide structures'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and there is no explicit 'when to use' guidance. The 'Triggers on' line is just the skill name repeated, not meaningful trigger conditions. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'presentation slide outliner' repeated twice. Missing natural variations users would say like 'outline slides', 'slide deck outline', 'presentation structure', 'organize slides', 'PowerPoint outline', '.pptx'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'presentation slide outliner' is somewhat specific to a niche task (outlining presentations), but the lack of detail about what distinguishes it from general presentation skills (like full presentation creation or editing) creates potential overlap. | 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 a skill would do without providing any actual instructions, examples, templates, or actionable guidance for creating presentation slide outlines. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable examples showing how to create a slide outline (e.g., a markdown template or structured format for a 10-slide presentation with title, key points, speaker notes).
Define a clear workflow: e.g., 1) Identify audience and goal, 2) Draft outline structure using provided template, 3) Validate slide count and content balance, 4) Output in specified format (Mermaid, markdown, PPTX structure).
Remove all boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') that describe meta-information about the skill rather than teaching how to perform the task.
Include at least one complete input/output example showing a user request and the expected slide outline format.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'presentation slide outliner' excessively, and provides zero substantive information about how to actually outline presentation slides. | 1 / 3 |
Actionability | There is no concrete guidance, no code, no commands, no examples of actual slide outlines, no templates, and no specific instructions. Every section is vague and abstract, describing what the skill supposedly does without showing how. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains zero steps. There is no sequence, no validation, and no process described at all. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of generic placeholder text with no references to external files, no structured navigation, and no meaningful organization of content across sections. | 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 | |
4dee593
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.