ppt-creator
Create professional slide decks from topics or documents. Generates structured content with data-driven charts, speaker notes, and complete PPTX files. Applies persuasive storytelling principles (Pyramid Principle, assertion-evidence). Supports multiple formats (Marp, PowerPoint). Use for presentations, pitches, slide decks, or keynotes.
75
67%
Does it follow best practices?
Impact
80%
1.37xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./ppt-creator/SKILL.mdQuality
Discovery
100%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 is a strong skill description that clearly communicates specific capabilities (slide deck creation, chart generation, speaker notes, multiple format support), includes relevant methodologies, and provides explicit trigger terms. It uses proper third-person voice throughout and covers both what the skill does and when to use it. The description is concise yet comprehensive, making it easy for Claude to select appropriately from a large skill set.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creating slide decks from topics/documents, generating structured content with data-driven charts, speaker notes, complete PPTX files, applying storytelling principles (Pyramid Principle, assertion-evidence), and supporting multiple formats (Marp, PowerPoint). | 3 / 3 |
Completeness | Clearly answers both 'what' (create slide decks, generate charts/notes/PPTX, apply storytelling principles) and 'when' with explicit trigger guidance ('Use for presentations, pitches, slide decks, or keynotes'). The 'Use for...' clause serves as an explicit trigger statement. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'slide decks', 'presentations', 'pitches', 'keynotes', 'PowerPoint', 'PPTX', 'speaker notes', 'charts', 'Marp'. These cover common variations of how users refer to presentation tasks. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly occupies a distinct niche around presentation/slide deck creation with specific triggers like 'PPTX', 'Marp', 'slide decks', 'keynotes', 'pitches'. The mention of specific frameworks (Pyramid Principle, assertion-evidence) and formats further distinguishes it from generic document or content creation skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill demonstrates thorough domain knowledge and a well-thought-out presentation creation workflow with good self-evaluation loops. However, it severely undermines its own progressive disclosure strategy by inlining extensive content from reference files, resulting in a bloated main file that duplicates information. The lack of concrete output examples (sample Marp slides, sample assertion headings) reduces actionability despite the detailed procedural descriptions.
Suggestions
Remove the inlined summaries of reference files (INTAKE.md questions, RUBRIC.md scoring items, STYLE-GUIDE.md specs, VIS-GUIDE.md details) from the main skill—keep only 1-line descriptions with links to the reference files.
Consolidate the duplicated workflow: remove either the Quick Start or Workflow Overview section, keeping one authoritative sequence of steps.
Add a concrete example showing actual output: a sample 2-3 slide Marp markdown snippet with assertion-style headings, bullet points, chart placeholders, and speaker notes to make the expected output format unambiguous.
Add explicit validation checkpoints within the workflow (e.g., verify chart PNGs rendered correctly before insertion, verify PPTX opens without errors after export).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~200+ lines. It redundantly describes the workflow twice (Quick Start and Workflow Overview), inlines extensive reference file summaries (INTAKE.md questions, RUBRIC.md scoring criteria, STYLE-GUIDE.md details, VIS-GUIDE.md details) that should remain in those reference files, and explains concepts Claude already understands (what the Pyramid Principle is, what WCAG AA means). Much of this content duplicates what the referenced files contain. | 1 / 3 |
Actionability | The skill provides a concrete chartkit.py CLI example and specifies output file paths, which is good. However, most guidance is procedural description rather than executable code—there are no examples of actual Marp markdown output, no sample slide content, and the 'apply Pyramid Principle' instructions are abstract rather than showing concrete before/after examples of slide content. | 2 / 3 |
Workflow Clarity | The workflow is clearly sequenced across 10 stages with a self-check feedback loop (score < 75 → refine → re-score, max 2 iterations), which is good. However, the workflow is presented twice (Quick Start + Workflow Overview) creating confusion about which to follow, and validation checkpoints within individual stages are implicit rather than explicit (e.g., no validation after chart generation, no check after PPTX export). | 2 / 3 |
Progressive Disclosure | The skill correctly references multiple external files (INTAKE.md, WORKFLOW.md, TEMPLATES.md, VIS-GUIDE.md, etc.) for one-level-deep navigation. However, it then inlines substantial summaries of those same files (all 10 intake questions, all 10 rubric items, detailed style guide specs), defeating the purpose of progressive disclosure and bloating the main file significantly. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- daymade/claude-code-skills
- Commit
6bb8d7f
- 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.