How to Install and Use the pptx Skill with Claude Code (2026)

Building a slide deck by hand is the kind of work that feels productive and mostly isn't. Dragging text boxes, re-aligning bullets, retyping numbers you already have in a spreadsheet. The pptx skill for Claude Code takes that mechanical layer off your plate: you describe the deck, it builds a real .pptx file you can open and keep editing. Here's how to install it and actually use it, including the part where you check it's safe first.

What the pptx skill is

The pptx skill is one of Anthropic's document skills, alongside the docx and xlsx ones. It generates and edits genuine PowerPoint files (editable slides, text, shapes, layouts), not screenshots or PDFs. It runs locally, builds the file with a Python library under the hood, and hands you back a .pptx you can open in PowerPoint, Keynote, or Google Slides.

The reason to use it over a chatbot that "writes you a deck" is that you get a working file, not a description of one. You own the output and you edit it like any other slide file.

Step 1: Check the source before you install

A skill is code that runs on your machine, so this step isn't optional, even for an official one. The pptx skill lives in Anthropic's public repo at github.com/anthropics/skills, under the document skills folder. Open the SKILL.md there and read what it does. For this skill the answer is reassuring: it runs locally and builds files without sending your content anywhere. Get in the habit of doing this read for every skill, because the next one you install might not be from a source you know.

Step 2: Install the skill

Clone the skills repo and copy the pptx skill into your Claude Code skills directory:

git clone https://github.com/anthropics/skills.git
cp -r skills/document-skills/pptx ~/.claude/skills/pptx

On Windows the destination is the same idea in your user folder: %USERPROFILE%\.claude\skills\pptx.

The skill relies on a Python library (python-pptx) to build files. If it isn't already available, install it:

pip install python-pptx

Restart Claude Code so it picks up the new skill. You can confirm it loaded by asking Claude what skills are available, or just by trying to use it in the next step.

Step 3: Generate your first deck

Open Claude Code in the folder where you want the file to land and describe the deck with real specifics. A vague prompt gives you a vague deck, so give it structure:

> Build a 6-slide pptx pitch deck. Slide 1: title, "Northwind Q2 Review." Slide 2: revenue up 18% to $2.4M. Slide 3: three growth drivers as bullets. Slide 4: one risk, churn ticking to 5%. Slide 5: the ask, $500K to hire four engineers. Slide 6: contact slide.

The skill assembles the .pptx and saves it to your folder. Open it in whatever slide app you use and it's fully editable, because it's a real file, not an export.

Step 4: Edit an existing deck

This is the part people underuse. Most slide work is updating last quarter's deck, not starting blank. Point the skill at a file you already have:

> Open q1-review.pptx, update the revenue figure on slide 2 to $2.4M, and add a slide after it summarizing the three biggest wins.

It modifies the file in place. For recurring reports (a monthly board deck, a weekly status) this turns an hour of manual updating into a one-line request plus a review pass.

Step 5: Fix the parts it gets wrong

Be realistic about what comes out. The skill is excellent at structure and content and merely okay at visual polish. Spacing can be loose, a title might run long, brand colors won't match unless you specify them. That's fine, because you get an editable file. Generate the deck to get 90% of the way there in seconds, then spend five minutes fixing alignment and swapping in your template colors by hand.

If brand consistency matters, pair it with the Brand Guidelines skill so the generated deck starts closer to your house style. For the neighboring document skills, the docx install guide and the xlsx install guide follow the same pattern, and the three together cover most document work.

Troubleshooting the common install errors

Most installs work on the first try, but three snags come up enough to name.

If Claude Code doesn't see the skill after you copy it, the usual cause is the folder path. The skill needs to sit directly in your skills directory as its own folder (~/.claude/skills/pptx/ with the SKILL.md inside it), not nested one level too deep from the copy. Check that the SKILL.md is one folder down, not two.

If generation fails with a Python error, the python-pptx library isn't installed in the environment Claude Code is using. Run the pip install again, and if you use virtual environments, make sure you're installing into the one that's active. On some machines you'll need pip3 instead of pip.

If the skill loads but produces a broken or empty file, your prompt was probably too vague for it to build a valid structure. Go back and give it explicit slide titles and content. The skill needs enough to work with; a one-line request often isn't.

Three prompt patterns that work

The difference between a usable deck and a frustrating one is almost entirely in how you ask. Three patterns get good results.

The slide-by-slide spec, shown above, is the most reliable: number each slide and state its title and key point. You do more work up front and get back a deck that needs almost no restructuring.

The outline-then-build pattern works when you're not sure of the structure yet. Ask the skill to propose a slide outline for your topic first, react to it in plain language, then tell it to build the deck from the agreed outline. This catches structural problems before they're baked into a file.

The update pattern is for recurring decks: point it at last period's file and describe only what changed. This is where the biggest time saving hides, because you're not regenerating, you're editing, and editing an existing structure is where the skill is most accurate.

Combining pptx with your data

The real payoff comes when you stop feeding it numbers by hand. If you already have the figures in a spreadsheet, use the xlsx skill to pull and summarize them, then ask the pptx skill to build the deck from that summary in the same session. The numbers flow from the workbook into the slides without you retyping a single figure, which also kills the transcription errors that creep in when you copy numbers between apps at 5pm. For a monthly report that's built from a standard data file, this pair turns an hour of assembly into a couple of minutes plus a review pass.

How this compares to the alternatives

Plenty of standalone AI deck builders exist, and they have their place. The web tools give you polished templates and a nice editing canvas but keep your deck locked in their platform. The pptx skill trades the pretty canvas for something more useful to a lot of people: a native .pptx file you own, generated inside the same environment where your data and documents already live, with no subscription and no export step. If you value design polish above everything, a dedicated deck tool wins. If you value owning an editable file and chaining it to your real data, the skill wins. Match it to what you actually need out of the deck.

When to use it and when not to

Use the pptx skill when the deck is content-heavy and structure-driven: a review, a report, a data summary, a pitch you'll refine. Skip it when the deck is a design piece where every slide is a custom layout, because there you're better off in the slide app from the start. It's a drafting and updating engine, not a designer. Judged as that, it saves real time on exactly the decks that eat your week.

The bottom line

Install it, read the SKILL.md first, and start with the update pattern on a deck you already rebuild every month. That's the fastest way to feel the value, because it turns a recurring hour of manual retyping into a one-line request. Once you trust it there, use it to draft new content-heavy decks from a clear spec, and keep the final visual polish for your own hands. The skill handles the mechanical 90%; you keep the 10% that makes a deck actually good. That division is the whole reason it's worth installing.

One last practical note: keep your prompts in a text file as you find ones that work. The slide-by-slide spec that produced a clean board deck this month will produce next month's too, with the numbers swapped. Over a few months you build a small library of prompts for the decks you make regularly, and generating them stops feeling like work at all. That habit, more than any single feature, is what turns the pptx skill from a novelty you tried once into a tool you reach for every week.