Create branded Google Slides presentations using Figma brand assets and Google Slides MCP. Use when asked to create a deck, presentation, pitch, or slides. Supports customer decks, sales presentations, internal updates, and product overviews. Pulls brand tokens (colors, typography, layouts) from Figma and creates slides in Google Slides. Requires figma and google-slides MCP servers.
From gtmnpx claudepluginhub inkeep/team-skills --plugin gtmThis skill uses the workspace's default tool permissions.
references/brand-guidelines.mdreferences/graphics-delegation.mdreferences/master-decks.mdreferences/mcp-tools.mdGuides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Configures VPN and dedicated connections like Direct Connect, ExpressRoute, Interconnect for secure on-premises to AWS, Azure, GCP, OCI hybrid networking.
Create on-brand Google Slides presentations by combining Figma brand assets with Google Slides MCP tools.
This skill requires two MCP servers (scoped to the gtm plugin — they only load when working in plugins/gtm):
If any are missing, instruct the user to run:
./secrets/setup.sh --skill gslides --account inkeep.1password.com
This registers figma and google-slides MCP servers, sets up gcloud ADC, and pulls Google OAuth credentials.
Visual asset creation requires the graphics skill (available in the same gtm plugin). When the graphics skill is available, this skill delegates visual asset creation to it via subagent. When unavailable, slides are text-only — note the gap and move on.
Before starting any work, create a task for each step using TaskCreate with addBlockedBy to enforce ordering. Derive descriptions and completion criteria from each step's own workflow text.
Mark each task in_progress when starting and completed when its step's exit criteria are met. On re-entry, check TaskList first and resume from the first non-completed task.
Identify:
~/reports/, documents, URLs, or inline instructionsBefore creating anything from scratch, find relevant existing work. Do this in order:
a) Check master deck templates
Load: references/master-decks.md
Match the presentation type to a master deck template. If there's a match, this is the default starting point — clone it, then customize.
b) Ask about prior versions
Ask the user if there are existing presentations on this topic, audience, or company. If they provide a Google Slides URL, use mcp__google-slides__get_presentation to read it.
c) Present options to the user
| What was found | Default action |
|---|---|
| Master deck matches the type | Clone the master deck, then customize for this request |
| Prior customized deck found for same company/topic | Offer to extend or duplicate the prior deck |
| Both master and prior deck found | Ask user: start from master (clean slate) or extend the prior version |
| Nothing relevant found | Create fresh (proceed to step 3) |
| User provided a specific URL in step 1 | Use that deck directly (clone or extend as appropriate) |
Wait for user confirmation before proceeding. If the user says "just create a new one," skip to step 3.
Cloning a deck: Use mcp__google-slides__get_presentation to read the source deck, then mcp__google-slides__create_presentation to create a new copy and replicate the slides. Never modify master decks directly.
Use the Figma MCP to extract brand tokens from the Inkeep design system.
Load: /brand and load any reference files relevant to your task following the skill's reference loading guidance for your content. This is important for ensuring you are fully grounded and can leverage brand assets, tokens, and guidance.
Load: references/brand-guidelines.md for the Figma file URL and slide-specific styling defaults.
Key assets to extract:
If the Figma MCP is unavailable, use the fallback tokens in references/brand-guidelines.md.
If extending or customizing a cloned deck that already has brand styling, skip this step — the styling carries over from the source.
Design the slide deck outline before creating anything.
If working from a cloned deck (master or prior version), read its existing slides first via mcp__google-slides__get_presentation. Then plan what to keep, modify, add, or remove.
Common slide types (for new decks or adding slides):
| Slide Type | Purpose | When to Use | Typical visual need |
|---|---|---|---|
| Title slide | Set context, company name, presentation title | Always first | Hero illustration or branded background (optional) |
| Problem/challenge | Frame the pain point | Customer/sales decks | Conceptual diagram or illustration |
| Solution overview | High-level value proposition | Customer/sales decks | System diagram, before/after, or flowchart |
| Feature deep-dive | Specific capability with visual | Product presentations | Product mockup or UI screenshot treatment |
| Social proof | Customer logos, quotes, metrics | Sales decks | Metric callout cards, quote cards, logo wall |
| Architecture/diagram | Technical overview | Technical audiences | Architecture diagram or data flow |
| Comparison/matrix | Feature comparison or competitive positioning | Evaluation stage | Visual comparison layout (optional) |
| CTA/next steps | Clear call to action | Always last | None (text-only) |
Present the slide outline to the user for review before creating or modifying slides.
After the user confirms the slide outline, evaluate which slides need visual assets and delegate creation to the graphics skill via subagent.
Load: references/graphics-delegation.md
a) Scan the outline for visual needs
Review each slide against the "Typical visual need" column in the table above. Build a list of graphics to create:
| Slide | What the graphic should communicate | Graphic type |
|---|---|---|
| (fill per slide) | (key message / purpose) | (diagram, illustration, mockup, data viz, etc.) |
If any slides need product mockups or UI screenshots (feature deep-dives), gather existing product screenshots, URLs, or spec paths now — the graphics subagent can't browse the product or ask the user. Pass these as content sources in the handoff.
b) Create a series brief
Before spawning any subagents, decide the locked visual constants for the deck. See references/graphics-delegation.md § Series brief. These decisions apply to every graphic in the deck:
For sales decks targeting a specific prospect, also capture the prospect's company name and domain for brand personalization.
c) Skip delegation when:
d) Delegate in parallel
For each graphic needed, spawn a subagent using the Agent tool. See references/graphics-delegation.md for the prompt template and handoff contract. Include the series brief and prospect context (if applicable) in every subagent prompt.
Spawn all graphics subagents in parallel (multiple Agent tool calls in one message). Each subagent loads the graphics skill and produces a Figma frame + exported PNG.
e) Collect results and place images
When subagents return, collect the exported image URLs. These will be placed during slide creation (step 6) using mcp__google-slides__add_image.
If any subagent fails, note the gap and proceed — the slide gets text-only content and you inform the user which visuals could not be created.
Load: references/mcp-tools.md for the full tool reference.
Place visual assets: For each slide that has a graphic from step 5, use mcp__google-slides__add_image with the exported image URL during slide creation. Full-slide graphics: x=0, y=0, width=720, height=405 (points). Inset graphics: position and size according to the slide layout.
Choose the approach based on the starting point:
Option A: Customize a cloned deck (recommended when a master or prior deck was found)
Best when working from an existing deck that already has structure and styling.
mcp__google-slides__get_presentationmcp__google-slides__add_slidemcp__google-slides__delete_slidemcp__google-slides__move_slideOption B: Slide-by-slide (for new decks)
Best when creating fresh decks from scratch.
mcp__google-slides__create_presentationmcp__google-slides__add_slidemcp__google-slides__add_text_boxmcp__google-slides__add_imagemcp__google-slides__update_text_styleAfter slides are created or modified, verify brand consistency:
For cloned decks, styling should already be correct — only verify and fix inconsistencies.
Use mcp__google-slides__batch_update for efficient bulk styling.
For each slide:
For cloned decks, focus on customizing existing content (company name, specific pain points, tailored metrics) rather than rewriting everything.
mcp__google-slides__get_presentationMust have:
Should have:
references/master-decks.md first