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
80
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/skillEvaluation — 80%
↑ 1.48xAgent success when using this skill
Validation 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 with explicit numbered scenarios. The main weakness is incomplete trigger term coverage, missing common user terms like 'PowerPoint', 'slides', or 'deck' that would improve skill selection accuracy.
Suggestions
Add common trigger term variations like 'PowerPoint', 'slides', 'slideshow', 'deck', or 'PPT' to improve matching when users use these natural terms
| 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...') with explicit numbered trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes 'presentations', '.pptx files', 'speaker notes', and 'layouts' as natural terms, but 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 like 'layouts', 'speaker notes', and 'slides' that wouldn't conflict with document or spreadsheet skills. | 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, validation steps, and detailed examples for all PPTX operations. Minor verbosity in repeated warnings and some explanatory sections could be trimmed to improve token efficiency.
Suggestions
Consolidate repeated 'NEVER set any range limits' warnings into a single note at the top of the document
Trim the extensive color palette examples section - consider moving to a separate reference file since Claude can generate appropriate palettes contextually
| 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 scripts. Every workflow has clear commands and expected outputs. | 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, editing). References to detailed files like html2pptx.md and ooxml.md are clearly signaled and one level deep. Content is appropriately split by task type. | 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.
- 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.