How do I start using beamer-automation?

Add the Rube MCP endpoint at https://rube.app/mcp, verify RUBE_SEARCH_TOOLS, connect Beamer via RUBE_MANAGE_CONNECTIONS, then discover tools and execute.

What if tool schemas change?

Always call RUBE_SEARCH_TOOLS first to fetch current tool slugs and argument schemas before executing.

Do I need to include memory and session IDs?

Yes. Include memory in RUBE_MULTI_EXECUTE_TOOL calls (even if empty) and reuse session IDs within a workflow; handle pagination as needed.

beamer-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Beamer Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/beamer

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Beamer connection via RUBE_MANAGE_CONNECTIONS with toolkit beamer
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 beamer
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: "Beamer 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 Beamer task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["beamer"]
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 Beamer-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `beamer`
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/beamer-automation/SKILL.mdView on GitHub

Overview

Automate Beamer operations through Composio's Beamer toolkit using the Rube MCP integration. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before execution and requires an ACTIVE Beamer connection to run workflows.

How This Skill Works

First, discover available Beamer tools and their input schemas using RUBE_SEARCH_TOOLS with a Beamer use_case. Next, verify the Beamer connection with RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE. Finally, execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL, supplying the required arguments and a memory object (even if empty) along with the session_id.

When to Use It

When you need to automate a Beamer task and want to rely on the latest tool schemas fetched by RUBE_SEARCH_TOOLS.
When setting up a new Beamer connection and you must confirm RUBE_MANAGE_CONNECTIONS shows ACTIVE before workflows.
When you want to discover the available Beamer tools for a specific operation before running anything.
When you want to reuse a session ID across steps to maintain context within a workflow.
When performing bulk operations or auditing tool schemas with RUBE_REMOTE_WORKBENCH or RUBE_GET_TOOL_SCHEMAS.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server and verify RUBE_SEARCH_TOOLS responds.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["beamer"] and complete any required auth until status is ACTIVE.
Step 3: Use RUBE_SEARCH_TOOLS to discover tools for your Beamer task, then run RUBE_MULTI_EXECUTE_TOOL with the chosen tool_slug, proper arguments, memory: {} and the session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.
Check that RUBE_MANAGE_CONNECTIONS reports ACTIVE before executing tools.
Use exact field names and types from the search results; avoid hardcoding slugs.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow and handle pagination tokens if provided.

Example Use Cases

Discover tools with use_case 'Beamer operations' and execute a specific tool slug retrieved from the search results.
Establish a Beamer connection via Rube MCP, then run a sequence of tools in a single session.
Perform bulk Beamer tasks using RUBE_REMOTE_WORKBENCH and run_composio_tool().
Retrieve full tool schemas with RUBE_GET_TOOL_SCHEMAS for auditing and schema validation.
Handle multi-page discovery results by following pagination tokens until all tools are fetched, then execute as needed.

Frequently Asked Questions

Add this skill to your agents