What is api-labz-automation?

A skill to automate API Labz tasks using the Rube MCP workflow language and the api_labz toolkit.

What is required to use this skill?

Rube MCP must be connected with RUBE_SEARCH_TOOLS available, and there must be an active API Labz connection via RUBE_MANAGE_CONNECTIONS for the api_labz toolkit.

What is the recommended workflow?

Discover available tools with RUBE_SEARCH_TOOLS, check the connection with RUBE_MANAGE_CONNECTIONS, then execute the tool with RUBE_MULTI_EXECUTE_TOOL, including memory and a session_id, and remember to reuse sessions when possible.

api-labz-automation

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

Files (1)

SKILL.md

2.9 KB

API Labz Automation via Rube MCP

Automate API Labz operations through Composio's API Labz toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/api_labz

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate API Labz operations with the Composio API Labz toolkit via Rube MCP. Always search for current tool schemas before executing tasks to ensure tooling stays up to date. This skill guides you from setup and connection to discovering tools and running workflows.

How This Skill Works

It discovers available API Labz tools using RUBE_SEARCH_TOOLS, then verifies an ACTIVE connection via RUBE_MANAGE_CONNECTIONS for the api_labz toolkit. It finally executes chosen tools with RUBE_MULTI_EXECUTE_TOOL, passing schema compliant arguments, a memory payload, and a session_id.

When to Use It

Starting a new API Labz task and ensuring you have the latest tool schemas
Setting up a fresh API Labz workflow that requires an ACTIVE connection
Running a workflow by first discovering tools and then selecting a slug
Performing multi-step Labz operations with session reuse across steps
Handling tool schema changes or pagination to fetch complete results

Quick Start

Step 1: Verify RUBE_SEARCH_TOOLS responds to confirm tool schemas are up to date
Step 2: Use RUBE_MANAGE_CONNECTIONS to connect the api_labz toolkit and ensure ACTIVE
Step 3: Discover tools with RUBE_SEARCH_TOOLS, then run RUBE_MULTI_EXECUTE_TOOL with a chosen tool slug, arguments, memory and session_id

Best Practices

Always call RUBE_SEARCH_TOOLS to fetch current tool schemas before executing
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status prior to execution
Use exact field names and types from search results
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow and avoid generating new ones unnecessarily

Example Use Cases

Discover the API Labz tool for a specific task, then execute with required arguments
Set up a persistent session for a multi step API Labz workflow and reuse across steps
Validate tool schemas with RUBE_SEARCH_TOOLS before running to prevent runtime errors
Ensure the api_labz connection is ACTIVE before execution to avoid failures
Handle pagination by checking for tokens in search results and continuing until complete

Frequently Asked Questions

Add this skill to your agents