Google Slides

Google Slides

Use this skill for Google Slides work in Codex local-plugin sessions.

Purpose Of This File

This file is intentionally minimal and only covers:

1. connector loading and runtime boundaries in the Codex node_repl world
2. mandatory routing to reference files
3. routing to workflow references

Detailed write, chart, thumbnail, creation, and final-pass rules live in references/. Latency is not a constraint for this skill, so always read the relevant reference files before performing the task.

Runtime Model

1. Use Google Slides connector or app tools directly from Codex when they are available.
2. Use node_repl only for source processing or small JavaScript utilities that are not connector calls.
3. Do not use embedded-runtime helper snippets or assumed global connector bindings.
4. Connector tools are not called from inside node_repl. Treat connector calls and node_repl helper work as separate execution surfaces.
5. Browser Use is not the Slides editing path. Use connector reads, slide structure, and thumbnails.

Default Routing

Unless the user asks otherwise:

1. New Google Slides deck: first check whether the [@presentations](plugin://presentations@openai-primary-runtime) plugin or the $PowerPoint skill is installed.
2. If either is installed, YOU MUST use [@presentations](plugin://presentations@openai-primary-runtime) or $PowerPoint to create a local .pptx, then import it into Drive as a native Google Slides presentation with mcp__codex_apps__google_drive_import_presentation using upload_mode: "native_google_slides".
3. If neither skill is installed, create the deck directly with Google Slides MCP.
4. Existing Google Slides edit: use Google Slides MCP directly.

Non-Negotiable Output Invariant

Inserted or edited content must match the target deck's existing structure and connector-observable presentation closely enough that it reads as native deck content. Treat wrong target deck, wrong slide, stale object IDs, missing chart updates, leftover placeholder text, clipped text, broken slide order, or unverified visible layout changes as failed output that must be corrected before handoff.

For Slides batch updates, API success is not completion. A fresh post-write LARGE thumbnail and examining the image by curling it is required for every touched slide. You MUST curl the image after requesting thumbnail. No skip. If the [@presentations](plugin://presentations@openai-primary-runtime) plugin or the $PowerPoint skill is installed, you MUST use one of them to create a local .pptx and import it to Google Drive with upload_mode: "native_google_slides".

Canonical Workflow Bias

Prefer one simple proven workflow over a large tree of recovery branches. When a task matches a known successful pattern, follow that pattern directly instead of re-evaluating every possible insertion or fallback path. Do not let accumulated edge-case guardrails turn a straightforward Slides task into a long blocker-analysis exercise.

For deck creation and editing tasks, prefer this general sequence when viable:

1. gather the required source material
2. attach to or create the destination presentation
3. read the deck structure and target slides
4. establish the slide checklist or slide plan
5. write small, grounded batches with live object IDs
6. verify through connector readback and post-batch thumbnails
7. stop once the deck is clean, complete, and scannable

If a simple verified workflow is viable, use it. Do not drift into speculative alternate paths.

Release-Blocker Checklist

Before final handoff, explicitly verify these with connector readback and thumbnails where relevant:

1. the target presentation id, title, and URL are the intended deck
2. every edited slide in scope was read after the write
3. every slide touched by a batch update has a fresh post-write thumbnail check
4. every changed chart is refreshed or replaced in the intended footprint, with obsolete placeholder text removed unless the user asked to keep it
5. every new or edited shape, image, table, and text box stays inside the slide bounds unless intentionally full-bleed
6. no slide in a multi-slide task was skipped, duplicated, or left in a mixed old/new state
7. no visual property is claimed as verified unless connector data or a fresh thumbnail supports it
8. final presentation output is an editable Google Slides deck, not one PNG per slide; verify editable components with mcp__codex_apps__google_drive_get_presentation or mcp__codex_apps__google_drive_get_slide
9. Even though you created a local pptx, do not cite the local pptx path as a deliverable in your final answer. Your final answer must only reference the gsuite link.

Slides

• Content: ensure the content covers everything requested by the user and ensure the storytelling of the overall deck is coherent.
• Search: use web.run's image_query for efficient image search instead of search_query.
• Visual assets: DO NOT use Python to draw any images; DO NOT use programmatic vector shapes for visuals; DO NOT use programmatic drawings of any sort. Use image search or imagegen instead! By default, DO NOT reuse the same image more than once (unless it's a background). Not only do you need to prepare visuals for the main concept, you also need to get decorative visuals. Before sourcing or generating visuals, be mindful of the desired aspect ratio, placement, and cropping options on the slide. For example, if you intend to place text to the left of the image containing a person, you should ask imagegen to put the person on the right side of the image.
• Default styling: use one composition instead of a collection of UI panels. UI-like styling typically includes card grids, pills, badges, button-like text boxes, tab or navigation patterns, repeated modular panels, dense dashboard-style layouts, and other component-library aesthetics that imply interactivity. Use stylized text boxes less, favoring a flat structure on the canvas.
• Visual storytelling: Prioritize visual storytelling by default, favoring real images, generated visuals, diagrams, plots, and charts to convey concepts whenever appropriate rather than relying solely on plain text, especially when the user does not provide assets. As a general rule of thumb, aim for approximately 2-4 visual assets per slide, including meaningful styling elements, adjusting as needed based on the topic, complexity, and overall theme of the task.
• Connectors in diagrams: In the final implementation, create connectors (arrows/edges) before creating entity nodes, so edges appear behind nodes and never cross through node shapes or labels. If this ordering is awkward during early iteration, you may create nodes first in the initial draft, then switch to connectors-first in the revised code.
• Overlap: You MUST fix ALL unintended overlap errors before you deliver the slides! It's of paramount importance!
• Font size: When a template is provided, match its font sizes. Avoid overly small text. When no template or style guidance is given, a good rule of thumb is at least 42pt for deck titles, 32pt for slide titles, and 17pt for body text. If you see overflow/overlap, try cutting content before shrinking text further to improve text layout.
• Text layout: when there is too much text, shorten it. Inspect visually for unexpected text wrapping. NEVER put 2 lines of text into a title/banner text box meant for a single line of text.
• Diagrams implementation: use native PowerPoint shapes for simple diagrams; use Graphviz for complex relational/topological/network-like diagrams; use imagegen for highly aesthetic, illustrative, or scientific infographic diagrams (e.g. chemical structures, circuit diagrams, etc.).
• Title slide: Keep the title slide minimal and simple. Avoid cramming in too much information.
• When to use diagrams: Prefer data-driven charts or plots when applicable; use diagrams only when they improve the storytelling (not to fill empty space).

If any check fails, the task is not complete.

Required Read Order (No Skips)

Before any content write or edit operation:

1. Read references/reference-connector-runtime-and-safety.md.
2. Read references/reference-target-presentation-guard.md.
3. Read references/reference-google-slides-mcp-discovery.md.
4. Read references/reference-request-shapes-and-write-safety.md.
5. Read references/reference-thumbnail-visual-verification.md.
6. Read every task-specific file from the matrix below.
7. If the task spans multiple categories, read all matching files.
8. If uncertain, read every file in references/.

For net-new local .pptx creation, if Default Routing uses [@presentations](plugin://presentations@openai-primary-runtime) or $PowerPoint, read the selected authoring skill before creating the deck.

Do not execute content edits until the required references are read in the current turn.

Connector Load Checklist

1. Confirm the exact target Google Slides URL or presentation id.
2. Resolve and record the presentation id, title, slide count, and target slide object IDs.
3. Treat target-presentation identity as a hard precondition for connector writes.
4. Before each edit pass, identify the slide, object IDs, and current geometry through connector reads.
5. Before every connector write batch, re-read references/reference-target-presentation-guard.md and re-confirm the target presentation and slide object IDs.
6. Read via connector first, using the current Google Slides actions:
   • get presentation, text, or outline
   • get slide
   • get slide thumbnail before and after batch updates, and when visual evidence matters
7. If the source is a template or existing deck that should be preserved, create a copy before editing.
8. Do not claim the connector is unavailable, read-only, or blocked unless the current session has established that through capability evidence.

Task To Reference Map