Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts Bigpicture IO Rube MCP Automation

agent tool_use skill risk: high

Bigpicture IO Rube MCP Automation

Instructs on automating Bigpicture IO operations through Composio's toolkit via Rube MCP, requiring RUBE_SEARCH_TOOLS calls first for schemas, connection management with RUBE_MANAG…

  • Human review
  • External action: high

SKILL 1 file

SKILL.md
---
name: bigpicture-io-automation
description: "Automate Bigpicture IO tasks via Rube MCP (Composio). Always search tools first for current schemas."
---
# Bigpicture 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](https://composio.dev/toolkits/bigpicture_io)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Bigpicture IO connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `bigpicture_io`
- 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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `bigpicture_io`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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_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 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](https://composio.dev)*

INPUTS

use_case REQUIRED

description of the Bigpicture IO task to perform

e.g. Bigpicture IO operations

session_id

existing workflow session identifier

REQUIRED CONTEXT

  • RUBE_SEARCH_TOOLS availability
  • bigpicture_io connection status

OPTIONAL CONTEXT

  • existing session_id
  • specific use_case query

TOOLS REQUIRED

  • RUBE_SEARCH_TOOLS
  • RUBE_MANAGE_CONNECTIONS
  • RUBE_MULTI_EXECUTE_TOOL

ROLES & RULES

  1. Always search tools first for current schemas
  2. Always call RUBE_SEARCH_TOOLS first to get current tool schemas
  3. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
  4. If connection is not ACTIVE, follow the returned auth link to complete setup
  5. Confirm connection status shows ACTIVE before running any workflows
  6. Always discover available tools before executing workflows
  7. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
  8. Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
  9. Use exact field names and types from the search results
  10. Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
  11. Reuse session IDs within a workflow
  12. Generate new ones for new workflows
  13. Check responses for pagination tokens and continue fetching until complete

EXPECTED OUTPUT

Format
markdown
Constraints
  • always search tools first
  • verify active connection before execution
  • use exact schemas from search results

SUCCESS CRITERIA

  • Verify connection is ACTIVE
  • Use schema-compliant arguments from search results

FAILURE MODES

  • Hardcoding tool slugs or arguments
  • Skipping RUBE_SEARCH_TOOLS
  • Executing before connection is ACTIVE
  • Omitting memory parameter
  • Not reusing session IDs

CAVEATS

Dependencies
  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Bigpicture IO connection via RUBE_MANAGE_CONNECTIONS
Missing context
  • Target MCP client or environment (e.g., Claude Desktop, Cursor) for the setup steps.
  • Error-handling or retry logic for failed tool calls or inactive connections.
Ambiguities
  • Placeholder text like "your specific Bigpicture IO task" and "TOOL_SLUG_FROM_SEARCH" left for user substitution without explicit formatting guidance.
  • Session ID generation and reuse rules are described but lack concrete examples of valid ID formats.

QUALITY

OVERALL
0.80
CLARITY
0.85
SPECIFICITY
0.80
REUSABILITY
0.75
COMPLETENESS
0.78

IMPROVEMENT SUGGESTIONS

  • Replace inline placeholders with clearly marked template variables such as {{use_case}} and {{tool_slug}}.
  • Add a minimal end-to-end example showing a complete successful workflow with sample IDs and responses.

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR AGENT