pptx

Overview of pptx skill

What the pptx skill is for

The pptx skill helps Claude create, edit, inspect, and repair PowerPoint .pptx presentations. It is built around the reality that a PowerPoint file is a ZIP package of Office Open XML files, so it supports both higher-level presentation workflows and low-level XML inspection when ordinary text extraction is not enough.

Best-fit users and PowerPoint jobs

This skill is a strong fit if you need Claude to work with slide decks rather than just write slide copy. Typical jobs include extracting structured slide content, editing existing decks, rearranging slides, replacing text while preserving formatting, adding speaker notes or comments, and generating new decks from HTML-like slide layouts. It is especially useful for teams that maintain templates, sales decks, training decks, or recurring reports.

What makes this pptx skill different

Unlike a generic prompt for PowerPoint, the repository includes practical helper scripts and technical references: scripts/inventory.py for structured extraction, scripts/replace.py for text replacement, scripts/rearrange.py for slide ordering, scripts/thumbnail.py for previews, scripts/html2pptx.js for HTML-to-PowerPoint generation, and ooxml.md for raw XML rules. That gives an agent a more reliable path from “edit this deck” to actual file-level changes.

Important adoption considerations

The pptx skill is more technical than a simple writing assistant. Some workflows depend on Python packages such as python-pptx and Pillow; HTML conversion uses Node.js libraries such as pptxgenjs, playwright, and sharp. Low-level edits require care because invalid XML relationships, element ordering, or image references can make a .pptx fail to open.

How to Use pptx skill

pptx install and repository files to read first

Install the skill from the skill directory context with:

npx skills add ComposioHQ/awesome-claude-skills --skill pptx

After install, start with SKILL.md for the main workflow, then read html2pptx.md if you plan to generate decks from HTML, and ooxml.md if you need comments, speaker notes, layouts, images, or other features that require raw XML access. For scripts, inspect scripts/inventory.py, scripts/replace.py, scripts/rearrange.py, scripts/html2pptx.js, and ooxml/scripts/unpack.py.

Inputs the pptx skill needs

For analysis, provide the .pptx file and specify whether you want plain text, structured JSON, visual slide order, notes, comments, or layout details. For editing, provide the source deck, the desired output deck name, replacement rules, slide order, brand constraints, and any text that must not change. For new decks, provide slide dimensions, audience, tone, slide-by-slide content, image assets, and whether you want editable PowerPoint objects or screenshot-like fidelity.

Strong prompt patterns for pptx usage

A weak prompt is: “Update this PowerPoint.” A stronger prompt is:

“Use the pptx skill to inspect Q3-review.pptx, extract a slide inventory, then replace only customer names and revenue figures using replacements.json. Preserve existing fonts, bullets, alignment, and slide order. Save as Q3-review-redacted.pptx and report any shapes that could not be edited safely.”

For generation:

“Create a 16:9 PowerPoint from HTML slides. Use 720pt x 405pt body dimensions, put all text inside <p>, heading, <ul>, or <ol> tags, avoid manual bullet symbols, and reserve chart areas with class="placeholder" so charts can be added later.”

Practical workflow for reliable outputs

For simple reading, convert or extract text first before attempting XML edits. For deck-wide text changes, run an inventory, review the JSON, then apply replacements rather than asking for blind edits. For slide rearrangement, use 0-based slide indices and confirm repeated slides intentionally. For complex formatting, unpack the .pptx, inspect ppt/presentation.xml, ppt/slides/slideN.xml, slide relationships, notes, and layouts before writing changes back.

pptx skill FAQ

Is pptx for PowerPoint creation or editing?

Both. The pptx skill can support new deck creation, existing deck edits, slide analysis, text extraction, slide rearrangement, and lower-level PowerPoint XML work. Its best value appears when the task involves real .pptx files, not just drafting slide titles and bullet points.

When should I use raw XML instead of normal extraction?

Use raw XML when you need speaker notes, comments, slide layouts, relationships, animations, images, detailed formatting, or anything not visible through basic text extraction. Plain text extraction is faster for summarization, but it misses many structures that matter in production decks.

Is this pptx guide beginner-friendly?

It is usable by beginners if the task is limited to extraction, replacement, or slide ordering. Advanced workflows require comfort with command-line tools, JSON, Python scripts, Node.js packages, and Office Open XML. If you only need slide copy, a normal writing prompt may be simpler.

When should I not use this skill?

Do not use it when you need guaranteed pixel-perfect design without reviewing the generated deck, when you cannot install required dependencies, or when the presentation contains highly complex proprietary layouts that must not be altered. Also review LICENSE.txt before reusing materials outside the intended Anthropic services context.

How to Improve pptx skill

Improve pptx results with better source context

Give the skill concrete files and constraints: the source .pptx, target output name, slide numbers, replacement data, brand rules, required fonts, aspect ratio, image paths, and whether formatting should be preserved or redesigned. The more explicitly you separate “content may change” from “layout must remain fixed,” the safer the output.

Avoid common PowerPoint failure modes

Most failures come from ambiguous editing instructions, unsupported HTML structure, bad slide dimensions, broken relationships, or invalid XML ordering. For HTML-to-PowerPoint work, keep text inside supported text tags, use real lists instead of manual bullets, match body dimensions to the PowerPoint layout, and check for overflow before export.

Iterate after the first output

Ask for an inventory or thumbnail pass before final edits when accuracy matters. After generating or modifying a deck, open the file in PowerPoint or LibreOffice, check slide count, missing images, bullet formatting, speaker notes, and chart placeholders, then ask the agent to fix specific slide numbers rather than regenerating everything.

Extend the pptx skill for team workflows

For recurring use, add template-specific notes: approved layouts, placeholder names, chart conventions, required slide masters, and forbidden edits. You can also maintain standard replacement JSON examples, preferred slide sequences, and validation checks so the pptx skill behaves consistently across quarterly reports, pitch decks, and localized PowerPoint versions.