bigpicture-io-automation
npx machina-cli add skill ComposioHQ/awesome-claude-skills/bigpicture-io-automation --openclawBigpicture IO Automation via Rube MCP
Automate Bigpicture IO operations through Composio's Bigpicture IO toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/bigpicture_io
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Bigpicture IO connection via
RUBE_MANAGE_CONNECTIONSwith toolkitbigpicture_io - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitbigpicture_io - 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: "Bigpicture IO 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 Bigpicture IO task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["bigpicture_io"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Bigpicture IO-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit bigpicture_io |
| 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/bigpicture-io-automation/SKILL.mdView on GitHub Overview
Automate Bigpicture IO operations through Composio's Bigpicture IO toolkit using Rube MCP. The workflow always starts by discovering current tool schemas to adapt to changes. Requires a connected Rube MCP and an ACTIVE Bigpicture IO connection with the bigpicture_io toolkit.
How This Skill Works
You first discover available tools with RUBE_SEARCH_TOOLS to fetch current tool slugs and input schemas. Then you verify connectivity with RUBE_MANAGE_CONNECTIONS and ensure the toolkit is ACTIVE. Finally, you execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL using the discovered slug and schema-compliant arguments, including a memory object; repeat within a session as needed.
When to Use It
- To automate a specific Bigpicture IO task end-to-end using Rube MCP and the bigpicture_io toolkit
- When tool schemas update, to avoid hardcoding slugs or fields
- Before running any workflow, to ensure RUBE_SEARCH_TOOLS can fetch current slugs and schemas
- To run multiple Bigpicture IO tools in a single session with RUBE_MULTI_EXECUTE_TOOL
- To verify the connection and handle authentication flow via RUBE_MANAGE_CONNECTIONS when needed
Quick Start
- Step 1: Connect Rube MCP (add https://rube.app/mcp) and verify RUBE_SEARCH_TOOLS responds
- Step 2: Use RUBE_SEARCH_TOOLS to discover available bigpicture_io tools and capture the tool slug and required arguments
- Step 3: Use RUBE_MANAGE_CONNECTIONS to confirm the toolkit bigpicture_io is ACTIVE, then run RUBE_MULTI_EXECUTE_TOOL with the discovered tool slug and a memory payload
Best Practices
- Always run RUBE_SEARCH_TOOLS first to fetch current schemas
- Ensure RUBE_MANAGE_CONNECTIONS reports ACTIVE before executing tools
- Use exact field names and types from the search results; avoid hardcoding
- Include the memory parameter in RUBE_MULTI_EXECUTE_TOOL, even if empty
- Reuse session IDs within a workflow and regenerate for new workflows
Example Use Cases
- Automate a specific Bigpicture IO task by discovering TOOL_SLUG_FROM_SEARCH via RUBE_SEARCH_TOOLS and executing with RUBE_MULTI_EXECUTE_TOOL using the returned arguments
- Set up and verify an ACTIVE connection to bigpicture_io, then execute a tool to fetch or modify IO data
- Perform bulk operations by using RUBE_REMOTE_WORKBENCH with run_composio_tool()
- Handle pagination by continuing to fetch tool schemas until no more tokens are returned
- Reuse a session_id across related tools in a single workflow to maintain context
