What are the prerequisites for templated automation?

Rube MCP must be connected with RUBE_SEARCH_TOOLS available, and there must be an ACTIVE templated connection via RUBE_MANAGE_CONNECTIONS. Always call RUBE_SEARCH_TOOLS first to fetch current schemas.

How do I execute a templated task?

Discover tools with RUBE_SEARCH_TOOLS, verify the connection with RUBE_MANAGE_CONNECTIONS, then execute the tool using RUBE_MULTI_EXECUTE_TOOL, providing memory and the correct schema-aligned arguments along with a session_id.

What are common pitfalls to avoid?

Do not hardcode tool slugs or arguments; always verify ACTIVE connections; ensure exact field names/types from the search results; include memory in multi-execute calls; manage session IDs properly and handle pagination when listing tools.

templated-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Templated Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/templated

Prerequisites

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

Step 2: Check Connection

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

Overview

Templated Automation via Rube MCP enables automating templated operations using Composio's Templated toolkit. It emphasizes discovering current tool schemas via RUBE_SEARCH_TOOLS and requires an ACTIVE templated connection via RUBE_MANAGE_CONNECTIONS. Always fetch schemas first to avoid hardcoding and keep workflows up to date.

How This Skill Works

First discover available tools with RUBE_SEARCH_TOOLS, then verify an ACTIVE templated connection with RUBE_MANAGE_CONNECTIONS. Finally execute the selected tool via RUBE_MULTI_EXECUTE_TOOL, passing memory and the schema-aligned arguments, using a shared session_id.

When to Use It

When templated tool schemas change and you can't hardcode slugs
When you need to validate an ACTIVE connection before running workflows
When orchestrating a sequence of templated tools in a single session
When performing bulk templated operations via RUBE_REMOTE_WORKBENCH
When you must reuse session IDs within a workflow to maintain context

Quick Start

Step 1: RUBE_SEARCH_TOOLS to fetch available templated tool schemas
Step 2: RUBE_MANAGE_CONNECTIONS with toolkit 'templated' and ensure ACTIVE
Step 3: RUBE_MULTI_EXECUTE_TOOL with a discovered tool slug and schema-aligned arguments; include memory and session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas and avoid hardcoding
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from the search results
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow and generate new ones for new workflows

Example Use Cases

Automate a templated data-entry task by discovering the tool slug via RUBE_SEARCH_TOOLS and executing it with RUBE_MULTI_EXECUTE_TOOL
Establish an ACTIVE templated connection with RUBE_MANAGE_CONNECTIONS, then run a templated mapping tool in sequence
Orchestrate multiple templated tools in a single session by reusing session_id across steps
Perform bulk templated operations using RUBE_REMOTE_WORKBENCH and run_composio_tool()
Fetch the full tool schema set with RUBE_GET_TOOL_SCHEMAS to validate inputs before execution

Frequently Asked Questions

Add this skill to your agents