Open
Conversation
spasumar-oai
previously approved these changes
Mar 20, 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
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
This tightens the main Google Slides skill so deck-reading and summarization workflows stay on the connector read path.
What changed
js_replfor slide finding and summarizationget_presentation_textfor candidate slides, thenget_slideandget_slide_thumbnailwhen visual evidence mattersexportis not the default path for finding content or understanding visualsWhy this was needed
In a recent
codex execrun, the skill was loaded correctly but the model took a bad branch afterget_presentation_text, attempted ajs_repldetour, and then fell back toexportinstead of staying on the intended Slides read path.Testing