$ ~/registry/skill/composiohq-composio-skills-bitquery-automation

SKILL

bitquery-automation

Discover and run Bitquery tools through Rube MCP for automated workflows.

Stars

★ 73,862

Source

GitHub

Updated

2026-08-29

// securityLow risk

Prompt only, no code
Open source
Community-trusted· 73.9k

Running security audit…

Credentials
Network egress
Code execution
Data access
Supply chain

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "bitquery-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/bitquery-automation/SKILL.md
2. Save it as ~/.claude/skills/bitquery-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// use cases

Automate Bitquery workflow execution

Developers or data analysts can use Rube MCP to chain tool discovery, connection checks, and execution steps, reducing manual effort for Bitquery-related operations.

Get the latest tool schema before running

When tool slugs or arguments may change, users can search for current tools and input schemas first, then execute with lower risk of failure from schema changes.

Handle connection and pagination issues

In Bitquery automation workflows, users can first confirm the connection is ACTIVE and then inspect pagination tokens in responses to complete data retrieval step by step.

// docs

AI summary

The README explains how to automate Bitquery operations through Composio’s Bitquery toolkit via Rube MCP. It covers prerequisites, connection setup, the standard workflow of searching tools, checking connection status, and executing discovered tools, plus operational cautions such as schema changes, session reuse, required memory fields, and pagination handling.

Show full docs ▾

Bitquery 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_CONNECTIONS with toolkit bitquery
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 bitquery
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_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 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

// FAQ

What does this skill mainly do?

It is used to automate Bitquery-related operations through Composio’s Bitquery toolkit via Rube MCP. The docs specifically emphasize searching tools first and then executing against the current schema.

What prerequisites are needed before using it?

Your client needs Rube MCP connected and must have access to RUBE_SEARCH_TOOLS. You also need to create and activate a bitquery connection through RUBE_MANAGE_CONNECTIONS.

Why must I search tools first?

Because tool schemas may change, the docs explicitly say not to hardcode tool slugs or arguments. You should first use RUBE_SEARCH_TOOLS to get current tools, input schemas, and execution guidance.

Automate BTCPay Server payment and merchant operations through Rube MCP.

ComposioGet→

$ loading_