Do I need API keys to use this skill?

No. Setup uses the MCP endpoint and toolkit connections; no API keys are required.

How do I handle changes in tool schemas?

Always search first with RUBE_SEARCH_TOOLS to fetch current schemas and avoid hardcoding slugs or field names.

What about session and memory requirements?

Reuse session IDs within a workflow for efficiency and include a memory object in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.

apilio-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Apilio Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/apilio

Prerequisites

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

Step 2: Check Connection

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

Overview

This skill automates Apilio operations using Composio's Apilio toolkit through Rube MCP. It relies on an active RUBE_SEARCH_TOOLS connection and a verified Apilio connection via RUBE_MANAGE_CONNECTIONS, and emphasizes discovering current tool schemas before execution.

How This Skill Works

Connect to Rube MCP and verify RUBE_SEARCH_TOOLS is available, then manage the Apilio toolkit connection with RUBE_MANAGE_CONNECTIONS. Discover tools using RUBE_SEARCH_TOOLS, choose a tool_slug, and execute it with RUBE_MULTI_EXECUTE_TOOL, supplying the required arguments and a memory object along with a session_id. Always ensure the connection is ACTIVE before running workflows.

When to Use It

Automating a specific Apilio action as part of a larger workflow after receiving an event or webhook.
You need to fetch the latest Apilio tool schemas before execution to avoid stale slugs or fields.
Integrating Apilio tasks into a multi-step automation pipeline that requires session management.
Troubleshooting or updating an automation where you must confirm the Apilio connection is ACTIVE prior to execution.
Running bulk or chained Apilio operations using RUBE_MULTI_EXECUTE_TOOL with a memory payload.

Quick Start

Step 1: Add the Rube MCP server (https://rube.app/mcp) and verify RUBE_SEARCH_TOOLS responds.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["apilio"] and confirm the connection status is ACTIVE.
Step 3: Use RUBE_SEARCH_TOOLS to discover tools, pick a TOOL_SLUG_FROM_SEARCH, and execute via RUBE_MULTI_EXECUTE_TOOL with a memory payload and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas and avoid hardcoding slugs.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing any tools.
Adhere to exact field names and types from the discovery results (schema compliance).
Include a non-null memory object in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({}).
Reuse session IDs within a workflow; generate new ones for new workflows and watch for pagination tokens.

Example Use Cases

Webhook-triggered Apilio action: discover the correct tool slug with RUBE_SEARCH_TOOLS, then run the action via RUBE_MULTI_EXECUTE_TOOL and log results.
Orchestrate three Apilio operations in sequence (enable, run, log) within a single workflow using a shared session_id and memory payload.
Nightly scene update: fetch updated Apilio tool schemas, connect the toolkit, and apply changes by executing the appropriate tool with current arguments.
New automation onboarding: connect to the Apilio toolkit with RUBE_MANAGE_CONNECTIONS, confirm ACTIVE, then perform an initial setup via a discovered tool.
Troubleshooting a failed run: re-fetch tool schemas to adapt to changes, then re-run the tool with the correct slug and updated arguments.

Frequently Asked Questions

Add this skill to your agents