gamma-automation
by ComposioHQgamma-automation is a Claude skill for automating Gamma tasks through Composio Rube MCP. Use it with live RUBE_SEARCH_TOOLS discovery, an active Gamma connection, and approval-aware workflows.
This skill scores 66/100, which means it is acceptable for directory listing but should be presented as a lightweight connector-oriented skill rather than a complete Gamma automation playbook. Directory users can tell what it is for and what external MCP connection it needs, but they should expect to rely on Rube tool discovery for most task-specific details.
- Valid skill metadata clearly identifies the trigger domain: automating Gamma tasks through Composio's Gamma toolkit via Rube MCP.
- Prerequisites and setup steps are explicit, including requiring RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, and an ACTIVE Gamma connection before workflows run.
- The skill instructs agents to search tools first for current schemas, which reduces stale-tool risk and gives agents a repeatable execution pattern.
- No support files, scripts, examples, or install command are present beyond the single SKILL.md, so adoption depends on users already being comfortable configuring Rube MCP.
- Workflow guidance is mostly a generic discovery/check/execute pattern; it does not document concrete Gamma task examples or stable tool schemas.
Overview of gamma-automation skill
What gamma-automation does
gamma-automation is a Claude skill for running Gamma presentation and document tasks through Composio’s Rube MCP server. Instead of guessing a Gamma API shape, the skill tells the agent to discover the current Gamma tools first with RUBE_SEARCH_TOOLS, confirm the user’s Gamma connection with RUBE_MANAGE_CONNECTIONS, and then execute the appropriate Rube tool using the latest schema.
Best fit for Workflow Automation users
This gamma-automation skill is best for users who already work in an MCP-enabled assistant and want repeatable Gamma operations inside broader Workflow Automation flows. It is most useful when Gamma is one step in a larger process, such as turning research notes into a deck, updating a presentation after a data change, or coordinating content generation with a connected Gamma workspace.
Main adoption requirement
The important blocker is not the skill file itself; it is the MCP connection. You need Rube MCP available at https://rube.app/mcp, RUBE_SEARCH_TOOLS responding in your client, and an active Gamma connection created through RUBE_MANAGE_CONNECTIONS with toolkit gamma. If your assistant cannot call MCP tools, gamma-automation will not deliver its intended value.
Why it is more than a generic prompt
A normal prompt can ask an assistant to “make a Gamma deck,” but it may hallucinate tool names or use stale schemas. gamma-automation’s differentiator is its tool-discovery-first pattern: search the live Rube tool catalog, inspect current input fields, check connection state, and only then execute. That makes it better suited to automation than one-off conversational drafting.
How to Use gamma-automation skill
gamma-automation install and setup path
Install the skill from the repository path if your skill manager supports GitHub skill installs:
npx skills add ComposioHQ/awesome-claude-skills --skill gamma-automation
Then configure Rube MCP in your client by adding https://rube.app/mcp as an MCP server. Confirm RUBE_SEARCH_TOOLS is available. Next call RUBE_MANAGE_CONNECTIONS with toolkit gamma; if the returned status is not ACTIVE, complete the authorization link and re-check before asking the skill to run Gamma actions.
Inputs the skill needs from you
For good gamma-automation usage, provide the real business goal, the target Gamma object or desired new output, source material, formatting expectations, and any constraints. A weak request is: “Update my Gamma.” A stronger request is: “Use Gamma via Rube to create a 10-slide investor update from these bullet notes, keep the tone concise, include sections for traction, roadmap, risks, and funding ask, and ask me before publishing or sharing.”
The stronger version improves results because the agent can search for a specific Gamma use case, map your intent to the right discovered tool, and avoid unsafe assumptions about publishing, overwriting, or sharing.
Recommended execution workflow
Start every run by asking the assistant to follow the skill’s discovery pattern: search tools, check the Gamma connection, summarize the available execution plan, then proceed. A practical prompt is:
“Use the gamma-automation skill. First run RUBE_SEARCH_TOOLS for my specific Gamma task and verify my gamma connection. Show me the tool you plan to use, required fields, and any risky action before execution. My task is: [describe task].”
This workflow is slower than direct prompting, but it reduces schema errors and makes the run auditable.
Repository files to read first
The repository is intentionally minimal. Read composio-skills/gamma-automation/SKILL.md first; it contains the prerequisites, setup flow, tool discovery pattern, and connection-check requirement. There are no companion scripts/, rules/, resources/, references/, or README.md files in the skill folder, so treat SKILL.md as the source of truth and rely on live Rube tool discovery for operational details.
gamma-automation skill FAQ
Is gamma-automation beginner friendly?
It is beginner friendly only if your AI client already supports MCP tools. The Gamma-side authorization flow is straightforward, but the user must understand that the assistant is calling external tools, not just generating text. If you are new to MCP, first confirm that your client can expose RUBE_SEARCH_TOOLS and RUBE_MANAGE_CONNECTIONS.
When should I not use gamma-automation?
Do not use gamma-automation for purely offline slide writing, manual design advice, or situations where you cannot connect a Gamma account. It is also a poor fit if you need guaranteed behavior without checking live schemas, because the skill deliberately depends on current Rube tool discovery rather than hardcoded tool calls.
How does it compare with asking Claude directly?
Claude alone can outline, rewrite, and structure presentation content. The gamma-automation skill becomes useful when the output needs to interact with Gamma through Rube MCP. Use ordinary prompts for ideation and copy refinement; use gamma-automation when the workflow requires authenticated Gamma operations, tool selection, or repeatable execution.
Does it work for broader Workflow Automation?
Yes, gamma-automation for Workflow Automation makes sense when Gamma is one connected service in a chain. For example, an agent can gather source content, transform it into a deck plan, discover available Gamma tools, and create or update Gamma assets. The skill does not define a full multi-app pipeline by itself, so your prompt should specify upstream inputs and downstream approvals.
How to Improve gamma-automation skill
Improve gamma-automation prompts with complete context
The fastest way to improve gamma-automation output is to provide context that maps cleanly to a Gamma operation: audience, deliverable type, source content, desired structure, brand or tone constraints, and permissions. Include whether the agent may create new assets, update existing ones, or must stop for approval before destructive or public actions.
Reduce common failure modes
The main failure modes are skipped tool discovery, inactive Gamma connection, vague task scope, and accidental assumptions about sharing or publishing. Prevent these by explicitly requiring RUBE_SEARCH_TOOLS first, confirming gamma connection status, asking for a short execution plan, and labeling risky actions as approval-required.
Iterate after the first output
After the first run, inspect both the Gamma result and the tool call summary. Then ask for targeted revisions: “shorten slide titles,” “make the executive summary more quantitative,” “split roadmap into two slides,” or “do not change the published version yet.” Specific revision instructions are more reliable than asking the agent to “make it better.”
Extend the skill responsibly
If you customize gamma-automation, add examples for your team’s most common Gamma workflows, such as deck creation, content refreshes, or template-driven updates. Keep the discovery-first rule intact. Hardcoding old tool schemas may look faster, but it removes the main safety benefit of the skill: adapting to the current Rube Gamma toolkit before execution.