Gamma Automation

What This Skill Does

• This skill automates Gamma operations using the Composio Gamma toolkit through Rube MCP.
• It is designed for users who need to streamline and automate tasks within the Gamma platform.
• The skill simplifies interaction with Gamma by providing tools for connection management, tool discovery, and execution.

When to Use

• Automate Gamma workflows.
• Discover available Gamma tools.
• Check Gamma connection status.
• Execute Gamma tools with schema-compliant arguments.
• Integrate Gamma operations into existing workflows.
• Dynamically adapt to Gamma tool schema changes.

Key Features

• Connects to Gamma via Rube MCP.
• Discovers available Gamma tools and their schemas.
• Manages Gamma connection status.
• Executes Gamma tools with provided arguments.
• Provides a structured workflow pattern for Gamma automation.
• Offers guidance on avoiding common pitfalls.

Manual Installation

• Manual installation.
• View Full Skill Content.
• The complete markdown content that gets installed.
• 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

Powered by Composio. 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

Powered by Composio