google-slides

name	google-slides
description	Create, read, copy, edit, repair, restyle, and verify native Google Slides presentations through Mail Pounder. Use when Codex must summarize a deck, follow a native template, update slide content, inspect thumbnails or tables, preserve layout structure, or apply Slides batch updates.

Google Slides

Use Mail Pounder's native Slides tools and preserve the presentation's visual system instead of flattening it into generic slides.

Workflow

1. Ground the deck with google_drive_get_presentation, google_drive_get_presentation_outline, and google_drive_get_presentation_text.
2. Inspect google_drive_get_slide, google_drive_get_slide_thumbnail, and google_drive_get_presentation_tables where layout or visual evidence matters.
3. For a template or prior-period deck, use google_drive_copy_file or google_drive_create_presentation_0cb5796bb4da. Edit only the copy unless the user explicitly targets the source.
4. For local files, use google_drive_import_presentation with upload_mode: "native_google_slides".
5. Apply coherent native mutations with google_drive_batch_update_presentation.
6. Re-read the final slide order, IDs, text, tables, and representative thumbnails.

Template discipline

• Match source exemplars by narrative role, density, evidence type, and hierarchy.
• Preserve slide-local structure, mixed text styles, native bullets, links, tables, charts, notes, and media types where supported.
• Map every inherited image, chart, screenshot, device frame, or placeholder to keep, replace, or delete. Never leave stale template content.
• Preserve media aspect ratios. Fit screenshots and charts without cropping meaning-bearing content.
• Avoid empty bullet paragraphs, typed bullet glyphs, generic placeholder text, overcrowding, and unreadably small narrative text.
• Verify the finished deck before returning its observed URL.