Create, edit, read, and design PowerPoint presentations (.pptx).
SkillScore91Maintained
Automatic
◆Doc Ops pack
Last verified 8/4/2026
What it changes
Passed 20 of 22 test cases with the skill, and 16 of 22 without it.
Without skill73%
With skill91%
Checks it passed that the model alone missed
Specifies 14-16pt for body text
Uses markitdown to extract slide text content from product_launch.pptx
Uses markitdown combined with grep to search for template placeholders
and 2 more in the full report
4 fixed16 passed either way2 still failing0 broke
Pass-rate lift
+18 pp
Tokens
+125%
Agent turns
0%
Response time
-22%
Model gemini-3.6-flashMeasured 8/4/2026v120 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 4
Prompt
What CLI command combination can scan an exported presentation file `final_deck.pptx` for forgotten template placeholders like `TODO`, `lorem`, `ipsum`, or `xxx`?
What was checked, without and with the skill
Checked
Without skill
With skill
Combines markitdown output with grep regex matching to scan for placeholder strings
Missed
Passed
case-13 · gemini-3.6-flash · 8/4/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md314 linessingle file
PowerPoint Presentation (.pptx)
A .pptx file is a ZIP archive of XML files. You can create, edit, and read them programmatically. Choose the right approach for the task:
Task
Approach
Create a new deck
pptxgenjs (Node) or python-pptx (Python)
Edit an existing deck
Unzip → edit slide XML → rezip
Read content from a deck
markitdown deck.pptx or unzip and parse XML
Convert to PDF
LibreOffice headless
Presentation Principles
Every slide has one job. A slide that makes three points makes zero. Split ruthlessly.
Text-only slides are forgettable. Every slide needs at least one visual element — chart, image, icon, data callout, or diagram.
The deck must work without the speaker. Async decks (sent via email, read without a presenter) need more text and context than live-presentation decks.
Visual hierarchy over bullet points. A large number + small label communicates faster than a sentence. A 2x2 grid communicates relationships better than a list.
Commit to a visual direction and hold it. One font pair. One color palette. One layout style. Inconsistency signals lack of polish.
AI slop is obvious. Cream backgrounds, accent stripes along card edges, Inter/Roboto with no rationale, blue CTA buttons, centered body text — these are trust killers. Avoid all of them.
Step 0: Before Creating
Ask the user:
What is the deck for? (investor pitch, all-hands, client presentation, technical review, sales demo)
Who is the audience? (technical, executive, external client, general team)
How many slides? Or: what content needs to be covered?
Brand constraints? (specific colors, fonts, logo to include)
Output format? (.pptx to edit further, or PDF to send)
Presenting live or sending async? (changes text density and speaker notes needs)