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
87
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
85%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 articulates both capabilities and usage triggers. It excels at completeness with an explicit numbered list of when to use it, and maintains good distinctiveness through the .pptx file format specification. The main weakness is missing common user terminology like 'PowerPoint', 'slides', or 'deck' that would improve trigger term coverage.
Suggestions
Add common user terminology like 'PowerPoint', 'slides', 'slideshow', or 'deck' to improve trigger term coverage for natural user queries
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Creating new presentations', 'Modifying or editing content', 'Working with layouts', 'Adding comments or speaker notes'. Uses third person voice appropriately. | 3 / 3 |
Completeness | Clearly answers both what ('Presentation creation, editing, and analysis') and when ('When Claude needs to work with presentations (.pptx files) for:' followed by explicit numbered triggers). The 'When' clause is explicit and comprehensive. | 3 / 3 |
Trigger Term Quality | Includes 'presentations', '.pptx files', 'speaker notes', and 'layouts' which are relevant keywords. However, missing common variations like 'PowerPoint', 'slides', 'slideshow', or 'deck' that users would naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on .pptx presentation files with distinct triggers. Unlikely to conflict with document, spreadsheet, or other file-type skills due to explicit file format mention. | 3 / 3 |
Total | 11 / 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 strong, comprehensive skill with excellent actionability and workflow clarity. The content provides concrete commands, detailed JSON schemas, and clear multi-step processes with validation checkpoints. The main weakness is some verbosity with repeated warnings and explanations that could be condensed without losing clarity.
Suggestions
Consolidate repeated 'NEVER set any range limits' warnings into a single note at the top of the document rather than repeating in each workflow step
Reduce the extensive color palette examples section - consider moving to a separate reference file or condensing to 5-6 representative palettes with a note about creative flexibility
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundant explanations and could be tightened. Repeated 'NEVER set any range limits' warnings and verbose workflow descriptions add unnecessary tokens, though most content is actionable. | 2 / 3 |
Actionability | Excellent actionability with specific executable commands, concrete code examples, JSON schemas, and copy-paste ready bash commands throughout. Every workflow has clear, runnable steps. | 3 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with explicit validation checkpoints (e.g., 'CRITICAL: Validate immediately after each edit'). The template-based workflow has numbered steps with clear dependencies and error recovery guidance. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections for different use cases (reading, creating without template, editing, creating with template). References to detailed files like html2pptx.md and ooxml.md are clearly signaled and one level deep. | 3 / 3 |
Total | 11 / 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 | |
- 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.