How do I ensure tool schemas are current?

Always call RUBE_SEARCH_TOOLS before executing; do not hardcode slugs or arguments.

Do I need API keys to use this skill?

No API keys are needed; just configure the MCP endpoint rube.app/mcp.

What if the connection is not ACTIVE?

Use RUBE_MANAGE_CONNECTIONS to authorize; confirm ACTIVE before running workflows.

How should I handle paginated results?

Check responses for pagination tokens and continue fetching until complete.

apitemplate-io-automation

Scanned

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

Files (1)

SKILL.md

3.0 KB

Apitemplate IO Automation via Rube MCP

Automate Apitemplate IO operations through Composio's Apitemplate IO toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/apitemplate_io

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["apitemplate_io"]
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 Apitemplate IO-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `apitemplate_io`
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/apitemplate-io-automation/SKILL.md

View on GitHub

Overview

Automates Apitemplate IO operations using Composio's toolkit through Rube MCP. Always start by running RUBE_SEARCH_TOOLS to fetch current tool schemas and confirm an ACTIVE connection via RUBE_MANAGE_CONNECTIONS before executing workflows.

How This Skill Works

The automation flow discovers tools with RUBE_SEARCH_TOOLS, then checks the Apitemplate IO connection with RUBE_MANAGE_CONNECTIONS, and finally executes the chosen tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and schema compliant arguments.

When to Use It

When you need to run an Apitemplate IO task with the latest tool schemas
When integrating Apitemplate IO operations into a larger automation flow via Rube MCP
When you must verify the connection status and authorize before running workflows
When executing multiple tools in sequence and maintaining memory and session state
When handling paginated tool results and continuing to fetch schemas and data

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration
Step 2: Run RUBE_SEARCH_TOOLS to fetch Apitemplate IO tool schemas
Step 3: Run RUBE_MANAGE_CONNECTIONS for the apitemplate_io toolkit and then execute a tool with RUBE_MULTI_EXECUTE_TOOL

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current slugs and schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from the search results rather than hardcoding
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs for related workflows and generate new ones for new runs

Example Use Cases

Create multiple Apitemplate IO templates from a data source using a discovered tool
Update several templates by iterating over tool arguments returned by the search
Fetch status or metadata of templates to monitor progress in a workflow
Run a sequence of Apitemplate IO tasks in a single session with memory management
Bulk operations via RUBE_REMOTE_WORKBENCH to run composer tools

Frequently Asked Questions

Add this skill to your agents