google-slides-template-surgery
Perform structural rework in connected Google Slides decks. Use when local visual cleanup is not enough and repeated layout defects require batch_update structure edits plus strict verification.
Best use case
google-slides-template-surgery is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Perform structural rework in connected Google Slides decks. Use when local visual cleanup is not enough and repeated layout defects require batch_update structure edits plus strict verification.
Teams using google-slides-template-surgery should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/google-slides-template-surgery/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How google-slides-template-surgery Compares
| Feature / Agent | google-slides-template-surgery | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Perform structural rework in connected Google Slides decks. Use when local visual cleanup is not enough and repeated layout defects require batch_update structure edits plus strict verification.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Google Slides Template Surgery Use this skill for structural Google Slides cleanup. This is the escalation path after normal visual iteration fails to converge. Start with local slide fixes first. Escalate to template surgery only when one of these is true: - the same spacing or overlap problem repeats across multiple slides - the slide structure is fundamentally bad and local nudges keep re-breaking the layout - the user explicitly asks to rework the template, placeholders, or repeated layout pattern - the deck needs a consistent structural reset, not just cosmetic polish For simple cleanup, prefer [google-slides-visual-iteration](../google-slides-visual-iteration/SKILL.md). ## Required Tooling Confirm the runtime exposes: - `get_presentation` or `get_presentation_text` - `get_slide` - `get_slide_thumbnail` - `batch_update` If any of those are missing, stop and explain that the deck cannot be safely restructured from Codex. ## Workflow 1. Read the deck before changing it. - Inventory slide types, repeated layouts, title patterns, image-heavy slides, and broken outliers. - Fetch the target slide structure with `get_slide` before writing. - Use live object IDs only. Never guess them. 2. Decide whether to patch or rebuild. - Patch in place when the slide has the right elements but the geometry is bad. - Duplicate or recreate structure when the slide is too broken for safe incremental edits. - Prefer one layout pattern at a time instead of broad deck-wide surgery in a single batch. 3. Plan the operation as a small structural batch. - Keep each batch narrow and intentional. - Do not mix unrelated edits just because they touch the same slide. - Copy request shapes from `./references/batch-update-recipes.md` instead of inventing them from memory. 4. Verify on representative slides. - After each structural batch, re-fetch thumbnails for the edited slide and 1-2 sibling slides that use the same pattern. - Do not assume a successful write means the layout is improved. - Finish the representative edited slide with [visual-change-loop](./visual-change-loop.md) before rolling the pattern out broadly. 5. Roll forward carefully. - Once a structural pattern works, apply it to the next matching slides. - Reuse the same margin logic, title placement, and content rhythm across sibling slides. ## Structural Rules - Prefer duplicating a clean slide pattern over endlessly mutating a broken one. - Prefer deleting or replacing redundant elements over stacking new ones on top of old ones. - Preserve user content by default. Structural cleanup is not permission to rewrite the narrative. - Keep batches reversible. If the slide gets worse after a pass, correct the structure before adding more edits. - If repeated edits are failing, stop and explain what constraint is blocking clean automation. ## Common Surgery Cases Use this skill for: - rebuilding crowded title/content slides with a cleaner text-and-image split - replacing a bad placeholder stack with a simpler repeated pattern - deleting duplicate or stale decorative shapes that keep causing overlap - normalizing title position, body width, and image frame placement across a section - duplicating a strong “golden” slide structure and adapting it for sibling slides Do not use this skill for: - one-off typo fixes - simple repositioning on a single slide - content generation from scratch - freeform redesign when the user only asked for cleanup ## Verification Standard A structural pass is only done when: - the target slide no longer has clipping or overlaps - the new structure looks stable in the thumbnail, not just valid in raw JSON - sibling slides using the same pattern still look coherent - no stale elements remain hidden behind the new layout ## References Read these before the first write: - `./references/template-surgery-playbook.md` - `./references/batch-update-recipes.md`
Related Skills
google-slides
Inspect, create, import, summarize, and update Google Slides presentations through connected Google Slides data. Use when the user wants to find a deck, read slide structure, summarize a presentation or specific slide, understand charts, graphs, or other slide visuals by combining slide text with thumbnail-based image understanding, create a new presentation, import a `.ppt`, `.pptx`, or `.odp`, or make general content edits in Google Slides. For visual polish on an existing deck, such as formatting cleanup, alignment fixes, overflow cleanup, or slide-by-slide deck cleanup, prefer `google-slides-visual-iteration`.
google-slides-visual-iteration
Iteratively inspect and polish existing connected Google Slides presentations in Codex using slide thumbnails plus raw Slides edits. Use when a user asks to fix a slide visually, clean up formatting, improve slide quality, make a deck look better, fix alignment, spacing, overlap, overflow, crowding, awkward whitespace, or deck-wide visual consistency in an existing Google Slides deck or shared Slides link, especially when the work should follow a thumbnail -> diagnose -> batch_update -> re-thumbnail verification loop.
google-slides-template-migration
Migrate a Google Slides deck onto a target template. Use when the user wants to preserve source content while rebuilding slides from a branded template structure instead of making incremental in-place edits.
google-slides-import-presentation
Import a local `.ppt`, `.pptx`, or `.odp` file into Google Slides, verify the resulting native deck, and hand it off to the right follow-on workflow. Use when the user wants to convert a presentation file into a native Google Slides deck before follow-on work.
google-sheets
Analyze and edit connected Google Sheets with range precision. Use when the user wants to find a spreadsheet, inspect tabs or ranges, search rows, plan formulas, clean or restructure tables, write concise summaries, or make explicit cell-range updates.
google-sheets-formula-builder
Design, repair, and roll out Google Sheets formulas with better syntax recall and validation discipline. Use when the user wants to add a formula column, fix a broken formula, choose between a row formula and a spill formula, build a lookup or filter formula, or turn repeated logic into a reusable named function.
google-sheets-chart-builder
Design, create, and revise Google Sheets charts with better chart-spec recall and editing discipline. Use when the user wants to add a chart to a sheet, choose the right chart type for existing data, repair a broken chart, update a chart's data series, or reposition or resize a chart after creating it.
google-drive
Use connected Google Drive as the single entrypoint for Drive, Docs, Sheets, and Slides work. Use when the user wants to find, fetch, organize, share, export, copy, or delete Drive files, or summarize and edit Google Docs, Google Sheets, and Google Slides through one unified Google Drive plugin.
google-docs
Inspect and edit Google Docs documents with index-aware batch updates. Use when the user wants to read document text or structure, find paragraph indexes, rewrite sections in place, edit tables, or apply style-aware document changes with Google Docs tools.
google-calendar
Manage scheduling and conflicts in connected Google Calendar data. Use when the user wants to inspect calendars, compare availability, review conflicts, find a meeting room, review event notes or attachments, or draft exact create, update, reschedule, or cancel changes with timezone-aware details.
google-calendar-meeting-prep
Build a practical meeting prep brief from a connected Google Calendar event and its nearby context. Use when the user wants to prepare for an upcoming meeting, understand what to read beforehand, pull in linked notes or docs, or get a concise brief on what the meeting appears to require.
google-calendar-group-scheduler
Find and rank good meeting times for multiple people using connected Google Calendar data. Use when the user wants to schedule a group meeting, compare candidate slots across several attendees, find the best compromise time, or add a room check after narrowing the attendee-compatible options.