Do I need API keys to use this skill?

No API keys are needed for the MCP endpoint itself; Alpha Vantage authentication is handled by the toolkit connection established via RUBE_MANAGE_CONNECTIONS.

How do I discover available tools?

Use RUBE_SEARCH_TOOLS with the Alpha Vantage use_case to fetch current tool slugs and their input schemas.

What if tool schemas change?

Always search for current schemas before execution and rely on live schema fields rather than hardcoding.

alpha-vantage-automation

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

Files (1)

SKILL.md

2.9 KB

Alpha Vantage Automation via Rube MCP

Automate Alpha Vantage operations through Composio's Alpha Vantage toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/alpha_vantage

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["alpha_vantage"]
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 Alpha Vantage-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `alpha_vantage`
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/alpha-vantage-automation/SKILL.md

View on GitHub

Overview

Orchestrate Alpha Vantage operations through Composio's toolkit using Rube MCP. The skill emphasizes discovering current tool schemas before use and maintaining an ACTIVE Alpha Vantage connection, ensuring consistent, up-to-date executions.

How This Skill Works

First, call RUBE_SEARCH_TOOLS to fetch available Alpha Vantage tool slugs and their input schemas. Then verify the Alpha Vantage connection with RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE. Finally, execute tools via RUBE_MULTI_EXECUTE_TOOL (including a memory payload) within a session, reusing session IDs when appropriate and avoiding hardcoded slugs.

When to Use It

When tool schemas change and you must fetch current slugs and arguments via RUBE_SEARCH_TOOLS
When establishing or verifying an ACTIVE Alpha Vantage connection through RUBE_MANAGE_CONNECTIONS
When orchestrating a sequence of Alpha Vantage tasks in a single session with RUBE_MULTI_EXECUTE_TOOL
When you need exact, schema-compliant arguments derived from live tool searches
When performing bulk or batch operations using RUBE_REMOTE_WORKBENCH or multiple tools

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client and run RUBE_SEARCH_TOOLS to load current Alpha Vantage tool schemas.
Step 2: Run RUBE_MANAGE_CONNECTIONS with toolkits: ["alpha_vantage"] and ensure the connection status is ACTIVE.
Step 3: Execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL using the tool_slug and schema-compliant arguments, including memory and a session_id.

Best Practices

Always run RUBE_SEARCH_TOOLS before executing to get current tool schemas
Ensure RUBE_MANAGE_CONNECTIONS shows ACTIVE before any runs
Pass memory (even empty) in RUBE_MULTI_EXECUTE_TOOL calls
Reuse session IDs within a workflow; avoid unnecessary new sessions
Avoid hardcoding tool_slugs or arguments; rely on live schemas and exact field names from the search results

Example Use Cases

Discover tools with RUBE_SEARCH_TOOLS, connect with RUBE_MANAGE_CONNECTIONS for alpha_vantage, then execute a discovered tool via RUBE_MULTI_EXECUTE_TOOL in a single session.
Batch multiple Alpha Vantage tasks in one workflow by reusing the same session_id and memory across several RUBE_MULTI_EXECUTE_TOOL calls.
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS to validate inputs before automation.
Run bulk operations using RUBE_REMOTE_WORKBENCH with run_composio_tool() for efficiency.
Handle paginated responses by following tokens in tool outputs and continuing fetches until complete.

Frequently Asked Questions

Add this skill to your agents