Do I need API keys to use this skill?

No API keys are needed for this setup. Just add the Rube MCP endpoint as an MCP server in your client configuration.

How do I discover available tools for Twelve Data?

Use RUBE_SEARCH_TOOLS with a use_case like Twelve Data operations; it returns tool slugs, input schemas, recommended execution plans, and known pitfalls.

What if tool schemas change or I need to update arguments?

Always search first to get current schemas; never hardcode tool slugs or arguments. Ensure memory is included and the connection remains ACTIVE.

twelve-data-automation

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

Files (1)

SKILL.md

2.9 KB

Twelve Data Automation via Rube MCP

Automate Twelve Data operations through Composio's Twelve Data toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/twelve_data

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["twelve_data"]
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 Twelve Data-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `twelve_data`
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/twelve-data-automation/SKILL.md

View on GitHub

Overview

Automate Twelve Data operations through Composio's Rube MCP toolkit. The workflow always searches for current tool schemas before running any task to adapt to changes. It also requires an active Twelve Data connection for reliable automation.

How This Skill Works

First discover available Twelve Data tools and input schemas with RUBE_SEARCH_TOOLS. Then verify the Twelve Data connection using RUBE_MANAGE_CONNECTIONS and execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, supplying a memory payload and a session_id.

When to Use It

When starting a Twelve Data task, first discover available tools with RUBE_SEARCH_TOOLS to get current slugs and schemas.
When building a workflow, verify the tool connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before running tools.
When tool arguments depend on the schema, populate them from the search results to ensure compatibility.
When performing multiple operations, use RUBE_REMOTE_WORKBENCH and run_composio_tool for bulk execution.
When dealing with paginated results, fetch all pages using the pagination tokens from search results.

Quick Start

Step 1: Verify Rube MCP is connected and search tools are available using RUBE_SEARCH_TOOLS.
Step 2: Manage the Twelve Data connection to ensure the toolkit is ACTIVE via RUBE_MANAGE_CONNECTIONS.
Step 3: Discover a tool slug and execute it with RUBE_MULTI_EXECUTE_TOOL, including memory and session_id.

Best Practices

Always search first to get current tool schemas
Check connection status is ACTIVE before executing tools
Use exact field names and types from the search results
Always 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

Fetch latest price data for a ticker by discovering the appropriate Twelve Data tool and executing it.
Download historical price data for a date range and export results to a file via a discovered tool.
Update a dashboard with new data by running a Twelve Data tool in a recurring workflow.
Run multiple Twelve Data operations in bulk using a remote bench workflow.
Handle a multi-page response by iteratively fetching pages until complete.

Frequently Asked Questions

Add this skill to your agents