Pptx Author
- 1 installs
- 34k repo stars
- Updated August 4, 2026
- anthropics/financial-services-plugins
Pptx-author is a Claude skill that produces a .pptx PowerPoint file on disk headlessly with python-pptx for managed-agent sessions.
About
Pptx-author is a skill that produces a PowerPoint file on disk in headless sessions instead of driving a live Office document. It writes a short python-pptx script to build the deck from a firm template or default layouts, saving to ./out and returning the file path for an orchestration layer to collect. A developer uses it in managed-agent runs with no open Office app, and it never emails or uploads the result.
- Produces a .pptx file on disk headlessly using python-pptx, for managed-agent sessions
- Writes to ./out/<name>.pptx and returns the relative path for the orchestration layer
- Fallback for headless runs when live-Office powerpoint tools are unavailable
Pptx Author by the numbers
- 1 all-time installs (skills.sh)
- Ranked #565 of 688 Office & Documents skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
pptx-author capabilities & compatibility
- Use cases
- presentations
What pptx-author says it does
Produce a .pptx file on disk (headless) instead of driving a live PowerPoint document — for managed-agent sessions with no open Office app.
Write to `./out/<name>.pptx`. Create `./out/` if it does not exist.
No external sends.** This skill writes a file; it never emails or uploads.
npx skills add https://github.com/anthropics/financial-services-plugins --skill pptx-authorAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| repo stars | ★ 34k |
| Last updated | August 4, 2026 |
| Repository | anthropics/financial-services-plugins ↗ |
What it does
Produce a .pptx deck file on disk headlessly with python-pptx when no live Office session is available.
Who is it for?
Headless managed-agent runs that must deliver a PowerPoint deck as a file artifact
Skip if: Sessions where mcp__office__powerpoint_* tools are available; use those live-document tools instead
When should I use this skill?
When running headless and you need to deliver a PowerPoint deck as a file rather than editing a live document
What you get
A .pptx file written to ./out/<name>.pptx with its relative path returned for the orchestration layer to collect.
- .pptx file at ./out/<name>.pptx
By the numbers
- output contract: ./out/<name>.pptx
Files
pptx-author
Use this skill when running headless (managed-agent / CMA mode) and you need to deliver a PowerPoint deck as a file artifact rather than editing a live document via mcp__office__powerpoint_*.
Output contract
- Write to
./out/<name>.pptx. Create./out/if it does not exist. - Return the relative path in your final message so the orchestration layer can collect it.
How to build the deck
Write a short Python script and run it with Bash. Use python-pptx:
from pptx import Presentation
from pptx.util import Inches, Pt
prs = Presentation("./templates/firm-template.pptx") # if a template is provided
# or: prs = Presentation()
slide = prs.slides.add_slide(prs.slide_layouts[5]) # title-only
slide.shapes.title.text = "Valuation Summary"
# ... add tables / charts / text boxes ...
prs.save("./out/pitch-<target>.pptx")Conventions (mirror the live-Office pitch-deck skill)
- One idea per slide. Title states the takeaway; body supports it.
- Every number traces to the model. If a figure comes from
./out/model.xlsx, footnote the sheet and cell. - Use the firm template when one is mounted at
./templates/; otherwise default layouts. - Charts: prefer embedding a PNG rendered from the model over native pptx charts when fidelity matters.
- No external sends. This skill writes a file; it never emails or uploads.
When NOT to use
If mcp__office__powerpoint_* tools are available (Cowork plugin mode), use those instead — they drive the user's live document with review checkpoints. This skill is the file-producing fallback for headless runs.
Related skills
Lark DocGenerate, update, and maintain structured documentation directly inside Lark/Feishu using natural language and agentic workflows.494kLark DriveLet their coding agents read, create, update and search documents stored in Lark (Feishu) Drive directly from prompts.493kLark SheetsConnect Claude, Cursor or other agents directly to Feishu/Lark spreadsheets for live data reads, writes, and structured automation.493kLark WikiGenerate, update, and sync structured knowledge bases inside Lark (Feishu) directly from code, specs, or agent output.493kLark WhiteboardGenerate, edit, and collaborate on visual diagrams and flowcharts directly inside Claude, Cursor or other agents.493kLark SlidesInstantly generate polished, professional slide decks from specs, roadmaps, or meeting notes using Lark/Feishu.493kFAQ
Where does pptx-author write the file?
To ./out/<name>.pptx, creating ./out/ if it does not exist, and returns the relative path in the final message.
When should I not use it?
When mcp__office__powerpoint_* tools are available; those drive the user's live document with review checkpoints instead.