How do I ensure I have the latest tool schemas?

Always call RUBE_SEARCH_TOOLS first to fetch current tool slugs and input schemas before any execution.

How can I confirm the Adrapid connection is ready?

Use RUBE_MANAGE_CONNECTIONS with the 'adrapid' toolkit and check that the status is ACTIVE.

Do I need to include a memory object in tool execution?

Yes. Include 'memory' in RUBE_MULTI_EXECUTE_TOOL calls, even if it is empty ({}).

adrapid-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Adrapid Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/adrapid

Prerequisites

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

Step 2: Check Connection

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

Overview

This skill automates Adrapid operations through Composio's Adrapid toolkit using Rube MCP. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before execution to avoid hardcoding and to adapt to schema changes.

How This Skill Works

You first verify RUBE_SEARCH_TOOLS is available, then use RUBE_MANAGE_CONNECTIONS to activate the Adrapid toolkit. After confirming an ACTIVE connection, you discover tools and their input schemas, and finally run tools with RUBE_MULTI_EXECUTE_TOOL, supplying the required arguments and memory context from the search results.

When to Use It

Automating recurring Adrapid tasks using discovered tool schemas.
When tool schemas update, requiring a fresh discovery before use.
Before any workflow, ensuring an ACTIVE Adrapid connection is present.
Executing multiple Adrapid tools in a single workflow with memory context.
Reusing session IDs across related tasks and handling large result sets via pagination.

Quick Start

Step 1: Ensure RUBE_SEARCH_TOOLS is available by configuring the MCP endpoint and querying for Adrapid tools.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit 'adrapid' and verify the connection is ACTIVE.
Step 3: Discover tools via RUBE_SEARCH_TOOLS, then execute a chosen tool with RUBE_MULTI_EXECUTE_TOOL using memory and the session_id.

Best Practices

Always search first for updated tool schemas and do not hardcode tool slugs or arguments.
Verify the Adrapid connection is ACTIVE before executing any tools.
Use exact field names and types from the tool schemas returned by RUBE_SEARCH_TOOLS.
Always include a memory object in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and handle pagination tokens to fetch complete results.

Example Use Cases

Discover Adrapid tools with RUBE_SEARCH_TOOLS and execute a selected task slug with proper arguments.
Connect to Adrapid via RUBE_MANAGE_CONNECTIONS and confirm ACTIVE status before running workflows.
Run a multi-tool Adrapid operation using RUBE_MULTI_EXECUTE_TOOL with a memory payload.
Maintain continuity by reusing a session_id across related Adrapid tasks within a single workflow.
Handle pagination by continuing to fetch results from RUBE_SEARCH_TOOLS until all tools are retrieved.

Frequently Asked Questions

Add this skill to your agents