google-slides-template-migration

Migrate Google Slides content onto a branded template while preserving structure.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/jetteim/platform-workstation-bootstrap --skill google-slides-template-migration-jetteim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: google-slides-template-migration
Source: https://github.com/jetteim/platform-workstation-bootstrap/tree/main/agents/skills/plugins/google-drive/google-slides-template-migration
Command: npx skills add https://github.com/jetteim/platform-workstation-bootstrap --skill google-slides-template-migration-jetteim

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Migrate a Google Slides deck onto a target template while preserving source content and rebuilding slides in a branded structure rather than making incremental edits.

Core Features & Use Cases

  • Template-driven migration: Duplicate from the template and port content to align with the template’s layout language.
  • Slide mapping & archetypes: Map source slides to template archetypes to maintain narrative flow and density.
  • Verification by thumbnails: Ensure migrated slides visually align with the template, using thumbnails for quick validation.
  • Migration rules guidance: Follow the migration rules and playbook to ensure consistency across decks.

Quick Start

Open both decks, map each source slide to a template archetype, duplicate from the template, port content, and verify with thumbnails.

Frequently Asked Questions about google-slides-template-migration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate a Google Slides presentation onto a branded template?

Yes, you can port content from a local PPTX file using the import_presentation function. The migration requires access to Google Slides APIs like get_presentation, get_slide, and batch_update to duplicate template layouts and transfer content.

What is the best way to preserve content structure when changing slide templates?

The best way to preserve content structure during template migration is mapping source slides to template archetypes. This maintains narrative flow and density by matching the source messaging to consistent layout patterns in the target deck.

How do I verify visual alignment after porting slides to a new template?

You verify visual alignment after porting slides by using the get_slide_thumbnail function. Generating thumbnails of the migrated slides allows you to quickly validate that the content visually aligns with the target template's layout language.

Does template migration work for large presentation decks with complex layouts?

Template migration works for complex decks by following migration rules and playbook guidance to ensure consistency. It maps each source slide to a template archetype, maintaining narrative flow and managing density across the presentation.

Why does my migrated slide not match the template layout correctly?

Migrated slides may not match the template layout if the source slide was not mapped to the correct template archetype. Verifying alignment with slide thumbnails and following the migration playbook ensures the layout language and content density remain consistent.