bitquery-automation
npx machina-cli add skill ComposioHQ/awesome-claude-skills/bitquery-automation --openclawBitquery Automation via Rube MCP
Automate Bitquery operations through Composio's Bitquery toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/bitquery
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Bitquery connection via
RUBE_MANAGE_CONNECTIONSwith toolkitbitquery - 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 toolkitbitquery - 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: "Bitquery 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 Bitquery task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["bitquery"]
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 Bitquery-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit bitquery |
| 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/bitquery-automation/SKILL.mdView on GitHub Overview
Automates Bitquery operations through Composio's Bitquery toolkit via Rube MCP. It relies on RUBE_SEARCH_TOOLS to fetch current tool schemas and requires an active Bitquery connection via RUBE_MANAGE_CONNECTIONS. This workflow guides discovery, connection validation, and tool execution to streamline Bitquery tasks.
How This Skill Works
First, discover available tools with RUBE_SEARCH_TOOLS to fetch current tool slugs and schemas. Then verify the Bitquery connection using RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE. Finally, execute the selected tool with RUBE_MULTI_EXECUTE_TOOL, supplying the discovered slug, schema-compliant arguments, a memory object, and a session_id.
When to Use It
- When you need to automate Bitquery tasks and want current tool schemas (no hardcoding).
- When you have an established Rube MCP connection and want to run Bitquery workflows.
- When you need to discover available Bitquery tools before choosing an operation.
- When reusing a session_id within a multi-step Bitquery workflow.
- When you must handle schema changes or pagination by re-fetching tool schemas.
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server and run RUBE_SEARCH_TOOLS to verify tool schemas.
- Step 2: Run RUBE_MANAGE_CONNECTIONS with toolkit 'bitquery' and confirm the connection status is ACTIVE.
- Step 3: Run RUBE_MULTI_EXECUTE_TOOL with a discovered TOOL_SLUG, its arguments, memory: {} and a session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to fetch up-to-date tool slugs and schemas.
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing any tools.
- Use exact field names and types from the search results; avoid hardcoding.
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
- Reuse session IDs within a workflow; generate new IDs only for new workflows.
Example Use Cases
- Discover Bitquery tools with RUBE_SEARCH_TOOLS, connect via RUBE_MANAGE_CONNECTIONS, then execute a tool with RUBE_MULTI_EXECUTE_TOOL in a single workflow.
- Reuse a session_id across multiple Bitquery tasks to avoid re-authenticating between steps.
- Handle schema changes by re-fetching tool schemas before each workflow instead of hardcoding slugs.
- Validate the connection status ACTIVE before any execution to prevent failures.
- Include the required memory parameter in every RUBE_MULTI_EXECUTE_TOOL call to ensure proper state management.
