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 defines the scope (presentation/.pptx files), lists specific capabilities (creating, editing, layouts, speaker notes), and provides explicit trigger conditions. It matches one of the rubric's own 'good overall examples' almost exactly, demonstrating best practices for skill descriptions.
| 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' (presentation creation, editing, analysis) and 'when' ('When Claude needs to work with presentations (.pptx files) for:' followed by explicit trigger scenarios). The 'when' clause is explicit and detailed. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'presentations', '.pptx files', 'creating new presentations', 'editing content', 'layouts', 'comments', 'speaker notes'. These cover common user language well. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to .pptx presentation files with specific triggers like 'presentations', 'speaker notes', and 'layouts' that are unlikely to overlap with other document-handling skills like PDF or spreadsheet tools. | 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.
The skill excels at actionability and workflow clarity with concrete commands, validation steps, and clear sequential processes for all three major workflows. However, it is severely bloated with content Claude already knows (design principles, color theory, 18 color palettes, extensive visual detail catalogs) and inline reference material (JSON schemas, formatting patterns) that should be in separate files. The token cost is very high relative to the unique, actionable information provided.
Suggestions
Move the 18 color palettes and visual details options (geometric patterns, border treatments, typography treatments, etc.) to a separate reference file like `design-reference.md` and link to it — Claude already understands design principles and can generate palettes contextually.
Move the detailed JSON schema examples and formatting patterns for the template workflow into a separate `template-workflow-reference.md` file, keeping only a brief summary and link in the main SKILL.md.
Remove explanatory text that Claude already knows, such as 'A .pptx file is essentially a ZIP archive containing XML files' and the extensive design principle explanations — replace with terse directives only.
| 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. Much of this (design principles, color theory, layout innovations) is knowledge Claude already possesses. The content could be cut by 50%+ without losing actionable value. | 1 / 3 |
Actionability | The skill provides concrete, executable commands throughout (python scripts with exact arguments, bash commands, JSON schemas with complete examples). Every workflow has specific copy-paste-ready commands and the replacement JSON format is thoroughly documented with working examples. | 3 / 3 |
Workflow Clarity | All three major workflows (creating from scratch, editing existing, creating from template) have clearly numbered sequential steps with explicit validation checkpoints. The editing workflow includes mandatory validation after each edit, the creation workflow includes visual validation with thumbnail inspection and a fix-and-retry loop, and the template workflow has inventory validation before replacement. | 3 / 3 |
Progressive Disclosure | The skill references external files (html2pptx.md, ooxml.md, scripts/) appropriately and uses one-level-deep references. However, the massive inline content (color palettes, visual details options, JSON schemas, formatting patterns) should be split into separate reference files rather than bloating the main SKILL.md. The body itself is a near-monolithic wall of text that would benefit from better content splitting. | 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
d065ead
- 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.