Simplify Google Slides skill docs

Author: Aismit

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

@@ -1,6 +1,6 @@
 ---
 name: google-slides-import-presentation
-description: Import a local `.ppt`, `.pptx`, or `.odp` file into Google Slides, verify the resulting native deck, and hand it off to the right follow-on workflow. Use when the user wants to convert a presentation file into a native Google Slides deck before summarizing, editing, cleaning up, or migrating it.
+description: Import a local `.ppt`, `.pptx`, or `.odp` file into Google Slides, verify the resulting native deck, and hand it off to the right follow-on workflow. Use when the user wants to convert a presentation file into a native Google Slides deck before follow-on work.
 ---
 
 # Google Slides Import Presentation
@@ -32,7 +32,7 @@ If `import_presentation` is unavailable, stop and say the file cannot be convert
 - Capture the resulting presentation ID or URL, slide count, and major slide titles.
 - Treat the imported deck as the new source of truth for follow-on work.
 
-4. Verify the conversion.
+4. Verify enough to hand it off safely.
 - Compare the imported slide count to the source file when that information is available.
 - Use thumbnails for spot checks when layout fidelity matters or the user plans visual cleanup next.
 
@@ -41,15 +41,15 @@ If `import_presentation` is unavailable, stop and say the file cannot be convert
 - Use [google-slides-visual-iteration](../google-slides-visual-iteration/SKILL.md) for post-import layout cleanup.
 - Use [google-slides-template-migration](../google-slides-template-migration/SKILL.md) when the imported deck should move onto a branded template.
 
-## Import Rules
+## Rules
 
 - Treat import as conversion into a new native Google Slides deck, not in-place editing of the original file.
 - Preserve source slide order and content by default.
 - Do not promise perfect fidelity for animations, transitions, SmartArt, or other Office-specific features.
 - If import introduces layout drift, fix it in the native Google Slides deck rather than editing the source file.
 - When the user says "edit this PPTX," import first and then operate on the resulting Google Slides deck.
 
-## Output Conventions
+## Output
 
 - Return the resulting deck title and link or ID when the runtime exposes it.
 - Call out any obvious import drift or unsupported formatting that needs follow-up.

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

@@ -1,19 +1,13 @@
 ---
 name: google-slides
-description: Inspect, create, import, summarize, and update Google Slides presentations through connected Google Slides data. Use when the user wants to find a deck, read slide structure, summarize a presentation, create a new presentation, import a `.ppt`, `.pptx`, or `.odp`, update slide text or layout, or route a Slides task to a more specific workflow such as visual iteration, template surgery, or template migration.
+description: Inspect, create, import, summarize, and update Google Slides presentations through connected Google Slides data. Use when the user wants to find a deck, read slide structure, summarize a presentation, create a new presentation, import a `.ppt`, `.pptx`, or `.odp`, update slide text or layout, or route a Slides task to a more specific workflow.
 ---
 
 # Google Slides
 
 ## Overview
 
-Use this skill as the default entrypoint for Google Slides work. Read the deck first, preserve content by default, and route to a narrower sibling skill only when the task is specifically import, visual cleanup, structural repair, or template migration.
-
-## Preferred Deliverables
-
-- Deck briefs that summarize slide order, titles, structure, and obvious issues.
-- Edit plans that name the target presentation, slide numbers or object IDs, and the intended changes.
-- Native Google Slides presentations that are ready for follow-on cleanup or content edits.
+Use this skill as the default entrypoint for Google Slides work. Stay here for deck search, summaries, light content edits, and new presentation creation. Route to a narrower sibling skill only when the task is specifically import, visual cleanup, structural repair, or template migration.
 
 ## Required Tooling
 
@@ -26,7 +20,7 @@ Confirm the runtime exposes the relevant Google Slides actions before editing:
 - `import_presentation` when starting from a local `.ppt`, `.pptx`, or `.odp`
 - `get_slide_thumbnail` when visual verification matters
 
-## Default Workflow
+## Workflow
 
 1. Identify the target presentation.
 - If the user names a deck but does not provide a URL, search for it first.
@@ -36,22 +30,17 @@ Confirm the runtime exposes the relevant Google Slides actions before editing:
 - Use `get_presentation` or `get_presentation_text` to capture slide order, titles, and overall structure.
 - Use `get_slide` before any slide-level write so object IDs and layout context come from the live deck.
 
-3. Choose the right depth of work.
-- For deck summaries, content review, or light text edits, stay in this skill.
+3. Route only when the job is narrower than general Slides work.
 - Use [google-slides-import-presentation](../google-slides-import-presentation/SKILL.md) when the source is a local presentation file.
 - Use [google-slides-visual-iteration](../google-slides-visual-iteration/SKILL.md) for spacing, overlap, alignment, and visual polish.
 - Use [google-slides-template-surgery](../google-slides-template-surgery/SKILL.md) when the repeated layout structure is broken.
 - Use [google-slides-template-migration](../google-slides-template-migration/SKILL.md) when content should move onto a company or team template deck.
 
-4. Keep edits grounded.
+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.
 
-5. Report the outcome clearly.
-- Say which presentation and slides were read or changed.
-- Call out any remaining issues that need a narrower workflow or human design judgment.
-
 ## Write Safety
 
 - Preserve slide order, titles, body text, charts, notes, and supporting evidence unless the user asks for a change.
@@ -60,12 +49,12 @@ Confirm the runtime exposes the relevant Google Slides actions before editing:
 - 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.
 
-## Output Conventions
+## Output
 
 - Reference slide numbers and titles when summarizing or planning edits.
-- Distinguish clearly between a proposed edit plan and changes that were actually applied.
-- When the request is exploratory, lead with the deck's purpose, major slide groups, and obvious weak spots.
-- When the request is write-oriented, state the exact slides or objects that will change before editing.
+- Distinguish clearly between a proposed plan and changes that were actually applied.
+- Say which presentation and slides were read or changed.
+- Call out any remaining issues that need a narrower workflow or human design judgment.
 
 ## Example Requests