The PPTX skill gives Claude a defined process for any task that touches a PowerPoint file. It covers deck creation and extraction as well as edits, templates, layouts, notes, comments, slide assembly and final validation.
Key takeaways
- Its trigger scope includes both reading and producing PPTX or POTX files.
- Bundled scripts can add slides, clean files, generate thumbnails and validate Office packages.
- The skill is proprietary; its LICENSE.txt contains the complete terms.
What does the PPTX skill do?
The trigger description is intentionally broad: if a presentation file must be opened, created or changed, the skill applies. The folder includes Python helpers for slide insertion, cleanup and thumbnail generation plus shared LibreOffice and XML-schema validation utilities. That combination makes the skill more than a writing prompt; it can direct file operations in the working environment.
How does the workflow work?
- Inspect the source deck, template, layouts and requested audience.
- Plan the slide sequence and visual hierarchy before editing.
- Create or modify slides and preserve notes, comments or template constraints where requested.
- Render thumbnails and validate the finished PPTX package before returning it.
The exact result still depends on the model, the files available in the working environment, and the permissions granted to that environment. This page documents the repository instructions; Anavem did not run an end-to-end benchmark of the skill.
What does a useful first task look like?
Give it an approved six-slide outline, a copy of the company template and a folder of licensed images. Ask for a new deck rather than an overwrite, require speaker notes on two slides and request a contact sheet of rendered slides. The task is bounded enough to compare the result with the outline and template.
How can you verify the result?
- Render every slide and inspect for clipping, missing fonts and off-canvas objects.
- Confirm the requested slide count, order, notes and template layouts.
- Open the PPTX in the recipient’s presentation software before distribution.
A successful run should produce an output you can inspect independently. If the result cannot be checked against a file, rendered artifact, source reference or explicit acceptance criterion, narrow the task before relying on it.
When is it a good fit?
- Building a presentation from a brief or structured source material.
- Updating an existing deck without discarding its template and layout rules.
- Extracting text or assembling slides from multiple PowerPoint files.
Choose it when those tasks match the documented scope. A popular repository is not evidence that a skill is appropriate for confidential or production data.
What should you review before installing it?
- Whether the skill may overwrite the source deck or should write a new copy.
- Which fonts, images and templates are available and licensed for the output.
- Whether LibreOffice rendering matches the recipient’s PowerPoint environment.
Read the current SKILL.md and every bundled script before installation. Pin a reviewed commit when repeatability matters, then test with non-sensitive data and the narrowest available permissions.
When is it not the right choice?
- A static PDF-only deliverable with no PowerPoint file involved.
- Brand-critical decks that cannot receive a final human visual review.
- Presentations containing untrusted macros or embedded objects that have not been inspected.
Why is it included in this research set?
This skill is published in Anthropic’s official Agent Skills repository. GitHub’s repository API reported 179,524 stars and 21,221 forks on 2026-10-03. Those figures apply to the repository as a whole, not to this individual folder.
GitHub stars and short-term growth are discovery signals, not quality scores. They do not prove security, correctness, maintained compatibility, or individual-skill usage.