Clarify thumbnail image handling in Slides skills

plugins/google-slides/skills/google-slides-visual-iteration/SKILL.md

@@ -46,10 +46,10 @@ If a dedicated visual-iteration tool exists in the runtime, use it. Otherwise, e
 - Fetch the thumbnail for the current slide only. Do not prefetch thumbnails for the rest of the deck before starting the current slide's edit loop.
 - Use `LARGE` when spacing, overlap, cropping, or dense layouts are the concern.
 - Treat the thumbnail as the source of truth for visual quality. Raw JSON alone is not enough.
-- When the tool returns a thumbnail artifact, image content, base64 image data, or an image-bearing URL/data wrapper, treat that as analyzable visual input for this workflow and inspect it directly.
+- When the tool returns inline image content in `content`, including image bytes, base64 image data, or an image-bearing data wrapper, treat that as analyzable visual input for this workflow and inspect it directly.
 - If the thumbnail payload includes image bytes, a data URL, or base64 image content, ingest it directly as if the user had uploaded a screenshot of the slide.
 - If `get_slide_thumbnail` succeeds, treat that as the visual verification path for this workflow even if the transcript view looks metadata-shaped. Do not abandon the thumbnail loop just because the runtime shows a thumbnail artifact, URL, or metadata wrapper instead of inline pixels in the message body.
-- Do not route thumbnail inspection through Atlas or another separate visual-analysis path when the connector already returned analyzable image content for the current slide.
+- The response may also include `contentUrl` metadata, but if inline image data is present, inspect that directly instead of downloading the URL or switching to another image-analysis path.
 - Do not switch to deck export, PDF rendering, or other fallback rendering paths when the thumbnail tool already succeeded. Only use a fallback path if the thumbnail action itself failed or is unavailable.
 
 4. Diagnose concrete visual problems.

plugins/google-slides/skills/google-slides/SKILL.md

@@ -40,7 +40,7 @@ Confirm the runtime exposes the relevant Google Slides actions before editing:
 - Use `get_slide` before any slide-level write so object IDs and layout context come from the live deck.
 - For slide summaries or inspection, do not rely on text extraction alone when a slide contains charts, graphs, screenshots, diagrams, or image-heavy content.
 - Use `get_slide_thumbnail` alongside text/structure reads when visual evidence matters so the summary reflects both what the slide says and what the slide shows.
-- If the thumbnail response includes image content, base64 image data, or an image-bearing URL/data wrapper, ingest that directly as slide image input rather than routing through Atlas or another separate visual-analysis path.
+- If the thumbnail response includes inline image content, base64 image data, or an image-bearing data wrapper, ingest that directly as slide image input. The response may also include `contentUrl` metadata, but if inline image data is present, inspect that directly instead of downloading the URL or relying only on metadata.
 - Treat the slide page size as a hard boundary for every shape, text box, image, and color band you create.
 
 3. Apply default creation polish when making a new presentation.