Add general and import Google Slides skills#27
Merged
Conversation
caseychow-oai
previously approved these changes
Mar 16, 2026
|
|
||
| - Preserve slide order, titles, body text, charts, notes, and supporting evidence unless the user asks for a change. | ||
| - Use live object IDs from the current deck state. Never guess IDs or request shapes. | ||
| - Treat deck-wide rewrites, slide deletions, and broad template changes as explicit actions that should be clearly scoped. |
Collaborator
There was a problem hiding this comment.
I would try to make this a little more specific, since it's not clear to me what the model should do as a result of this.
| - Preserve slide order, titles, body text, charts, notes, and supporting evidence unless the user asks for a change. | ||
| - Use live object IDs from the current deck state. Never guess IDs or request shapes. | ||
| - Treat deck-wide rewrites, slide deletions, and broad template changes as explicit actions that should be clearly scoped. | ||
| - If the user asks to edit a `.pptx`, convert it into native Google Slides first instead of promising in-place Office edits. |
Collaborator
There was a problem hiding this comment.
Con You should also make sure that this is clearly stated to the user.
| - Use live object IDs from the current deck state. Never guess IDs or request shapes. | ||
| - Treat deck-wide rewrites, slide deletions, and broad template changes as explicit actions that should be clearly scoped. | ||
| - If the user asks to edit a `.pptx`, convert it into native Google Slides first instead of promising in-place Office edits. | ||
| - Do not promise pixel-perfect fidelity when importing Office formats into Google Slides. |
Collaborator
There was a problem hiding this comment.
Is this something that should be in the slide importer?
| 4. Keep writes grounded. | ||
| - Restate the target slide numbers, titles, or object IDs before making changes. | ||
| - Prefer small `batch_update` requests over large speculative batches. | ||
| - Use thumbnails for verification whenever the task is visual, not just textual. |
Collaborator
There was a problem hiding this comment.
The task being visual might be something that can be teed up a little.
Collaborator
Author
There was a problem hiding this comment.
yeah tried being more specific here
spasumar-oai
approved these changes
Mar 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds two general-purpose Google Slides skills on top of the existing Google Slides plugin:
google-slidesgoogle-slides-import-presentationThis change also updates the Google Slides plugin manifest so the plugin description and default prompt reflect the broader workflow:
.ppt,.pptx, and.odpfiles into native Google SlidesWhy
We need a clearer convention for connector-backed skills in this repo:
Google Slides already had specialized skills for visual iteration, template surgery, and template migration, but it still lacked the default connector skill that common requests should route through.
That left two gaps:
google-slidesentrypoint for deck search, reading, summarization, and standard editsThe runtime already supports native presentation import, so
google-slides-import-presentationturns that capability into an explicit, reusable workflow instead of leaving it implicit.Notes
google-slidesis the default entrypoint and routes users to the narrower Slides skills only when the task is specifically import, visual cleanup, template surgery, or template migration.google-slides-import-presentationassumes the source file becomes a new native Google Slides deck, then hands off to the general or specialized Slides workflows as needed.Validation
google-slideswithquick_validate.pygoogle-slides-import-presentationwithquick_validate.pygit diff --checkjq