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 its scope around PowerPoint presentation tasks, includes explicit trigger conditions, and lists specific capabilities. It matches one of the rubric's 'good overall examples' almost exactly, demonstrating best practices for skill descriptions. The description uses third person voice appropriately and provides enough detail for disambiguation from other document-related skills.
| 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 conflict 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.
This skill excels at actionability and workflow clarity, providing concrete commands, validation steps, and error recovery for all major PPTX operations. However, it is severely bloated with content that either Claude already knows (design principles, color theory, layout concepts) or should be in separate reference files (18 color palettes, extensive visual detail catalogs, JSON schema examples). The skill would benefit greatly from aggressive trimming and splitting reference material into linked files.
Suggestions
Move the 18 color palettes and visual details options (geometric patterns, border treatments, typography treatments, etc.) into a separate design-reference.md file and link to it - this alone would cut ~100 lines
Remove or drastically reduce the 'Design Principles' and 'Color Palette Selection' sections - Claude already understands design principles, color theory, and content-appropriate styling
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 inline
Remove explanatory text like 'A .pptx file is essentially a ZIP archive containing XML files' - Claude already knows this
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~350+ 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 throughout (python scripts with exact arguments, bash commands, JSON schemas with concrete examples). Every workflow step has specific, copy-paste ready commands and the JSON replacement format is thoroughly documented with working examples. | 3 / 3 |
Workflow Clarity | All three major workflows (creating from scratch, editing existing, using templates) 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 the template workflow has inventory verification steps with error recovery guidance. | 3 / 3 |
Progressive Disclosure | The skill does reference external files (html2pptx.md, ooxml.md) for detailed guidance, which is good progressive disclosure. However, the massive inline content for color palettes, visual details options, and formatting patterns should be split into separate reference files. The main SKILL.md tries to be both an overview and a comprehensive reference, resulting in a monolithic document. | 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
7cc63f3
- 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.