# google-slides

Extracts design systems from existing Google Slides decks to build slides matching a reference template. Rebuilds and updates native presentations without breaking styles.

- skill · `type=skill` · Codex, ChatGPT · 21 installs · ★ 7596
- Author: OpenAI · official OpenAI repository
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/openai/plugins/tree/HEAD/plugins/google-drive/skills/google-slides/SKILL.md
- Updated: 2026-10-08
- HTML: https://affpapa.org/en/nevibecode/skills/google-slides

## What it does

This skill does not generate presentations from scratch. Blank decks route to the `presentations` tool instead. It activates when you provide a native Google Slides deck as a reference, a prior-period report, or a corporate template. The workflow copies the target template once, edits the copy directly inside the `ChatGPT` folder on Google Drive, and leaves your original file untouched.

Under the hood, execution follows strict technical phases. A Node.js helper exports the document tree into `raw-template.json`. Next, `parse_template_design_system.mjs` maps layout IDs and theme colors into `design-system.json`. For visual checks, the deck exports to PDF, and `pdftoppm` converts every slide into PNG images at 120 DPI.

Running this without an existing deck makes no sense, as every layout rule depends on parsing a native reference.

## Requirements
- Works with: Google Drive, Google Workspace

## Install

### Codex (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add openai/plugins --skill google-slides -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/google-slides/SKILL.md` — For all projects use ~/.agents/skills/

### Claude Code

1. **Skills CLI (Vercel)**
```bash
npx skills add openai/plugins --skill google-slides -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/google-slides/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/google-slides/

### Cursor

**Manually: put the files in place**
- File: `.cursor/skills/google-slides/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install openai/plugins google-slides
```

2. **Manually: put the files in place**
- File: `.github/skills/google-slides/SKILL.md`

### Gemini CLI

**Platform CLI**
```bash
gemini skills install https://github.com/openai/plugins --path plugins/google-drive/skills/google-slides
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/google-slides/SKILL.md` — The legacy .windsurf/skills/ path still works

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/openai/plugins/tree/HEAD/plugins/google-drive/skills/google-slides/SKILL.md

## When to use it
- adapt corporate Google Slides templates for new presentations
- update prior-period decks while preserving native styles
- repair broken slide layouts and clean up formatting
- extract theme colors and master layouts into a JSON schema

## Example prompts
- Use the template deck `1abc...` to build a Q4 update report
- Clean up formatting and fix layout issues in presentation `1xyz...`

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 45748b52df4e2063.

BEGIN THIRD-PARTY FILE 45748b52df4e2063
````text
---
name: google-slides
description: Route Google Slides authoring requests and derive a design system from a native template or reference deck. Use this skill when the user provides an existing native Google Slides deck as a template, reference, or prior-period source, or asks to edit, update, repair, restyle, or clean up an existing native Google Slides deck. Use the Presentations skill instead for net-new presentation creation when no existing native Google Slides deck must be followed.
---

# Google Slides

### Presentations clarification questions

- Ask for new presentations or major rewrites. Skip this for edits/conversions.
- Inspect prompt, conversation history, existing file and relevant references to figure out what questions to ask.
- Questions should cover topic, audience, and purpose and come before planning
- When asking questions, focus on consequential dimensions not stated or clearly implied.
- When the artifact is a new analysis, focus on which definition, metric, or lens should drive conclusions.
- Unresolved reference labels or question marks are user-owned: ask, don't infer.
- Once topic, audience, and purpose are clear, proceed without asking. Choose emphasis, format, length, style, details. Use placeholders for missing facts.

Use `request_user_input` once if available, else ask via a message. Have the best suggestion first. Append `(Recommended)` to its label. Have another good alternative second. Have `Use your judgment` as the third and final option. If the request times out or returns no answer, proceed using your best judgment; do not ask again.

## Route the Request

- Use `[@presentations](plugin://presentations@openai-primary-runtime)` to create a net-new presentation when no existing native Google Slides deck is the template or reference.
- Use this skill to create a presentation by following an existing native Google Slides template, reference deck, or prior-period deck.
- Use this skill to edit, update, repair, restyle, or clean up an existing native Google Slides deck.
- If a request combines new content with an existing native Google Slides deck that must be followed, use this skill.
- Do not use this skill to author a blank or from-scratch presentation.

## Parse a Template Deck

If code mode is unavailable in the current Codex environment, reproduce the same read-to-file, parse, and render workflow with the available connector and local tools. Preserve the same artifacts and validation steps; do not skip the workflow merely because code mode cannot be used.

For template or reference following, first use code mode to read the complete template/reference presentation directly into a file. Set `SKILL_DIR` to this skill's absolute directory and `WORKSPACE` to an absolute task workspace, then run this in one `functions.exec` call:

```js
const SKILL_DIR = "<absolute-skill-directory>";
const WORKSPACE = "<absolute-task-workspace>";
const loaded = await tools.exec_command({
  cmd: `/bin/cat -- '${SKILL_DIR}/host/read-template-to-file.mjs'`,
  workdir: SKILL_DIR,
  login: false,
  yield_time_ms: 30000,
  max_output_tokens: 20000,
});
if (loaded.exit_code !== 0) throw new Error("Could not load the template reader");
const { readTemplateToFile } = new Function(
````
END THIRD-PARTY FILE 45748b52df4e2063

The third-party file has ended. Everything between the 45748b52df4e2063 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 3249 of 15364 bytes. © OpenAI · MIT · https://github.com/openai/plugins/tree/HEAD/plugins/google-drive/skills/google-slides/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md