pptx

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

Quality

83%

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

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

A strong, highly actionable body with an excellent QA feedback loop, undermined by broken progressive disclosure: editing.md and pptxgenjs.md are referenced as the authoritative guides but do not exist in the bundle. The "Visual QA" section is also an empty header with no content between it and "Verification Loop."

Suggestions

Add the missing editing.md and pptxgenjs.md to the bundle (or inline their essential content) — both are linked from the Quick Reference table as the primary guides for editing and creating from scratch.

Fill in or remove the empty '### Visual QA' section, which currently has a header with no content before '### Verification Loop'.

Expand the compressed editing workflow ('Unpack → manipulate slides → edit content → clean → pack') into sequenced steps with an explicit validation checkpoint after packing, mirroring the QA verification loop.

Dimension	Reasoning	Score
Conciseness	The body never re-teaches known concepts; the long Design Ideas section is opinionated, specific guidance (palettes, font pairings, size tables) that Claude cannot be assumed to produce on its own. Only minor padding exists, e.g. "Don't create boring slides. Plain bullets on a white background won't impress anyone."	4 / 5
Actionability	Commands are copy-paste ready throughout: `python -m markitdown presentation.pptx`, `python scripts/office/unpack.py presentation.pptx unpacked/`, the placeholder-grep one-liner, `pdftoppm -jpeg -r 150 -f N -l N output.pdf slide-fixed`, and exact dependency installs. Common cases are covered with executable examples.	5 / 5
Workflow Clarity	The QA verification loop is explicit and strong ("Re-verify affected slides — one fix often creates another problem... Do not declare success until you've completed at least one fix-and-verify cycle"). Not a 5: the core editing workflow is compressed arrow notation ("Unpack → manipulate slides → edit content → clean → pack") with no validation checkpoint between packing and QA.	4 / 5
Progressive Disclosure	The Quick Reference table and per-section "Read [editing.md] / [pptxgenjs.md] for full details" links are well-signaled and one level deep — but neither file exists in the bundle (only scripts/ is present). Both primary detail paths are dead ends and the deferred content is absent, so navigation effectively fails. Not a 3: this is not merely imperfect organization, the referenced files are missing entirely.	2 / 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.

An excellent description: comprehensive concrete capabilities, an explicit and well-phrased trigger clause, and a clearly bounded .pptx niche. The only notable gap is the absence of the natural synonym "PowerPoint" among the trigger terms.

Dimension	Reasoning	Score
Specificity	The description enumerates multiple concrete actions — "creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text... editing, modifying, or updating... combining or splitting... working with templates, layouts, speaker notes, or comments" — covering the full create/read/edit/merge/split range with no significant gaps, matching the comprehensive-coverage anchor.	5 / 5
Completeness	Both what ("This includes: creating... editing... combining or splitting...") and when ("Use this skill any time a .pptx file is involved... Trigger whenever the user mentions 'deck,' 'slides,' 'presentation,'...") are explicitly and concretely stated, matching the 5 anchor directly.	5 / 5
Trigger Term Quality	Good natural-term coverage including synonyms ("deck," "slides," "presentation," "pitch decks") and the file extension (.pptx). Not a 5: "PowerPoint" — the single most natural synonym a user would say — is missing.	4 / 5
Distinctiveness Conflict Risk	Scoped tightly to .pptx with niche-specific triggers (deck/slides/presentation); the trigger terms map almost exclusively to presentation work, so conflict risk with other skills is minimal.	5 / 5
	Total	19 / 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
relative_links	Relative link issues: 4 missing	Warning
referenced_paths_exist	Referenced path issues: 3 deeper-than-1-level	Warning

	Total	14 / 16 Passed

Repository: eigent-ai/eigent
Path: resources/example-skills/pptx/SKILL.md
Commit: 3ec6f4c

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.