What prerequisites must be met to use this skill?

Rube MCP must be connected, an active Currents API connection via RUBE_MANAGE_CONNECTIONS with the currents_api toolkit must exist, and RUBE_SEARCH_TOOLS must be available.

Why must tool schemas be discovered before execution?

Tool slugs and argument schemas can change; discovering tools ensures you use up-to-date definitions and avoid hardcoding.

How do I run multiple Currents API tasks in a single workflow?

Establish an active connection, discover tools, then use RUBE_MULTI_EXECUTE_TOOL with a memory object and the discovered tool_slugs, reusing the same session_id where appropriate.

currents-api-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Currents API Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/currents_api

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["currents_api"]
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 Currents API-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `currents_api`
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/currents-api-automation/SKILL.md

View on GitHub

Overview

This skill lets you orchestrate Currents API operations through Composio's Currents API toolkit using Rube MCP. It emphasizes always searching for current tool schemas before execution to avoid stale slugs and args. Prerequisites include a connected Rube MCP and an active Currents API connection using the currents_api toolkit.

How This Skill Works

You first discover available tools with RUBE_SEARCH_TOOLS, then verify the Currents toolkit connection via RUBE_MANAGE_CONNECTIONS, and finally execute the chosen tool(s) with RUBE_MULTI_EXECUTE_TOOL, passing the discovered arguments and a memory object. This pattern ensures schema accuracy, connection readiness, and proper session handling for each workflow.

When to Use It

When you need to automate a Currents API task end-to-end from discovery to execution
When tool schemas or slugs change and you must re-fetch definitions
When you require an ACTIVE connection before running workflows
When chaining multiple Currents API calls in a single session
When bulk or remote-bench execution of multiple tools is needed

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server and verify RUBE_SEARCH_TOOLS is responsive
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["currents_api"] and ensure the status is ACTIVE
Step 3: Use RUBE_SEARCH_TOOLS to discover tools, then run RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug and memory

Best Practices

Always call RUBE_SEARCH_TOOLS before any workflow
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from the search results
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow; generate new ones for new workflows

Example Use Cases

Discover a Currents API operation, validate the connection, then execute the tool with discovered args to fetch data
Chain multiple Currents API read tools in a single session to aggregate results
After a schema update, re-search tools and re-run the workflow to ensure compatibility
Bulk operations: use RUBE_REMOTE_WORKBENCH with run_composio_tool() to batch multiple tools
Create or update records via a Currents API tool by executing the appropriate slug with the required memory state

Frequently Asked Questions

Add this skill to your agents