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

2.90x

Quality

88%

Does it follow best practices?

Impact

90%

2.90x

Average score across 3 eval scenarios

Securityby

Medium

Suggest reviewing before use

Quality

Content

77%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 content is highly actionable with strong, validated multi-step workflows, but it is longer than necessary and its progressive-disclosure structure is undermined by referenced files that are not present in the bundle plus bulky reference content inlined in SKILL.md.

Suggestions

Move the 18-palette color catalog and the "visual details options" menu into a separate reference file (e.g. design-reference.md) and link to it from a short "Design Principles" summary to reduce SKILL.md length.

Verify html2pptx.md, ooxml.md, and the ooxml/scripts/unpack.py, validate.py, pack.py files are actually shipped in the bundle, since the workflows mark them MANDATORY reads but they are not present in the visible package.

Trim repeated emphasis scaffolding (multiple "MANDATORY/CRITICAL/NEVER set range limits" markers) into a single note near each workflow to tighten the token budget without losing the instruction.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and avoids explaining concepts Claude already knows, but the 18-palette color catalog (~70 lines), the extended "visual details options" menu, and the fully inlined inventory JSON schema are bulky content that could be tightened or moved to a reference, fitting the mostly-efficient-but-could-be-tighter anchor.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands (markitdown, unpack/validate/pack, thumbnail, rearrange, inventory, replace, soffice, pdftoppm) plus concrete JSON examples that cover the common cases, matching the score-5 anchor.	5 / 5
Workflow Clarity	Three numbered workflows are clearly sequenced with explicit validation checkpoints and feedback loops (validate-after-each-edit then fix; generate thumbnails, inspect, adjust, regenerate), matching the score-5 anchor.	5 / 5
Progressive Disclosure	References to html2pptx.md and ooxml.md are clearly signaled as one-level-deep reads, but those files (and the referenced ooxml/scripts/ unpack/validate/pack scripts) are absent from the visible bundle, and substantial reference-grade content (palette catalog, visual-options menu, inventory schema) is inlined rather than split out, fitting the some-structure-but-could-be-better-organized anchor.	3 / 5
	Total	16 / 20 Passed

Description

100%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.

The description is a strong, near-exemplar match to the rubric's good examples: it states concrete capabilities, gives explicit trigger guidance, and scopes clearly to .pptx work. No meaningful gaps across any dimension.

Dimension	Reasoning	Score
Specificity	"Presentation creation, editing, and analysis" plus the enumerated list (creating, modifying content, layouts, comments, speaker notes) lists multiple specific concrete actions with comprehensive coverage, matching the score-5 anchor.	5 / 5
Completeness	It explicitly answers both what (creation/editing/analysis) and when ("When Claude needs to work with presentations (.pptx files) for: ...") with concrete trigger phrases, which is the score-5 anchor example.	5 / 5
Trigger Term Quality	Natural terms like "presentations", ".pptx files", "comments", and "speaker notes" are covered including the file extension, matching the comprehensive-coverage-with-synonyms anchor.	5 / 5
Distinctiveness Conflict Risk	It targets a clear niche (.pptx presentations) with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	20 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 2 missing	Warning

	Total	14 / 16 Passed

Repository: davepoon/buildwithclaude
Path: plugins/all-skills/skills/pptx/SKILL.md
Commit: a9fa86d

Reviewed: about 18 hours 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.