$ ~/registry/skill/composiohq-composio-skills-twelve-data-automation

SKILL

twelve-data-automation

Connect and automate Twelve Data workflows through Rube MCP tools.

Stars

★ 73,665

Source

GitHub

Updated

2026-08-28

// securityLow risk

Prompt only, no code
Open source
Community-trusted· 73.7k

Running security audit…

Credentials
Network egress
Code execution
Data access
Supply chain

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "twelve-data-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/twelve-data-automation/SKILL.md
2. Save it as ~/.claude/skills/twelve-data-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// use cases

Integrate Twelve Data into a workflow

When developers integrate Twelve Data into an automation flow, they can first discover current tool schemas, then verify the connection and execute the right tool to avoid failures from outdated parameters.

Manage connection and execution consistently

When analysts or researchers need to call Twelve Data through Rube MCP, they can follow a consistent sequence of tool discovery, connection verification, and execution.

Run bulk or multi-step automations

For multi-step Twelve Data operations, users can reuse the same session and handle details like pagination, schemaRef, and the required memory parameter as noted in the docs.

// docs

AI summary

The document explains how to automate Twelve Data operations through Composio's toolkit via Rube MCP. It covers prerequisites, connection setup, and a standard workflow: search tools first, verify the twelve_data connection, then execute with schema-compliant arguments. It also highlights common pitfalls such as not hardcoding schemas, always including the memory field, reusing session IDs within a workflow, and checking pagination or full schemas when needed.

Show full docs ▾

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

// FAQ

What does this skill do?

It automates Twelve Data operations through Composio's Twelve Data toolkit via Rube MCP. The docs emphasize searching tools first, then checking the connection before execution.

What prerequisites are required?

You need Rube MCP connected and RUBE_SEARCH_TOOLS available. You also need an active twelve_data connection set up through RUBE_MANAGE_CONNECTIONS.

Why must I search tools first?

Because tool schemas may change, the docs explicitly advise against hardcoding tool slugs or arguments. You should call RUBE_SEARCH_TOOLS first and execute based on the current schema.

Automate Baserow table tasks and data workflows through Rube MCP.

ComposioGet→

$ loading_