pptx

Use this skill any time a .pptx or .potx 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 or .potx 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 (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

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

An exceptionally dense, expert-oriented skill that maximizes token value with environment-specific footguns, executable commands, and a validation-driven workflow. The only structural gap is the absence of a separate reference doc for the sizable design-guidance section.

Suggestions

Consider extracting the Design Ideas section (palettes, typography, spacing, avoid-list) into a referenced DESIGN.md so the main body stays a lean overview.

The color-palette table is large static reference data that could live in the bundle as a data file loaded on demand rather than always occupying the body.

Dimension	Reasoning	Score
Conciseness	Lean and expert-oriented throughout — no filler explaining what a PPTX is or how libraries work; nearly every line is a footgun, exact value, or environment-specific constraint Claude would not know ('pptxgenjs mutates option objects in place', 'outEnd corrupts the file'). Long design/palette/typography sections are actionable reference data, not over-explanation.	5 / 5
Actionability	Fully executable guidance: copy-paste bash blocks for unpack/edit/zip/validate, exact script invocations with flags, and concrete API values (color: "FF0000", transparency: 0-100, charSpacing) covering the common creation and editing cases.	5 / 5
Workflow Clarity	Sequenced editing workflow with explicit, emphasized validation checkpoints ('run after <p:sldIdLst> is final', 'After writeFile(), run validate.py') and a mandatory QA section with a render-inspect-fix feedback loop for the destructive repack/delete operations — validation is present, so no cap applies.	5 / 5
Progressive Disclosure	Good single-file structure with a clear scripts table referencing real bundle files (thumbnail.py, add_slide.py, clean.py, office/validate.py, office/soffice.py — all verified present) one level deep and well-signaled; falls short of 5 because the large Design Ideas section is inline with no separate one-level-deep reference document.	4 / 5
	Total	19 / 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, explicit description that comprehensively enumerates concrete capabilities and provides clear, natural trigger guidance with file extensions. Only minor synonym coverage is missing (e.g., 'PowerPoint', 'slideshow').

Suggestions

Add 'PowerPoint' and 'slideshow' as natural trigger synonyms to broaden keyword coverage.

Consider mentioning '.ppt' (legacy format) in the trigger clause for completeness, since the body covers its conversion.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — creating slide decks/pitch decks/presentations, reading/parsing/extracting text, editing/modifying/updating, combining or splitting, working with templates/layouts/notes/comments — giving comprehensive coverage of the .pptx/.potx domain.	5 / 5
Completeness	Explicitly answers both what ('This includes: creating... reading... editing... combining or splitting... working with templates...') and when ('Trigger whenever the user mentions deck, slides, presentation, or references a .pptx/.potx filename') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Covers natural terms ('deck,' 'slides,' 'presentation') plus file extensions (.pptx, .potx) and 'templates', but misses common synonyms like 'PowerPoint' or 'slideshow', leaving a few natural terms out.	4 / 5
Distinctiveness Conflict Risk	Tightly scoped to .pptx/.potx files with distinct, file-extension-based triggers and clear niche; minimal overlap risk with other skills.	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
referenced_paths_exist	Referenced path issues: 9 deeper-than-1-level	Warning

	Total	15 / 16 Passed

Repository: K-Dense-AI/scientific-agent-skills
Path: skills/pptx/SKILL.md
Commit: b2a92ba

Reviewed: 3 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.