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.
90
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
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, 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
77%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 with excellent workflow clarity, particularly in the QA/verification loop which includes explicit validation steps, feedback loops, and stopping criteria. The main weakness is the lengthy Design Ideas section inlined in the main SKILL.md, which accounts for roughly half the document and would benefit from being extracted into a separate reference file. The skill demonstrates strong practical knowledge with executable commands throughout.
Suggestions
Extract the Design Ideas section (color palettes, typography, spacing, common mistakes) into a separate file like `design-guide.md` and reference it from the main SKILL.md to improve progressive disclosure and conciseness.
Consider moving the full subagent prompt template to a separate file or making it more concise inline, since it adds significant length to the QA section.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The quick reference table and reading/editing/creating sections are lean and efficient. However, the Design Ideas section is very lengthy (~100 lines of color palettes, typography tables, spacing rules, and anti-patterns) that could be split into a separate reference file. The QA section is well-structured but somewhat verbose with the full subagent prompt template inline. | 2 / 3 |
Actionability | The skill provides fully executable bash commands for text extraction, thumbnail generation, unpacking, PDF conversion, and image inspection. The QA section includes a concrete grep command for placeholder detection, a copy-paste-ready subagent prompt, and specific verification steps. Code examples are real and runnable. | 3 / 3 |
Workflow Clarity | The editing workflow references a detailed guide and provides a clear sequence. The QA section has an explicit verification loop with numbered steps, validation checkpoints ('only when valid'), feedback loops (fix → re-verify), and clear stopping criteria ('stop after one fix-and-verify cycle'). The content QA and visual QA are clearly sequenced with specific commands at each step. | 3 / 3 |
Progressive Disclosure | The quick reference table effectively routes to editing.md and pptxgenjs.md for detailed workflows. However, the Design Ideas section (color palettes, typography, spacing, common mistakes) is a large block of inline content that would be better split into a separate reference file. The QA section's subagent prompt template is also lengthy inline content. Without bundle files provided, the referenced editing.md and pptxgenjs.md cannot be verified. | 2 / 3 |
Total | 10 / 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
- douglasvought/wiggle-skills
- Commit
b27906e
- 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.