pptx
Presentation creation, editing, and analysis. When Claude needs to work with presentations (.pptx files) for: (1) Creating new presentations, (2) Modifying or editing content, (3) Working with layouts, (4) Adding comments or speaker notes, or any other presentation tasks
85
81%
Does it follow best practices?
Impact
90%
2.90xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
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 both what the skill does and when it should be used. It lists specific capabilities (creating, editing, layouts, speaker notes) and explicitly defines trigger conditions with the file format (.pptx). The description is well-structured and closely matches the rubric's good examples—in fact, it is one of the provided good examples.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creating presentations, modifying/editing content, working with layouts, adding comments or speaker notes. These are distinct, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (creation, editing, analysis of presentations) and 'when' ('When Claude needs to work with presentations (.pptx files) for...' followed by explicit trigger scenarios). The 'when' clause is explicit and well-structured. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'presentation', '.pptx', 'slides' is implied through 'presentations', 'speaker notes', 'layouts', 'editing'. The file extension .pptx is a good technical trigger. Could be slightly improved by mentioning 'slides' or 'PowerPoint' explicitly, but coverage is good. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to .pptx presentation files with specific triggers. Unlikely to conflict with document, spreadsheet, or other file-type skills due to the explicit file format and presentation-specific terminology. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill excels at actionability and workflow clarity, providing concrete commands, validation steps, and clear sequential processes for all three major workflows. However, it is severely bloated with inline content that should be in separate reference files—particularly the 18 color palettes, extensive design option catalogs, and detailed JSON formatting examples. The skill would benefit greatly from moving reference material to supporting files and keeping the main SKILL.md as a lean overview with pointers.
Suggestions
Move the 18 color palettes and visual details options (geometric patterns, border treatments, typography treatments, etc.) to a separate DESIGN-REFERENCE.md file and reference it from the main skill
Move the detailed JSON schema examples and formatting patterns for the template workflow into a separate TEMPLATE-WORKFLOW-REFERENCE.md, keeping only a brief summary inline
Remove explanatory content Claude already knows, such as 'A .pptx file is essentially a ZIP archive containing XML files' and general design principles like 'Create clear visual hierarchy through size, weight, and color'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~400+ lines. The color palette section alone lists 18 palettes with hex codes, the visual details options section is a massive catalog of design ideas, and the template workflow includes extensive JSON schema examples and formatting patterns that could be in separate reference files. Much of this content (design principles, color theory, layout innovations) is knowledge Claude already possesses. | 1 / 3 |
Actionability | The skill provides fully executable commands (python scripts, bash commands), concrete JSON schemas with examples, specific file paths, and copy-paste ready workflows. Every step includes the actual command to run with proper arguments. | 3 / 3 |
Workflow Clarity | All three major workflows (creating from scratch, editing, creating from template) have clearly numbered sequential steps with explicit validation checkpoints. The editing workflow includes validate-then-fix loops, the creation workflow includes visual validation with thumbnail inspection and re-generation, and the template workflow has inventory verification steps. | 3 / 3 |
Progressive Disclosure | The skill references external files (html2pptx.md, ooxml.md) appropriately for detailed guidance, but the main SKILL.md itself is a monolithic wall of content. The 18 color palettes, extensive visual details options, and detailed JSON schema examples should be in separate reference files rather than inline. The structure exists but content that should be separate is inline. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- davepoon/buildwithclaude
- Commit
c911a92
- 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.