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

89%

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

78%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 body is highly actionable with copy-paste commands and a strong QA verification loop, and it avoids conceptual padding. Its main weaknesses are in progressive disclosure: the two detailed guides it routes users to (editing.md, pptxgenjs.md) are missing from the bundle and the office scripts path is broken, and the sizable Design Ideas material is inlined rather than split into a reference file.

Suggestions

Add the missing referenced files editing.md and pptxgenjs.md to the bundle (or remove/replace the links), since the Quick Reference table and section pointers currently route users to documents that do not exist.

Fix scripts/office: it is a 20-byte file containing '../../_shared/office' rather than a real directory, so 'python scripts/office/unpack.py …' cannot run — restore the actual office scripts or correct the path.

Move the large Design Ideas content (color palettes, typography pairings, layout/avoid lists) into a separate design.md reference file and link to it from SKILL.md, keeping the main skill as a lean overview that routes to the detailed guides.

Dimension	Reasoning	Score
Conciseness	The body avoids conceptual padding (it never explains what a PPTX is or how libraries work) and is dense with actionable specifics, matching the 'efficient; minor instances that could be trimmed' anchor; it does not reach 5 because the large inlined Design Ideas section (10 color palettes, 8 font pairings, an extended 'Avoid' list) is heavy token load for the main file.	4 / 5
Actionability	Copy-paste-ready, executable commands cover the common cases — 'python -m markitdown presentation.pptx', 'soffice --headless --convert-to pdf output.pptx', 'pdftoppm -jpeg -r 150 output.pdf slide', the placeholder grep, and pip/npm installs — plus concrete hex codes, pt sizes, and a ready subagent QA prompt, matching the anchor-5 example.	5 / 5
Workflow Clarity	The QA section provides an explicit fix-and-verify feedback loop ('Do not declare success until you've completed at least one fix-and-verify cycle') and a content-QA grep checkpoint, but the core Editing Workflow ('Unpack → manipulate slides → edit content → clean → pack') is terse and defers detail to editing.md, leaving minor validation gaps that fit anchor 4 rather than 5.	4 / 5
Progressive Disclosure	Structure is well-formed — a one-level-deep Quick Reference table with clearly signaled links to editing.md and pptxgenjs.md — but scored against the actual bundle, those referenced files do not exist and scripts/office is a 20-byte broken path file rather than a directory, so the promised navigation is not delivered; this fits the 'some structure… references present but not delivered / content that should be separate is inline' band rather than the 4–5 anchors.	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.

An exemplary description: it enumerates comprehensive concrete capabilities, supplies natural trigger terms with synonyms and the file extension, and explicitly covers both what the skill does and when to invoke it. Conflict risk is low because every trigger is tied to the .pptx niche.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text…; editing, modifying, or updating…; combining or splitting slide files; working with templates, layouts, speaker notes, or comments' — giving comprehensive coverage that matches the anchor-5 example.	5 / 5
Completeness	Explicitly answers both 'what' (the enumerated action list) and 'when' ('Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx filename'; 'If a .pptx file needs to be opened, created, or touched, use this skill'), satisfying the anchor-5 bar of concrete trigger phrases for both.	5 / 5
Trigger Term Quality	Comprehensive natural-term coverage including synonyms ('deck,' 'slides,' 'presentation,' 'pitch decks') and the file extension ('.pptx filename,' '.pptx file'), matching the anchor-5 example that asks for synonyms plus extensions.	5 / 5
Distinctiveness Conflict Risk	The skill is anchored to a clear niche — .pptx files — with extension-based triggering and repeated .pptx scoping, giving minimal conflict risk as in the anchor-5 example; the generic words 'deck/slides/presentation' are explicitly bound to the .pptx context rather than left open.	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
relative_links	Relative link issues: 4 missing	Warning
referenced_paths_exist	Referenced path issues: 1 missing, 1 deeper-than-1-level	Warning

	Total	14 / 16 Passed

Repository: nextlevelbuilder/goclaw
Path: skills/pptx/SKILL.md
Commit: 169e0ba

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.