What is required to get started with gamma-automation?

Rube MCP connectivity, access to the Gamma toolkit, and the ability to verify RUBE_SEARCH_TOOLS responds before executing any tool.

Do I always need an ACTIVE Gamma connection before running a tool?

Yes. RUBE_MANAGE_CONNECTIONS must show ACTIVE to safely execute tools.

Should tool slugs or arguments be hardcoded?

No. Always fetch schemas with RUBE_SEARCH_TOOLS and use exact field names and types from the results.

gamma-automation

npx machina-cli add skill ComposioHQ/awesome-claude-skills/gamma-automation --openclaw

Files (1)

SKILL.md

2.8 KB

Gamma Automation via Rube MCP

Automate Gamma operations through Composio's Gamma toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/gamma

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Gamma connection via RUBE_MANAGE_CONNECTIONS with toolkit gamma
Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit gamma
If connection is not ACTIVE, follow the returned auth link to complete setup
Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Gamma operations", known_fields: ""}]
session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Gamma task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["gamma"]
session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL
tools: [{
  tool_slug: "TOOL_SLUG_FROM_SEARCH",
  arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
Schema compliance: Use exact field names and types from the search results
Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Gamma-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `gamma`
Execute	`RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs
Bulk ops	`RUBE_REMOTE_WORKBENCH` with `run_composio_tool()`
Full schema	`RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef`

Powered by Composio

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/gamma-automation/SKILL.mdView on GitHub

Overview

Automate Gamma operations through Composio's Gamma toolkit via Rube MCP. It ensures you always search for current tool schemas before execution, avoiding hardcoded slugs.

How This Skill Works

Workflows start by verifying RUBE_SEARCH_TOOLS, then establishing a Gamma connection with RUBE_MANAGE_CONNECTIONS using the gamma toolkit and ensuring the status is ACTIVE. Next, discover available tools and their input schemas with RUBE_SEARCH_TOOLS, and finally execute a selected tool with RUBE_MULTI_EXECUTE_TOOL using the memory field and a session_id.

When to Use It

When you need to automate a Gamma operation and want to use the latest tool schemas
When you're setting up a Gamma connection for the first time or re-authenticating
When you need to discover tools before a workflow and handle pagination in results
When you execute a discovered Gamma tool and must pass memory and a session_id
When performing bulk Gamma tasks using the remote bench workflow

Quick Start

Step 1: Add the MCP server https://rube.app/mcp and verify connectivity with RUBE_SEARCH_TOOLS
Step 2: Manage Gamma connection with RUBE_MANAGE_CONNECTIONS and complete authentication if prompted
Step 3: Discover tools and execute a chosen tool with RUBE_MULTI_EXECUTE_TOOL, including memory and session_id

Best Practices

Always call RUBE_SEARCH_TOOLS before executing tools
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools
Use exact field names and types from the search results
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow and handle pagination when listing tools

Example Use Cases

Discover Gamma tool options for a task by querying RUBE_SEARCH_TOOLS with a Gamma use case
Connect to Gamma via RUBE_MANAGE_CONNECTIONS and complete any required authentication
Execute a discovered tool using RUBE_MULTI_EXECUTE_TOOL with the correct slug and arguments
Fetch all tool schemas across paginated responses using RUBE_SEARCH_TOOLS
Perform multiple Gamma tasks in bulk with RUBE_REMOTE_WORKBENCH and run_composio_tool

Frequently Asked Questions

Add this skill to your agents