PowerPoint Presentation Workflows
Tech Stack Target / Version: PowerPoint current desktop or web releases and python-pptx automation.
Use this skill when a .pptx deck is the output and slide composition matters.
- Leverage native parallel subagent dispatch and 200k+ context windows where available.
Current MCP Reality
Presentation MCP tooling is host-dependent. Some clients expose Office presentation tools directly, while others do not. Do not assume stable public tool names. If the current client lacks those tools, use the included local automation script or generate the content structure first and import it into PowerPoint.
Activation Conditions
Use symptom -> action triggers: when one matches, apply this skill and verify with the protocol below.
- Creating a deck from structured content
- Applying templates, branding, and slide layouts
- Updating text, images, or charts inside an existing presentation
- Extracting slide text for review or translation
Practical Workflow
- Confirm whether the client exposes presentation tools.
- Prefer template-driven decks over manual one-off slide formatting.
- Keep one idea per slide and treat text density as a defect.
- Validate the final deck visually before calling it done.
MCP Fallback – Native Automation
When MCP is unavailable, use native automation: python-pptx for .pptx, image export or screenshot checks for visual validation, and manual review for animations or speaker notes. Preserve slide order, layouts, theme fonts, media, notes, and aspect ratio, then reopen or render the deck before claiming success.
Cross-Client Portability
This skill is written to stay usable across GitHub Copilot, Claude Code, and Codex.
- GitHub Copilot: keep the folder in a Copilot-visible skill path or wrap the
workflow in project instructions when folder discovery is unavailable.
- Claude Code: keep the folder in a local skills directory or a compatible plugin source.
- Codex: install or sync the folder into
$CODEX_HOME/skills/powerpoint-ppt and restart Codex after major changes.
MCP Availability And Fallback
Preferred MCP Server: PowerPoint MCP
- Fallback prompt: "Use the PowerPoint Presentation Workflows skill without MCP. Follow the documented local or manual fallback, show the selected tool surface, and report the verification evidence."
- Use
python-pptx, PowerPoint desktop, or a scriptable slide generator when the MCP surface is unavailable.
- Render the final deck and manually verify layout, overflow, and speaker-facing notes before delivery.
- Do not claim an MCP operation was used when the active host does not expose it.
Anti-Patterns
- Writing for the author instead of the reader: It bakes in unstated context and leaves the actual audience unsure what to do next.
- Skipping concrete examples or commands: Abstract guidance is easy to approve and hard to apply correctly.
- Letting links, screenshots, or versions drift: Polished formatting does not help if the instructions are no longer true.
Verification Protocol
Before claiming "skill applied successfully":
- Pass/fail: The Powerpoint Ppt artifact type, target format, and required output fidelity are stated before editing.
- Pass/fail: MCP availability is checked and the native automation fallback path is named when MCP is absent.
- Pass/fail: The produced file or formula is opened, parsed, rendered, or otherwise validated locally.
- Pressure-test scenario: Apply the workflow to a file with formatting, metadata, or conversion edge cases and verify nothing important is lost.
- Success metric: Zero unverified document claims; the artifact itself is the evidence.
Deck Checklist
References & Resources
Scripts
Examples
Related Skills
1---
2name: powerpoint-ppt
3version: "2.0"
4last_updated: 2026-09-08
5tags: [slides, ppt, docs, writing, quality]
6description: "PowerPoint (.pptx) manipulation via MCP server. Use for creating slides, formatting presentations, managing placeholders, adding images, applying templates, or extracting text from .pptx files."
7metadata:
8 source: https://skillmd.com/skills/practicalswan/powerpoint-ppt
9---
10
11# PowerPoint Presentation Workflows
12
13> Tech Stack Target / Version: PowerPoint current desktop or web releases and `python-pptx` automation.
14
15Use this skill when a `.pptx` deck is the output and slide composition matters.
16
17- Leverage native parallel subagent dispatch and 200k+ context windows where available.
18
19
20## Current MCP Reality
21
22Presentation MCP tooling is host-dependent. Some clients expose Office presentation tools directly, while others do not. Do not assume stable public tool names. If the current client lacks those tools, use the included local automation script or generate the content structure first and import it into PowerPoint.
23
24## Activation Conditions
25
26Use symptom -> action triggers: when one matches, apply this skill and verify with the protocol below.
27
28- Creating a deck from structured content
29- Applying templates, branding, and slide layouts
30- Updating text, images, or charts inside an existing presentation
31- Extracting slide text for review or translation
32
33## Practical Workflow
34
351. Confirm whether the client exposes presentation tools.
362. Prefer template-driven decks over manual one-off slide formatting.
373. Keep one idea per slide and treat text density as a defect.
384. Validate the final deck visually before calling it done.
39
40## MCP Fallback – Native Automation
41
42When MCP is unavailable, use native automation: `python-pptx` for `.pptx`, image export or screenshot checks for visual validation, and manual review for animations or speaker notes. Preserve slide order, layouts, theme fonts, media, notes, and aspect ratio, then reopen or render the deck before claiming success.
43
44<!-- MCP:START -->
45
46<!-- PORTABILITY:START -->
47## Cross-Client Portability
48
49This skill is written to stay usable across GitHub Copilot, Claude Code, and Codex.
50
51- GitHub Copilot: keep the folder in a Copilot-visible skill path or wrap the
52 workflow in project instructions when folder discovery is unavailable.
53- Claude Code: keep the folder in a local skills directory or a compatible plugin source.
54- Codex: install or sync the folder into
55 `$CODEX_HOME/skills/powerpoint-ppt` and restart Codex after major changes.
56
57<!-- PORTABILITY:END -->
58
59## MCP Availability And Fallback
60
61Preferred MCP Server: PowerPoint MCP
62
63- Fallback prompt: "Use the PowerPoint Presentation Workflows skill without MCP. Follow the documented local or manual fallback, show the selected tool surface, and report the verification evidence."
64- Use `python-pptx`, PowerPoint desktop, or a scriptable slide generator when the MCP surface is unavailable.
65- Render the final deck and manually verify layout, overflow, and speaker-facing notes before delivery.
66- Do not claim an MCP operation was used when the active host does not expose it.
67
68<!-- MCP:END -->
69
70## Anti-Patterns
71
72- Writing for the author instead of the reader: It bakes in unstated context and leaves the actual audience unsure what to do next.
73- Skipping concrete examples or commands: Abstract guidance is easy to approve and hard to apply correctly.
74- Letting links, screenshots, or versions drift: Polished formatting does not help if the instructions are no longer true.
75
76## Verification Protocol
77
78Before claiming "skill applied successfully":
79
801. Pass/fail: The Powerpoint Ppt artifact type, target format, and required output fidelity are stated before editing.
812. Pass/fail: MCP availability is checked and the native automation fallback path is named when MCP is absent.
823. Pass/fail: The produced file or formula is opened, parsed, rendered, or otherwise validated locally.
834. Pressure-test scenario: Apply the workflow to a file with formatting, metadata, or conversion edge cases and verify nothing important is lost.
845. Success metric: Zero unverified document claims; the artifact itself is the evidence.
85
86## Deck Checklist
87
88- [ ] Title slide is present
89- [ ] Slide layouts are consistent
90- [ ] Fonts and colors match the template
91- [ ] Images are high-resolution and not stretched
92- [ ] Final slides were reviewed in slideshow size, not just as raw XML or text
93
94## References & Resources
95
96### Scripts
97- [PPT Automation Script](./scripts/ppt-automation.py) - Local fallback for building or updating presentation content
98
99### Examples
100- [Presentation Examples](./examples/presentation-examples.md) - Example deck structures and content patterns
101
102## Related Skills
103
104- [documentation-authoring](../documentation-authoring/SKILL.md): Use it when the workflow also needs drafting structured technical or product documents.
105- [documentation-patterns](../documentation-patterns/SKILL.md): Use it when the workflow also needs reusable documentation structures and templates.
106- [documentation-quality](../documentation-quality/SKILL.md): Use it when the workflow also needs documentation review standards and quality gates.
107- [documentation-verification](../documentation-verification/SKILL.md): Use it when the workflow also needs final documentation validation before publishing.