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

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Quality

Content

70%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill body is highly actionable with three well-sequenced workflows, explicit validation feedback loops, and concrete executable commands throughout. Its main weaknesses are token bloat from inline design-palette content that belongs in a reference file, a missing inline code example for the html2pptx creation step, and references to files (html2pptx.md, ooxml.md, ooxml/scripts/) that are absent from the bundle.

Suggestions

Move the 18 example color palettes and the "Visual Details Options" lists into a design reference file (e.g., references/design.md), keeping a short pointer in SKILL.md to reduce token consumption on every load.

Fix the broken references: html2pptx.md, ooxml.md, and the ooxml/scripts/ directory (unpack.py, validate.py, pack.py) are marked as MANDATORY reads but are not present in the bundle, so both the creation and editing workflows cannot actually be executed as written.

Add a minimal inline html2pptx.js usage snippet (import, html2pptx() call, pptx.writeFile()) to the creation workflow so the most common task has copy-paste-ready guidance without requiring the external reference.

Dimension	Reasoning	Score
Conciseness	Commands and workflows are mostly efficient, but roughly 100 lines of inline content (18 example color palettes and the extensive "Visual Details Options" lists) pad the file, and lines like "A .pptx file is essentially a ZIP archive containing XML files" explain orientation Claude already knows. This is more than the 'minor instances' of level 4 but far from the heavy padding of level 2.	3 / 5
Actionability	Provides fully executable commands (unpack/pack, rearrange.py with concrete index lists, thumbnail.py with all flags) and complete JSON schema examples with error-message samples. Not a 5 because the primary creation workflow's step 3 ("Create and run a JavaScript file using the html2pptx.js library") has no inline code snippet, leaving the most common task without copy-paste-ready guidance.	4 / 5
Workflow Clarity	All three workflows are clearly sequenced with explicit validation checkpoints and feedback loops: the editing workflow mandates "Validate immediately after each edit and fix any validation errors before proceeding", and the creation workflow includes a visual validation loop with a concrete issue checklist (text cutoff, overlap, positioning, contrast) repeated "until all slides are visually correct". This matches the top anchor including error-recovery loops.	5 / 5
Progressive Disclosure	The body correctly delegates detail to separate files with clearly signaled MANDATORY reads, but scored against the actual bundle: the referenced html2pptx.md, ooxml.md, and ooxml/scripts/ (unpack.py, validate.py, pack.py) do not exist in the bundle (only the five scripts/ files are present, all of which are real and referenced). Combined with ~100 lines of palette/design content inlined in SKILL.md, this fits anchor 3; not 4 because broken references and inlined bulk exceed 'minor organization gaps', not 2 because the overall structure and reference signaling are good.	3 / 5
	Total	15 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that explicitly states both capabilities and trigger conditions with concrete, enumerated actions and a specific file extension. The only weakness is missing natural synonyms like "PowerPoint", "slides", or "deck" that users commonly say when requesting presentation work.

Dimension	Reasoning	Score
Specificity	The description enumerates four concrete actions ("Creating new presentations", "Modifying or editing content", "Working with layouts", "Adding comments or speaker notes") plus open-ended coverage, which matches the anchor for multiple specific concrete actions with comprehensive coverage rather than the 'minor gaps' of level 4.	5 / 5
Completeness	Explicitly answers both what ("Presentation creation, editing, and analysis" with enumerated capabilities) and when ("When Claude needs to work with presentations (.pptx files) for: ...") with concrete trigger phrases, matching the top anchor exactly.	5 / 5
Trigger Term Quality	Includes natural terms like "presentations", ".pptx files", "speaker notes", and "layouts", but misses common synonyms users would actually say such as "PowerPoint", "slides", or "deck". Good coverage with a few natural terms missing fits anchor 4; not 5 because synonym coverage is incomplete, not 3 because several relevant natural keywords are present.	4 / 5
Distinctiveness Conflict Risk	The .pptx file extension and presentation-specific terms (speaker notes, layouts) establish a clear niche with distinct triggers and minimal conflict risk with other document skills, matching the top anchor.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: netease-youdao/LobsterAI
Path: SKILLs/pptx/SKILL.md
Commit: 791a352

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.