google-slides

# Google Slides Use this skill for Google Slides work where the destination should remain an editable native slide deck. ## Start by classifying the task - READ: summarize a deck, slide, section, or speaker notes. - EDIT: update text, images, charts, tables, links, or notes. - CREATE: make a new presentation. - ADAPT: move source material into a template or reference deck. - CLEANUP: improve layout, spacing, hierarchy, readability, and consistency. - REPAIR: fix placeholders, slide order, broken formatting, stale objects, or missing content. - MIGRATE: preserve source content while changing deck style or destination. ## Target deck identity Before editing: - Confirm the target deck. - Confirm the slide or slide range. - Confirm whether the user wants a copy or direct edits. - Read the current deck structure before changing it. Never edit the wrong deck. When multiple decks could match, clarify or identify candidate titles before making changes. ## Reading decks When summarizing: - Preserve slide order. - Capture the title, main message, evidence, and action item for each slide. - Include speaker notes when relevant. - Separate what the deck says from what you infer. - For long decks, provide section-level summaries plus important slide-level details. ## Editing existing decks - Match the existing visual system: type, color, spacing, footers, page markers, chart style, and layout rhythm. - Populate existing placeholders when they exist. - Avoid adding new freeform boxes when a template placeholder should be used. - Preserve charts, images, speaker notes, links, and media unless asked to replace them. - Make changes in small batches and re-check affected slides. ## Creating new decks For a new deck: - Build a coherent story before writing slides. - Use one main idea per slide. - Make slide titles communicate the takeaway. - Keep body text concise and readable. - Use visuals, charts, or diagrams when they explain better than text. - Keep title slides minimal. Common deck arc: 1. title or framing 2. context or problem 3. key insight 4. evidence or analysis 5. recommendation or solution 6. next steps ## Template and source-deck adaptation When adapting source material into a template: - Preserve required source text, numbers, charts, links, and notes. - Match content to suitable slide archetypes. - Use template placeholders and reusable objects when possible. - Do not leave old template sample content. - Do not silently summarize source material that must remain exact. - Split dense content across slides if needed. ## Visual quality Every touched slide should be checked for: - no unintended overlap - no clipped text - no generic placeholder prompts - no stale template sample copy - readable font sizes - meaningful hierarchy - consistent alignment - consistent margins - images cropped around the important subject - charts with readable labels and units ## Charts, tables, and evidence - Refresh or replace charts only in the intended footprint. - Remove obsolete chart placeholder text. - Keep chart labels, units, and legends readable. - Use tables for concise comparisons, not dense prose. - Preserve source data meaning. - Do not claim a visual change is verified unless it has been checked in the deck. ## Speaker notes For notes: - Preserve existing speaker notes unless the user asks to remove them. - Keep notes tied to the correct slide. - Use notes for presenter detail that would clutter the slide. - When migrating decks, verify important notes did not disappear. ## Final QA checklist Before finishing: 1. Confirm the final deck is the intended Google Slides presentation. 2. Confirm every slide in scope was read after editing. 3. Confirm all requested slides were created, edited, moved, or cleaned up. 4. Check slide order. 5. Check that no old placeholders or sample copy remain. 6. Check that text, charts, images, tables, links, and notes are preserved or changed according to the request. 7. Check readability, overlap, clipping, and layout consistency. 8. Mention any tradeoffs if the source content was too dense or formatting could not be perfectly preserved.