Clarify native Google Slides copy and import flows

[Aismit]

Summary

This updates the Google Slides plugin surface so the model is more likely to keep copy-and-edit workflows inside native Google Slides.

The main behavior change is to explicitly steer requests like "translate this deck and save it as a new Slides file" toward native deck-copy flows instead of export or re-upload detours.

What changed

• Updated the Google Slides plugin metadata to advertise native copy, import, and create flows more clearly.
• Updated the main Google Slides skill to call out create_from_template for transformed copies of an existing deck.
• Added guidance to keep live-deck workflows native when create_from_template, create_presentation, or import_presentation can satisfy the request.
• Tightened the agent default prompts so Slides import/copy behavior is described more accurately.
• Expanded the import skill prompt text to cover .ppt, .pptx, and .odp consistently.

Why this is needed

The connector implementation already supports the core primitives for this workflow:

• copy an existing Slides deck into a new native deck
• edit the copied deck
• import local presentation files into native Slides

What was missing was the capability-facing guidance. The previous metadata and skill text undersold native copy flows, which made it easier for the model to choose the wrong path and behave as if it needed to leave Google Slides to complete the task.

Files changed

• plugins/google-slides/.codex-plugin/plugin.json
• plugins/google-slides/skills/google-slides/SKILL.md
• plugins/google-slides/skills/google-slides/agents/openai.yaml
• plugins/google-slides/skills/google-slides-import-presentation/agents/openai.yaml

Testing

• git diff --check
• jq empty plugins/google-slides/.codex-plugin/plugin.json
• ruby -e "require 'yaml'; %w[plugins/google-slides/skills/google-slides/agents/openai.yaml plugins/google-slides/skills/google-slides-import-presentation/agents/openai.yaml].each { |f| YAML.load_file(f) }"

Simpler explanation

Before this change, the model had the right Google Slides tools available but the plugin surface did not clearly tell it to use the native copy-first path for sibling-deck workflows. After this change, the Slides surface describes that path directly, so the model is more likely to duplicate the deck in Slides first and then edit the native copy instead of falling into a file-export workaround.