Skills / ComposioHQ/awesome-claude-skills / finage-automation Try your first task finage-automation
Start a fresh conversation. Replace the highlighted placeholders.
Use finage-automation to, with Rube connected and an active Finage connection, discover the current supported options for [market-data objective] and return a no-change execution plan. Required inputs User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
name: finage-automation description: "Automate Finage tasks via Rube MCP (Composio). Always search tools first for current schemas." requires: mcp: [rube] Finage Automation via Rube MCP
Automate Finage operations through Composio's Finage toolkit via Rube MCP.
Toolkit docs : composio.dev/toolkits/finage
Prerequisites
Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Finage connection via RUBE_MANAGE_CONNECTIONS with toolkit finage
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 finage
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: "Finage 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 Finage task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["finage"]
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
Powered by Composio