Anthropic / skills/pptx/SKILL.md
PowerPoint Presentations
A presentation authoring and editing workflow with OOXML helpers, template guidance and rendered-slide review. Useful for editable decks, with substantial file-mutation and licensing caveats.
Source reviewed · reviewed · Named sources were inspected. No runtime results are established by this label.
01 / Task fit
Where it may help.
These are intended uses indicated by the upstream material. They are not measured outcomes.
- Editable presentation drafts and template-based updates
- Separating content, package-structure and rendered-slide review
What it is
A skill that tells an agent how to create, inspect and edit PowerPoint files. It combines presentation-writing guidance with scripts for duplicating slides, cleaning package parts, making thumbnails and checking file structure. The skill is a workflow; the actual work depends on a host agent, local tools and your source material.
Why you might use it
Use it when a deck must remain editable or fit an existing template. Its guidance addresses details that a text-only slide outline misses: relationships between package parts, notes, charts, layout choices and a separate visual inspection step. A file that opens is still not proof that its content fits or reads well.
Put it in context.
Illustrative requests and outputs to review. These examples are separate from the recorded evaluation below.
Refresh a template-based operations deck
Example request
Provide an approved template and a synthetic five-item status table. Ask for one summary slide, three workstream slides and a decision slide, saving a separate output and retaining notes and editable text.
What to look for. A draft PowerPoint file plus a slide-by-slide content and visual review in an authorized runtime.
Before you rely on it. This example was not executed. Duplicated slides may share chart or embedded-object parts; editing one can affect another. Preserve the original and inspect every rendered slide.
Remove retired material from a training deck
Example request
On a disposable copy, remove two retired topics, finish the slide order, then inspect which media and relationships the cleanup helper would discard.
What to look for. A smaller draft deck with the intended slide list and no stale package references, subject to independent validation.
Before you rely on it. The cleanup helper deletes files. Source review found prefix/quote-sensitive slide discovery and a potential Windows path mismatch; neither was runtime-tested here.
02 / Setup & access
What it asks of your environment.
Requirements
- A host agent with file and shell access in an environment where the per-skill terms permit use. The reviewed license is proprietary, not the repository's Apache-licensed skill terms.
- Node and pptxgenjs for new decks; Python and named XML/image packages for helpers; markitdown for text extraction; LibreOffice and PDF image tools for rendering. Upstream claims of preinstallation do not establish availability on your machine.
- An approved template, usable fonts and source content. Local file work does not inherently require an account; the host service and license conditions are separate.
Permissions & data access
- Read presentation ZIP/XML, images, notes and embedded content. Write a new package or replace the input when an output path is omitted.
- Run local Python/Node/native renderers and delete unreferenced files during cleanup. Dependency installation may contact package registries; granting the skill does not create a file-access sandbox.
Instructions alone do not enforce a sandbox. The agent host, connected tools and approvals determine what the skill can actually read, change or send.
03 / Things to check
Security concerns & practical limits.
These concerns follow from the reviewed sources. They describe possible exposure or required review; they are not confirmed vulnerabilities.
Review before use
Runtime not run: restrictive per-skill terms
The pinned PPTX license labels all skill components subject to Anthropic-service agreements and adds restrictions on copying outside those services, derivatives and redistribution. This pass stopped at source review; no PPTX helper was imported or executed here.
Review before use
Cleanup can mistake an XML naming change for an empty deck
Source trace: slide discovery looks for literal p:sldId elements and double-quoted r:id attributes. If a valid presentation uses another XML prefix or quoting form, both discovery and its refusal guard can miss the slide list. The cleanup path can then treat on-disk slides as orphaned. This is a source-level concern, not a reproduced deletion; use a disposable copy and inspect the slide list before cleanup.
Review before use
Windows path formatting can leave deleted-part declarations
Source trace: removed file paths are recorded with str(Path), while content-type PartName values use forward slashes. On Windows the comparison can miss a deleted part. No Windows cleanup was executed; check the resulting package with an independent validator in an authorized runtime.
Review before use
Editing helpers can overwrite or delete content
The entrypoint documents in-place editing, add_slide.py defaults to replacing its input package unless an output path is supplied, and clean.py deletes unreferenced parts. The review did not establish rollback or recovery. Work from a retained original and a separate output.
Limits and nuances
- Runtime not run because the reviewed per-skill terms restrict the evaluation context. These findings come from source inspection only.
- No PowerPoint/LibreOffice rendering, template interoperability, generated-deck quality, font behavior or malicious-document resilience was evaluated.
04 / Review record
What we checked. What’s still open.
Recorded review scope
- Manual review of purpose, dependencies, mutation boundaries, path helpers and selected cleanup control flow. Runtime not run.
- Pinned entrypoint, per-skill license and each file named in the report source manifest
Not tested or established
- Runtime not run because the reviewed per-skill terms restrict the evaluation context. These findings come from source inspection only.
- No PowerPoint/LibreOffice rendering, template interoperability, generated-deck quality, font behavior or malicious-document resilience was evaluated.
- One bounded pass at one pinned revision; no model-effectiveness baseline, repeated trials, security certification or assurance about future versions.
- No private files, credentials, authenticated accounts, paid requests or real customer workflows. Transitive dependencies and current vulnerability advisories were not audited.
- Review date
- Source revision
dbd4588f9e1033efb41dad4bef2f7947c8993d44- Our relationship
- Explored. Investigated through the recorded review. No use or replication is claimed.
Upstream content can change after review. A repository revision identifies source scope; it does not prove that every script, dependency or runtime behavior was tested. How freshness is handled.
Recorded evaluation / Source review
Results with their limits attached.
Runtime not run because of the per-skill license boundary. Six manual source-review expectations: four met and two concerns identified in cleanup logic. No presentation was generated, edited or rendered.
- Passed
- 4
- Failed
- 2
- Total recorded
- 6
These counts refer to the cases in this report. They are not a benchmark against other skills. A source review does not establish runtime behavior.
Read the evidence reportThe report provides the case definitions, observations and baseline scope. Missing baselines or untested behaviors remain limitations.
Recorded environment
- Manual review of pinned public source; no upstream code imported or executed
Recorded commands (1)
Commands document this evaluation. They are not setup instructions for your environment.
Read pinned entrypoint, per-skill license and named helper control flow; record findings without executing the upstream skill.Findings from this evaluation
Needs attention
Runtime not run: restrictive per-skill terms
The pinned PPTX license labels all skill components subject to Anthropic-service agreements and adds restrictions on copying outside those services, derivatives and redistribution. This pass stopped at source review; no PPTX helper was imported or executed here.
Needs attention
Cleanup can mistake an XML naming change for an empty deck
Source trace: slide discovery looks for literal p:sldId elements and double-quoted r:id attributes. If a valid presentation uses another XML prefix or quoting form, both discovery and its refusal guard can miss the slide list. The cleanup path can then treat on-disk slides as orphaned. This is a source-level concern, not a reproduced deletion; use a disposable copy and inspect the slide list before cleanup.
Needs attention
Windows path formatting can leave deleted-part declarations
Source trace: removed file paths are recorded with str(Path), while content-type PartName values use forward slashes. On Windows the comparison can miss a deleted part. No Windows cleanup was executed; check the resulting package with an independent validator in an authorized runtime.
Needs attention
Editing helpers can overwrite or delete content
The entrypoint documents in-place editing, add_slide.py defaults to replacing its input package unless an output path is supplied, and clean.py deletes unreferenced parts. The review did not establish rollback or recovery. Work from a retained original and a separate output.
Evaluation limitations
- Runtime not run because the reviewed per-skill terms restrict the evaluation context. These findings come from source inspection only.
- No PowerPoint/LibreOffice rendering, template interoperability, generated-deck quality, font behavior or malicious-document resilience was evaluated.
- One bounded pass at one pinned revision; no model-effectiveness baseline, repeated trials, security certification or assurance about future versions.
- No private files, credentials, authenticated accounts, paid requests or real customer workflows. Transitive dependencies and current vulnerability advisories were not audited.
05 / Reuse & discovery
License, attribution & popularity.
Proprietary / service terms
The separate per-skill license was read at this revision. It ties use to Anthropic-service terms and adds restrictions on copying, derivatives and redistribution; this source review does not grant permission to install or reuse it.
Why it is in this collection
Selected from a widely followed repository and dated skills.sh directory observations. Installs are rounded directory displays, not independently verified users or evidence of quality, safety or growth.
182,031 repository stars
- Scope
- Entire anthropics/skills repository, not this individual skill
- Observed
- Time window
- Snapshot observed 2026-10-19
Popularity and inclusion do not establish quality, compatibility or security. Counts belong to their named metric and date; they are not a current ranking.
Dated discovery signal
Discovery snapshots.
238,200 skill installs on skills.sh · Page labels this Installs without stating a time window
Observed . Scope: Individual pptx directory listing; rounded display.
Selection snapshot; displayed K value converted to an approximate integer. No rate, rank or measured trend is inferred.
Snapshot source ↗06 / Follow the evidence
Go to the original.
- Pinned skill instructions github.com
- Per-skill license github.com
- add_slide.py inspected source github.com
- clean.py inspected source github.com
- __init__.py inspected source github.com
- Dated directory interest signal www.skills.sh
IonBin’s source notes are independent assessments. Upstream authors retain their work and attribution. This page does not install or execute the skill.