Publish Sign in

Editing Presentations

Edit existing PowerPoint files or templates with XML-safe workflows.

You say
Install this skill Read the source first Free Written by MiniMax-AI · unverified publisher
Context cost
1.7k tokensestimated from the bundle, loaded when it triggers
Bundle
1 file · 6.9 kBtext throughout, nothing executable
Licence
Proprietary. LICENSE.txt has complete termsfree to use
Last change
—no release on file
Servers it uses
Noneruns standalone

What it does

Edit existing PowerPoint files or templates with XML-safe workflows. Use for template-based deck updates: analyze layouts, map content to slides, duplicate/reorder/delete slides safely, edit slide XML in parallel, clean orphaned assets, and repack validated PPTX output.

Installed, it changes the agent in these ways.

What this skill changes about the agent is not written down here yet. The listing was collected from its source, and the description is in its own SKILL.md.

Output format

Produces one artefact, exactly shaped.

content
Filed under

Learning & Documentation

The skill itself

This is the whole product. A skill is instructions the model reads, so there is nothing behind the listing you cannot see first — the front matter loads with every session, and the body below it loads when the skill triggers.

SKILL.md6.9 kB · 194 lines
--- name: ppt-editing-skill description: "Edit existing PowerPoint files or templates with XML-safe workflows. Use for template-based deck updates: analyze layouts, map content to slides, duplicate/reorder/delete slides safely, edit slide XML in parallel, clean orphaned assets, and repack validated PPTX output." license: Proprietary. LICENSE.txt has complete terms ---
7# Editing Presentations
8
9## Template-Based Workflow
10
11When using an existing presentation as a template:
12
131. **Copy and analyze**:
14 ```bash
15 cp /path/to/user-provided.pptx template.pptx
16 python -m markitdown template.pptx > template.md
17 ```
18 Review template.md to see placeholder text and slide structure.
19
202. **Plan slide mapping**: For each content section, choose a template slide.
21
22 ⚠️ **USE VARIED LAYOUTS** — monotonous presentations are a common failure mode. Don't default to basic title + bullet slides. Actively seek out:
23 - Multi-column layouts (2-column, 3-column)
24 - Image + text combinations
25 - Full-bleed images with text overlay
26 - Quote or callout slides
27 - Section dividers
28 - Stat/number callouts
29 - Icon grids or icon + text rows
30
31 **Avoid:** Repeating the same text-heavy layout for every slide.
32
33 Match content type to layout style (e.g., key points → bullet slide, team info → multi-column, testimonials → quote slide).
34
353. **Unpack**
36
374. **Build presentation** (do this yourself, not with subagents):
38 - Delete unwanted slides (remove from <p:sldIdLst>)
39 - Duplicate slides you want to reuse (add_slide.py)
40 - Reorder slides in <p:sldIdLst>
41 - **Complete all structural changes before step 5**
42
435. **Edit content**: Update text in each slide{N}.xml.
44 **Use subagents here if available** — slides are separate XML files, so subagents can edit in parallel.
45
466. **Clean**
47
487. **Pack**
49
50## Output Structure
51
52Copy the user-provided file to template.pptx in cwd. This preserves the original and gives a predictable name for all downstream scripts.
53
54```bash
55cp /path/to/user-provided.pptx template.pptx
56```
57
58```text
59./
60├── template.pptx # Copy of user-provided file (never modified)
61├── template.md # markitdown extraction
62├── unpacked/ # Editable XML tree
63└── edited.pptx # Final repacked deck
64```
65
66Minimum expected deliverable: edited.pptx.
67
68---
69
70## Scripts
71
72| Script | Purpose |
73|--------|---------|
74| unpack.py | Extract and pretty-print PPTX |
75| add_slide.py | Duplicate slide or create from layout |
76| clean.py | Remove orphaned files |
77| pack.py | Repack with validation |
78
79
80Removes slides not in <p:sldIdLst>, unreferenced media, orphaned rels.
81
82
83Always write to /tmp/ first, then copy to the final path. Python's zipfile module uses seek internally, which fails on some volume mounts (e.g. Docker bind mounts). Writing to a local temp path avoids this.
84
85Validates, repairs, condenses XML, re-encodes smart quotes.
86
87---
88
89## Slide Operations
90
91Slide order is in ppt/presentation.xml → <p:sldIdLst>.
92
93**Reorder**: Rearrange <p:sldId> elements.
94
95**Delete**: Remove <p:sldId>, then run clean.py.
96
97**Add**: Use add_slide.py. Never manually copy slide files—the script handles notes references, Content_Types.xml, and relationship IDs that manual copying misses.
98
99---
100
101## Editing Content
102
103**Subagents:** If available, use them here (after completing step 4). Each slide is a separate XML file, so subagents can edit in parallel. In your prompt to subagents, include:
104- The slide file path(s) to edit
105- **"Use the Edit tool for all changes"**
106- The formatting rules and common pitfalls below
107
108For each slide:
1091. Read the slide's XML
1102. Identify ALL placeholder content—text, images, charts, icons, captions
1113. Replace each placeholder with final content
112
113**Use the Edit tool, not sed or Python scripts.** The Edit tool forces specificity about what to replace and where, yielding better reliability.
114
115### Formatting Rules
116
117- **Bold all headers, subheadings, and inline labels**: Use b="1" on <a:rPr>. This includes:
118 - Slide titles
119 - Section headers within a slide
120 - Inline labels like (e.g.: "Status:", "Description:") at the start of a line
121- **Never use unicode bullets (•)**: Use proper list formatting with <a:buChar> or <a:buAutoNum>
122- **Bullet consistency**: Let bullets inherit from the layout. Only specify <a:buChar> or <a:buNone>.
123
124---
125
126## Common Pitfalls
127
128### Template Adaptation
129
130When source content has fewer items than the template:
131- **Remove excess elements entirely** (images, shapes, text boxes), don't just clear text
132- Check for orphaned visuals after clearing text content
133- Run content QA with markitdown to catch mismatched counts
134
135When replacing text with different length content:
136- **Shorter replacements**: Usually safe
137- **Longer replacements**: May overflow or wrap unexpectedly
138- Verify with markitdown after text changes
139- Consider truncating or splitting content to fit the template's design constraints
140
141**Template slots ≠ Source items**: If template has 4 team members but source has 3 users, delete the 4th member's entire group (image + text boxes), not just the text.
142
143### Multi-Item Content
144
145If source has multiple items (numbered lists, multiple sections), create separate <a:p> elements for each — **never concatenate into one string**.
146
147**❌ WRONG** — all items in one paragraph:
148```xml
149<a:p>
150 <a:r><a:rPr .../><a:t>Step 1: Do the first thing. Step 2: Do the second thing.</a:t></a:r>
151</a:p>
152```
153
154**✅ CORRECT** — separate paragraphs with bold headers:
155```xml
156<a:p>
157 <a:pPr algn="l"><a:lnSpc><a:spcPts val="3919"/></a:lnSpc></a:pPr>
158 <a:r><a:rPr lang="en-US" sz="2799" b="1" .../><a:t>Step 1</a:t></a:r>
159</a:p>
160<a:p>
161 <a:pPr algn="l"><a:lnSpc><a:spcPts val="3919"/></a:lnSpc></a:pPr>
162 <a:r><a:rPr lang="en-US" sz="2799" .../><a:t>Do the first thing.</a:t></a:r>
163</a:p>
164<a:p>
165 <a:pPr algn="l"><a:lnSpc><a:spcPts val="3919"/></a:lnSpc></a:pPr>
166 <a:r><a:rPr lang="en-US" sz="2799" b="1" .../><a:t>Step 2</a:t></a:r>
167</a:p>
168<!-- continue pattern -->
169```
170
171Copy <a:pPr> from the original paragraph to preserve line spacing. Use b="1" on headers.
172
173### Smart Quotes
174
175Handled automatically by unpack/pack. But the Edit tool converts smart quotes to ASCII.
176
177**When adding new text with quotes, use XML entities:**
178
179```xml
180<a:t>the &#x201C;Agreement&#x201D;</a:t>
181```
182
183| Character | Name | Unicode | XML Entity |
184|-----------|------|---------|------------|
185| " | Left double quote | U+201C | &#x201C; |
186| " | Right double quote | U+201D | &#x201D; |
187| ' | Left single quote | U+2018 | &#x2018; |
188| ' | Right single quote | U+2019 | &#x2019; |
189
190### Other
191
192- **Whitespace**: Use xml:space="preserve" on <a:t> with leading/trailing spaces
193- **XML parsing**: Use defusedxml.minidom, not xml.etree.ElementTree (corrupts namespaces)
194
In the file
SKILL.md949 words
Files1
LicenceProprietary. LICENSE.txt has complete terms
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈90
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
1,635
on trigger
The instruction body, read only when the skill fires.
0.86%
of a 200k window
Ten skills this size would take about 9% of the window before you open a file.
050k100k150k200k context window

1.7k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Middling. Fine to keep on in a project where you use it weekly, worth unloading in one where you never do.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

Adoption
Installsnone yet
Ratingno reviews yet

The procedure it runs

The procedure has not been published here. It is in the skill’s own SKILL.md, which its author has not sent to the marketplace yet.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

It writes no files and reaches no network. All it changes is how the model reasons and writes.

What it asks for
Writes filesno
Network accessno

Read from the allowed-tools line of this skill’s own SKILL.md. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

1 file, 6.9 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md6.9 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 1 file you can review in full before installing. The Proprietary. LICENSE.txt has complete terms licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# Editing Presentations · 1.7k tokens when loaded npx mcprush@latest skill add minimax-ai/editing-presentations

Writes to .claude/skills/editing-presentations/ in the current project. Add --global to put it in your home directory instead, for every project.

Which clients pick it up on their own

A skill is a folder of text. A client with a skills folder reads it without being told; everywhere else the same text works, it is just handed to the model rather than found.

Claude Code.claude/skills/
Claude Desktop
ChatGPT
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok.grok/skills/
Zed.agents/skills/
Windsurf.windsurf/skills/
Agent SDK.claude/skills/
HTTP / API
This release
Versionnot versioned
Publishedno release date on file
PriceFree
Referenceminimax-ai/editing-presentations

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v
  • No earlier releases have been published to the marketplace.
Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

—no reviews yet · no installs yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Who can post

Only accounts that have had the skill installed for fourteen days, so a review is written after living with it rather than after reading it. Publishers may reply once.

Who wrote it

MI
MiniMax-AI

Publishes on mcprush.

0 servers listed3 skills listednot claimed
Profile
Publisher
Servers0
Claim this skill