What is required before running Apiflash tasks?

An active Rube MCP connection and an active Apiflash connection via the toolkit. Always verify with RUBE_SEARCH_TOOLS and RUBE_MANAGE_CONNECTIONS before execution.

Why must I call RUBE_SEARCH_TOOLS first?

Tool schemas change over time. RUBE_SEARCH_TOOLS returns current tool slugs, input fields, and recommended execution plans, preventing hardcoded values.

How do I ensure successful execution?

Ensure the connection is ACTIVE, use exact field names/types from the tool schema, include memory in RUBE_MULTI_EXECUTE_TOOL calls, and manage sessions consistently within a workflow.

apiflash-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Apiflash Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/apiflash

Prerequisites

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

Step 2: Check Connection

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

Overview

This skill automates Apiflash tasks through Composio's Rube MCP integration. It emphasizes loading the latest tool schemas with RUBE_SEARCH_TOOLS, establishing an ACTIVE Apiflash connection, and executing workflows via RUBE_MULTI_EXECUTE_TOOL. Stay synced with current schemas to avoid hardcoding slugs or fields.

How This Skill Works

Discover available Apiflash tools and their input schemas using RUBE_SEARCH_TOOLS, then establish or verify an ACTIVE connection with RUBE_MANAGE_CONNECTIONS for the apiflash toolkit. Finally, run tools through RUBE_MULTI_EXECUTE_TOOL, supplying the discovered tool_slug and schema-compliant arguments within a session_id.

When to Use It

Automating a sequence of recurring Apiflash tasks in a defined workflow.
Before any execution, fetching current tool schemas with RUBE_SEARCH_TOOLS to avoid stale slugs.
Ensuring the Rube MCP connection is ACTIVE via RUBE_MANAGE_CONNECTIONS prior to execution.
Chaining multiple Apiflash actions in a single session using RUBE_MULTI_EXECUTE_TOOL.
Performing bulk operations or integrating with RUBE_REMOTE_WORKBENCH (run_composio_tool) for scalability.

Quick Start

Step 1: Set up Rube MCP by adding https://rube.app/mcp as an MCP server in your client configuration.
Step 2: Discover tools with RUBE_SEARCH_TOOLS using use_case: 'Apiflash operations' and note the available tool_slugs and schemas.
Step 3: Connect and execute: run RUBE_MANAGE_CONNECTIONS with toolkit 'apiflash', ensure ACTIVE, then use RUBE_MULTI_EXECUTE_TOOL with a discovered tool_slug, proper arguments, memory: {}, and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to obtain current tool slugs and input schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing any tools.
Use exact field names and types from the tool schemas retrieved by RUBE_SEARCH_TOOLS.
Include the memory parameter in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
Reuse session IDs within a workflow and generate new ones only for separate workflows.

Example Use Cases

Discover Apiflash tools with RUBE_SEARCH_TOOLS, connect to toolkit apiflash, then execute a chosen tool in a single session.
Chain multiple Apiflash actions in one session using RUBE_MULTI_EXECUTE_TOOL with the discovered tool slugs.
Perform bulk Apiflash operations via RUBE_REMOTE_WORKBENCH using run_composio_tool for parallel tasks.
Validate current tool schemas with RUBE_GET_TOOL_SCHEMAS to ensure compatibility before integration.
Handle pagination in RUBE_SEARCH_TOOLS responses by continuing fetch until all tools are retrieved.

Frequently Asked Questions

Add this skill to your agents