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.

1.54x

Quality

96%

Does it follow best practices?

Impact

82%

1.54x

Average score across 14 eval scenarios

Securityby

Low

Low-risk findings worth noting

The canonical home for this skill is gyan/pptx

Quality

Content

92%

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

The body is highly actionable with concrete commands, specific design reference data, and a strong QA fix-and-reverify loop. Its main weakness is progressive disclosure: the referenced editing.md and pptxgenjs.md files are missing from the bundle, and a sizable design section is inlined rather than split into a referenced file.

Suggestions

Add the missing referenced files editing.md and pptxgenjs.md to the bundle (or remove the links) — the Quick Reference and Editing/Creating sections point to them but they do not exist, so navigation breaks when Claude tries to load them.

Move the large inline Design Ideas block (color palettes, typography, spacing, avoid-list) into a separate reference such as design.md and link to it from a brief overview, keeping SKILL.md a lean index.

Reconcile all referenced paths against the bundle: thumbnail.py, office/unpack.py, and office/soffice.py exist, but editing.md and pptxgenjs.md do not, so either ship them or switch those pointers to inline guidance.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, providing concrete reference data (hex palettes, "36-44pt bold", "0.5\" minimum margins") and copy-paste commands rather than explaining concepts Claude already knows; it does not pad with generic background, so it sits at the top anchor despite its length.	3 / 3
Actionability	Fully executable, copy-paste-ready guidance throughout — "python -m markitdown presentation.pptx", "python scripts/office/unpack.py presentation.pptx unpacked/", "pdftoppm -jpeg -r 150 output.pdf slide" — with specific examples and concrete values, matching the top anchor.	3 / 3
Workflow Clarity	The QA section gives a clear sequenced loop with explicit validation checkpoints — "1. Generate slides → Convert to images → Inspect ... 5. Repeat until a full pass reveals no new issues" and "Do not declare success until you've completed at least one fix-and-verify cycle" — providing the feedback loop the rubric requires for document manipulation.	3 / 3
Progressive Disclosure	References are well-signaled and one level deep ("Read [editing.md](editing.md) for full details", "Read [pptxgenjs.md](pptxgenjs.md)"), but those two referenced files are absent from the bundle and a large inline Design Ideas section (palettes, typography, spacing, avoid-list) that could be split out keeps it below the top anchor.	2 / 3
	Total	11 / 12 Passed

Description

100%

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 comprehensive and trigger-rich, enumerating concrete actions and explicit natural-language triggers within a clearly bounded .pptx niche. It answers both 'what' and 'when' unambiguously, with the only minor gap being the absent common term "PowerPoint."

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — "creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file; editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments" — matching the anchor for comprehensive concrete actions, not the partial level below.	3 / 3
Completeness	Explicitly answers both what (create/read/edit/combine/split pptx) and when ("Use this skill any time a .pptx file is involved" plus "Trigger whenever the user mentions...") with explicit trigger guidance, satisfying the top anchor.	3 / 3
Trigger Term Quality	Covers natural terms users say — "Trigger whenever the user mentions \"deck,\" \"slides,\" \"presentation,\" or references a .pptx filename" — giving good coverage of natural keywords, though it omits the common variation "PowerPoint."	3 / 3
Distinctiveness Conflict Risk	Scoped to a clear .pptx niche ("any time a .pptx file is involved in any way") with distinct, file-type-specific triggers, making it unlikely to fire for the wrong skill.	3 / 3
	Total	12 / 12 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: tsinghua-fib-lab/AgentSociety
Path: extension/skills/pptx/SKILL.md
Commit: 1832bcb

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