Get the FREE Ultimate OpenClaw Setup Guide →

autom-automation

npx machina-cli add skill ComposioHQ/awesome-claude-skills/autom-automation --openclaw
Files (1)
SKILL.md
2.8 KB

Autom Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/autom

Prerequisites

  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Autom connection via RUBE_MANAGE_CONNECTIONS with toolkit autom
  • 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.

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

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Autom 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 Autom task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["autom"]
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

OperationApproach
Find toolsRUBE_SEARCH_TOOLS with Autom-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit autom
ExecuteRUBE_MULTI_EXECUTE_TOOL with discovered tool slugs
Bulk opsRUBE_REMOTE_WORKBENCH with run_composio_tool()
Full schemaRUBE_GET_TOOL_SCHEMAS for tools with schemaRef

Powered by Composio

Source

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

Overview

This skill automates Autom operations through Composio's Autom toolkit via Rube MCP. It emphasizes always searching for current tool schemas with RUBE_SEARCH_TOOLS before running workflows and ensuring an active Autom connection.

How This Skill Works

Connect to Rube MCP and confirm the Autom toolkit is available. Always call RUBE_SEARCH_TOOLS to fetch current tool slugs and input schemas, then verify the connection with RUBE_MANAGE_CONNECTIONS. Finally, run the tool with RUBE_MULTI_EXECUTE_TOOL, providing the discovered arguments, a memory object, and a valid session_id.

When to Use It

  • Automate Autom operations and require up-to-date tool schemas
  • Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before running workflows
  • Discover available Autom tools for a use case using RUBE_SEARCH_TOOLS
  • Execute a tool with schema-compliant arguments and a memory payload
  • Bulk perform operations across multiple Autom tools using bulk/multi-tool workflows

Quick Start

  1. Step 1: RUBE_SEARCH_TOOLS with a use_case like Autom operations to discover tools
  2. Step 2: RUBE_MANAGE_CONNECTIONS for toolkit autom and ensure status is ACTIVE
  3. Step 3: RUBE_MULTI_EXECUTE_TOOL with a discovered tool_slug, proper arguments, memory, and a valid session_id

Best Practices

  • Always search first to get current tool schemas
  • Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing
  • Use exact field names and types from the search results
  • Always include memory in RUBE_MULTI_EXECUTE_TOOL calls
  • Reuse session IDs within a workflow and generate new ones for new workflows

Example Use Cases

  • Discover available Autom tools for a specific use case and execute a chosen tool with proper arguments
  • Set up the Rube MCP connection for the autom toolkit and run a workflow after confirming ACTIVE
  • Create and reuse a session_id across multiple steps of a single Autom workflow
  • Include a memory object in RUBE_MULTI_EXECUTE_TOOL calls to maintain state
  • Bulk-run several discovered Autom tools via RUBE_REMOTE_WORKBENCH for batch automation

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers