HavenSkills
PowerPoint Skills

PPTX Skill for Claude

The pptx skill is an official Anthropic skill for slide decks: building a new one with pptxgenjs, editing an existing deck or template by unpacking and rewriting its slide XML, and reading a deck's text and layout back out through its own scripts. It installs with one command.

By Anthropic

A .pptx is also a ZIP archive of XML, and the pptx skill splits the work the same way as the Word skill: building a new deck is a library job, touching an existing one is a file-surgery job. Getting those two mixed up is the most common way a deck task goes wrong.

What it actually finishes

  • Build a new deck — a pptxgenjs script that writes slides, layouts, speaker notes and charts, built as a structured deck by default.
  • Build from a template — unpack the .pptx/.potx, edit the slide XML in place, and zip it back, so the company's own layouts survive.
  • Edit an existing deck — the same unpack → edit ppt/slides/slideN.xml → zip route, one file per slide.
  • Read a deck's text — python scripts/slide_text.py deck.pptx prints one block per slide, each under a <!-- Slide number: N --> marker, which is how you find the slide you need to change.
  • See the deck as a human would — python scripts/thumbnail.py deck.pptx renders a visual grid of the slides, which is the only way text extraction can tell you the layout is broken.
  • Combine or split slide files, and work with speaker notes and comments.

When it fires, and when to skip it

It fires whenever a .pptx or .potx file is involved in any way — as input, output or both — and whenever someone says "deck", "slides" or "presentation" and means a file, not a talk. Reading and extracting text counts too: pulling the words out of a deck and pasting them into an email is still this skill.

What it does not do is decide your design. A structured deck is the default route — theme, layouts, consistent type — and a quick throwaway is the exception you ask for, not the default you get.

How to check it worked

  1. Run slide_text.py on the output. One block per slide, in order, is the signature of a deck that wrote all its slides rather than only the first few.
  2. Run thumbnail.py and look at the grid. Overlapping text, text running off the edge of a slide, and a title sitting on top of body copy are all invisible to text extraction and obvious in a thumbnail.
  3. Open the file in a real presenter once. Speaker notes and layout placeholders only show up there.

The thumbnail pass is the one people skip, and it is the one that catches a deck that is technically complete and unusable.

What goes wrong

A generation script cannot edit an existing deck. The route table in the skill is explicit about this: existing files and templates go through unpack → edit ppt/slides/slideN.xml → zip. If you write a script against a deck you were handed, you get a new deck that has none of the original layouts, and the change you wanted to make is gone.

Text extraction says nothing about layout. slide_text.py gives you the words, not the position, size or overlap. A deck can extract perfectly and look broken. Judging layout without thumbnail.py is guessing.

Script paths are relative to the skill's own directory. Copy a script into another working folder and it stops finding what it needs.

One XML file per slide. The slides are ppt/slides/slideN.xml, not a single document — which is why editing a deck is a per-slide job and why a change to one slide cannot take the rest of the deck down with it.

Structured versus throwaway is a decision, not a default. The skill builds a structured deck unless a quick throwaway is what was asked for. Reaching for the fast route on a deck that will be presented is how you arrive at slides with inconsistent layouts.

How it compares

  • pptx — the argument in front of a room: layouts, speaker notes, charts on slides.
  • docx — the same argument as a document, with tracked changes when someone reviews it.
  • xlsx — the numbers as a model rather than a picture of a number.
  • pdf — the exported, fixed-layout version you send when the deck is final.

A deck built from an outline is the classic case where all four show up in one afternoon: outline in docx, figures in xlsx, slides in pptx, exported to pdf.

Try a sample task

This walkthrough gives you a prompt and an acceptance check to run in your own client.

Build a three-slide PowerPoint deck

Provide a short project brief, one data series and the intended audience.

Use the PPTX skill to build a three-slide update with a title slide, an editable chart and one next-steps slide. Render each slide and fix overlap.

What to verify A .pptx with three slides, an editable chart, and readable text without overlaps at the final slide size.

Best for Presentation drafts, existing decks, editable charts and visual slide review.

How to use pptx

Supply the audience, presentation length and any template to preserve. Ask for one main takeaway per slide.

Acceptance check Render the slides and check the slide order, text fit, alignment and notes before sharing the PPTX.

Install for your agent

Run the command from your project directory. After installation, reload the client if it has already started. Tool access and execution features depend on the client.

Claude Code

npx skills add anthropics/skills --skill pptx -a claude-code

Codex

npx skills add anthropics/skills --skill pptx -a codex

Cursor

npx skills add anthropics/skills --skill pptx -a cursor

GitHub Copilot

npx skills add anthropics/skills --skill pptx -a github-copilot
Ask your agent to install the skill
Install pptx from anthropics/skills in this project. Show me the destination folder and report any dependencies the source lists.

For manual installation, copy the entire skill folder, including references and scripts, into a skill directory supported by your client. See the installation guide.

What the upstream guide covers

The PowerPoint guide separates reading and analysis, editing an existing presentation, and building a new deck. It links to workflow-specific instructions for editing and slide generation. Open the guide before choosing a route, then render the output and inspect each slide.

HavenSkills workflow check

No workflow check recorded yet. Use the sample task above to make your own check in your client.

Review methodology and recorded checks

Requirements, permissions and limits

Runtime
PptxGenJS for creation; Python and LibreOffice for selected editing and rendering
File and tool access
Creating and editing decks can require Node.js, Python helpers and rendering software. Review asset access if the brief includes internal slides or images.
Limits to check
Missing fonts or a different rendering engine can change spacing. Open the final deck in the intended PowerPoint environment.

Frequently asked questions

Can it edit a deck someone sent me?

Yes — by unpacking it, editing the slide XML, and zipping it back. The generation library is for new decks only.

Can it read a deck without opening PowerPoint?

Yes. slide_text.py extracts the text per slide, which is enough for summarising or moving content elsewhere.

How do I check the slides actually look right?

Render thumbnails with thumbnail.py and look at the grid. Text extraction cannot see overlap or overflow.

Does it keep speaker notes?

Notes are part of the package, so they survive an unpack-and-rezip edit. A deck regenerated from extracted text would not.

Is it safe for a deck that matters?

The repository describes these skills as demonstration and teaching material and asks you to test them thoroughly before critical use.