presentation-slide-outliner
Presentation Slide Outliner - Auto-activating skill for Visual Content. Triggers on: presentation slide outliner, presentation slide outliner Part of the Visual Content skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill presentation-slide-outliner36
Quality
3%
Does it follow best practices?
Impact
99%
1.08xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/18-visual-content/presentation-slide-outliner/SKILL.mdDiscovery
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 severely underdeveloped, consisting only of the skill name, a duplicated trigger term, and a category label. It provides no information about what actions the skill performs or when it should be selected, making it nearly useless for skill selection among multiple options.
Suggestions
Add specific actions the skill performs, e.g., 'Creates structured outlines for presentations, organizes content into logical slide sequences, generates speaker notes frameworks'
Include a 'Use when...' clause with natural trigger terms like 'Use when the user needs to outline a presentation, structure slide content, plan a slide deck, or organize presentation flow'
Add keyword variations users might naturally say: 'presentation outline', 'slide structure', 'deck planning', 'organize slides', 'presentation framework'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Presentation Slide Outliner') without describing any concrete actions. There are no verbs indicating what the skill actually does - no mention of creating outlines, structuring content, generating slides, etc. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just the skill name repeated twice ('presentation slide outliner, presentation slide outliner'). This provides no natural keyword variations users might say like 'outline slides', 'presentation structure', 'slide deck outline', or 'organize presentation'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Presentation Slide Outliner' is somewhat specific to outlining presentations, the lack of detail means it could overlap with general presentation skills. The category 'Visual Content' is broad and doesn't help distinguish it from other presentation-related 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 essentially a placeholder template with no actual content. It describes what a presentation slide outliner skill might do but provides zero actionable guidance, no examples of slide outline formats, no concrete steps for creating outlines, and no useful information whatsoever. The entire content could be replaced with a single sentence and lose nothing of value.
Suggestions
Add concrete examples of slide outline formats (e.g., hierarchical structure with title, key points, speaker notes)
Provide executable code or templates for generating slide outlines in common formats (Markdown, YAML, or presentation tool syntax)
Include a clear workflow: gather content → structure into sections → create slide hierarchy → validate flow
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with specific, actionable instructions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that waste tokens without adding value. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific steps, no examples of actual slide outlines. The content describes what the skill supposedly does but never instructs how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains no actual steps. There are no processes, sequences, or validation checkpoints. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no structure for discovery. No references to detailed materials, no examples, no linked resources - just empty promises of capabilities. | 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 | |
- 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.