googleslides-automation
by ComposioHQgoogleslides-automation helps agents create and edit Google Slides via Rube MCP: create decks, generate slides from Markdown, copy templates, batch update content, and fetch thumbnails after checking current tool schemas.
This skill scores 70/100, which means it is acceptable for directory listing but should be presented as a Rube-dependent automation guide rather than a turnkey package. Directory users get enough information to understand when to use it and how an agent should start, but the lack of support files, install command, and fuller examples leaves some execution details to live MCP schemas and agent judgment.
- Clear trigger and scope: the frontmatter and title identify Google Slides automation via Rube MCP for creating presentations, adding slides from Markdown, batch updates, templates, and thumbnails.
- Operational prerequisites are explicit: it requires Rube MCP, `RUBE_SEARCH_TOOLS`, an active `googleslides` connection via `RUBE_MANAGE_CONNECTIONS`, and current schema lookup before execution.
- Includes concrete workflow entry points and tool names such as `GOOGLESLIDES_PRESENTATIONS_CREATE` and `GOOGLESLIDES_CREATE_SLIDES_MARKDOWN`, which gives agents more direction than a generic prompt.
- No support files, scripts, examples, or reference assets are included; adoption depends entirely on the single SKILL.md and live Rube tool schemas.
- No install command is provided in the skill file, and the setup assumes users already know how to add and operate the Rube MCP endpoint in their client.
Overview of googleslides-automation skill
What googleslides-automation is for
googleslides-automation is a Claude skill for creating and editing Google Slides through Rube MCP by Composio. It is built for users who want an agent to perform concrete slide-deck operations: create a presentation, generate slides from Markdown, copy from an existing template, batch update content, and retrieve thumbnails for review.
The main value is not “write me a deck” in the abstract. The skill gives the agent a tool-first workflow for operating on real Google Slides files, including the requirement to search current Rube tool schemas before calling Google Slides actions.
Best-fit users and slide deck workflows
This googleslides-automation skill is a good fit if you regularly turn structured notes, reports, launch plans, sales outlines, or meeting material into Google Slides. It is especially useful for Slide Decks where the content source is already semi-structured: Markdown headings, bullet lists, speaker notes, template IDs, brand instructions, or an existing presentation to update.
It is less useful if you only need copywriting advice, visual design critique, or a one-off outline with no need to touch Google Slides directly.
Key differentiators before install
The important differentiator is MCP-backed execution. Instead of asking a model to describe what slides should exist, the skill guides the agent to connect to the googleslides toolkit, inspect available tools with RUBE_SEARCH_TOOLS, and use live tool schemas such as presentation creation, Markdown-to-slides generation, batch updates, template copying, and thumbnail retrieval.
That makes adoption dependent on your MCP setup. If Rube MCP is not available in your client, the skill cannot perform the core Google Slides actions.
How to Use googleslides-automation skill
googleslides-automation install and setup path
Install the skill from the Composio skill collection, then configure Rube MCP in your AI client:
npx skills add ComposioHQ/awesome-claude-skills --skill googleslides-automation
The repository path is:
composio-skills/googleslides-automation/SKILL.md
The skill expects Rube MCP to be connected at:
https://rube.app/mcp
Before asking for deck work, verify that RUBE_SEARCH_TOOLS is available. Then use RUBE_MANAGE_CONNECTIONS with toolkit googleslides. If the connection is not ACTIVE, follow the returned authorization link and confirm the connection before running slide operations.
Inputs the skill needs for reliable output
For strong googleslides-automation usage, give the agent operational inputs, not just a vague goal. Useful inputs include:
- Deck title and intended audience
- Desired slide count or section structure
- Markdown content to transform into slides
- Existing
presentationIdif updating a deck - Template presentation ID if copying from a branded deck
- Brand constraints such as tone, colors, layout preferences, or forbidden changes
- Whether the agent should create, update, copy, or only inspect thumbnails
A weak prompt is: “Make a sales deck.”
A stronger prompt is: “Use googleslides-automation to create a 10-slide Google Slides deck from the Markdown below for a VP Sales audience. First confirm the active googleslides connection, search current tool schemas, create a presentation titled Q3 Pipeline Review, generate slides from the Markdown, then retrieve thumbnails so I can review layout issues.”
Practical workflow for first run
Start by reading SKILL.md; there are no extra scripts, references, or README files in this skill directory, so the skill file is the source of truth. In use, a good workflow is:
- Ask the agent to confirm Rube MCP availability.
- Ask it to run
RUBE_SEARCH_TOOLSbefore selecting Google Slides tools. - Confirm or establish an active
googleslidesconnection. - Provide the deck content or target presentation ID.
- Let the agent perform one operation class at a time: create, generate from Markdown, batch update, copy template, or fetch thumbnails.
- Review thumbnails or slide IDs before asking for broader edits.
This reduces the risk of schema mismatch, accidental edits to the wrong presentation, or over-broad batch updates.
Prompt pattern for better slide creation
Use explicit task framing:
Use googleslides-automation for Slide Decks.
Goal: create a Google Slides presentation for [audience].
Action: [create new deck / update existing deck / copy from template].
Inputs: [Markdown, template ID, presentation ID, title].
Constraints: [slide count, tone, branding, sections to preserve].
Verification: search current Rube tool schemas first, confirm googleslides connection is ACTIVE, then return the presentation link and thumbnail review notes.
This helps the agent choose the right Google Slides tool instead of relying on generic slide-generation behavior.
googleslides-automation skill FAQ
Is googleslides-automation beginner-friendly?
Yes, if your AI client already supports MCP servers. The skill’s workflow is straightforward, but beginners should understand that it depends on Rube MCP and Google authorization. If you have never configured MCP tools, setup may take longer than the slide-generation task itself.
How is it different from a normal slide prompt?
A normal prompt can draft an outline or suggest slide text. The googleslides-automation skill is designed to operate on actual Google Slides through Composio’s Rube MCP tools. That means it can create files, update presentations, copy from templates, and fetch thumbnails when the connection is active.
When should I not use this skill?
Do not use it when you cannot authorize Google Slides access, when your organization blocks external MCP connections, or when you need precise graphic design beyond what the available Google Slides tool schema supports. Also avoid it for highly sensitive decks unless your security review approves the MCP and Google account workflow.
What should I check before installing?
Check whether your client can add https://rube.app/mcp, whether RUBE_SEARCH_TOOLS is available, and whether you are allowed to connect the googleslides toolkit. Also inspect SKILL.md directly, because this skill currently has a single-file implementation without helper scripts or additional reference assets.
How to Improve googleslides-automation skill
Improve googleslides-automation results with better inputs
The biggest quality gain comes from structured source content. Markdown with clear #, ##, and bullet hierarchy usually converts better than pasted prose. Include slide intent where needed, such as “problem,” “market evidence,” “roadmap,” or “decision ask.” If using a template, provide the template ID and explain what should be preserved: layouts, theme, title slide, section dividers, or footer conventions.
Common failure modes to prevent
The most common blocker is skipping the required tool search. Rube tool schemas can change, so the agent should always call RUBE_SEARCH_TOOLS before using Google Slides actions. Another common issue is ambiguous deck targeting: if you provide multiple links or IDs, clearly identify which presentation should be edited and which should only be used as a template.
For batch updates, ask the agent to summarize intended changes before execution when the deck is important.
Iteration after the first generated deck
After creation, do not ask for “make it better” without specifics. Use thumbnail review or slide numbers:
- “Shorten slides 3 and 4 by 30%.”
- “Add an executive-summary slide after slide 1.”
- “Keep the template, but replace product screenshots only.”
- “Fetch thumbnails again and flag slides with overcrowded text.”
This keeps googleslides-automation focused on verifiable Google Slides operations.
Repository-level improvements worth adding
For future maintainers, the skill would be stronger with a short README.md, example prompts, sample Markdown input, and a troubleshooting section for inactive googleslides connections. A small reference file showing safe batch-update patterns would also reduce adoption risk for users editing existing Slide Decks rather than creating new presentations.