pptx
Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.
83
92%
Does it follow best practices?
Impact
82%
1.54xAverage score across 14 eval scenarios
Passed
No known issues
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, well-crafted skill description that thoroughly covers capabilities, trigger conditions, and edge cases (e.g., extracting content from .pptx for use elsewhere). It uses third person voice appropriately and provides comprehensive natural language triggers. The only minor note is that it uses second person 'Use this skill' framing at the start, but this is directed at Claude as the agent selecting skills, which is acceptable and consistent with the good examples in the rubric.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creating slide decks/pitch decks/presentations, reading/parsing/extracting text, editing/modifying/updating, combining/splitting slide files, working with templates/layouts/speaker notes/comments. | 3 / 3 |
Completeness | Clearly answers both 'what' (creating, reading, parsing, editing, combining presentations) and 'when' with explicit triggers ('Trigger whenever the user mentions deck, slides, presentation, or references a .pptx filename'). The entire description is essentially a detailed 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'deck,' 'slides,' 'presentation,' '.pptx,' 'pitch decks,' 'speaker notes,' 'templates,' and even covers the scenario of referencing a .pptx filename. These are all terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very clearly scoped to .pptx files specifically, with distinct triggers like 'deck,' 'slides,' 'presentation,' and '.pptx.' Unlikely to conflict with other skills since it's anchored to a specific file format and domain. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill that provides clear workflows with strong validation checkpoints, especially in the QA section. The progressive disclosure is effective with a clean routing table and appropriate delegation to sub-guides. The main weakness is the Design Ideas section, which while useful, is lengthy and could benefit from being extracted to a separate reference file to improve token efficiency.
Suggestions
Consider moving the Design Ideas section (color palettes, typography, layout options) to a separate file like `design-guide.md` and referencing it from the main skill, reducing the SKILL.md token footprint significantly.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The quick reference table and reading/editing/creating sections are lean and efficient. However, the Design Ideas section is quite lengthy with extensive color palettes, typography tables, and layout guidance that could be split into a separate reference file. The QA section is thorough but somewhat verbose with explanations Claude could infer. | 2 / 3 |
Actionability | The skill provides fully executable commands (markitdown, thumbnail.py, unpack.py, soffice.py, pdftoppm), concrete grep patterns for placeholder detection, a complete QA subagent prompt template, and specific numeric values for sizing, spacing, and margins. Guidance is copy-paste ready throughout. | 3 / 3 |
Workflow Clarity | The QA verification loop is exemplary with explicit validation checkpoints, feedback loops (fix → re-verify → repeat), and a clear mandate to not declare success prematurely. The editing workflow references a detailed guide while providing a clear high-level sequence. The converting-to-images section includes both full and partial re-render commands. | 3 / 3 |
Progressive Disclosure | The quick reference table immediately routes to the right guide (editing.md, pptxgenjs.md) based on task type. The main SKILL.md serves as an effective overview with well-signaled one-level-deep references. Inline content (design ideas, QA) is appropriately kept in the main file since it applies universally across all PPTX tasks. | 3 / 3 |
Total | 11 / 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
- anthropics/skills
- Commit
f458cee
- 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.