bitquery-automation

Overview of bitquery-automation skill

What bitquery-automation does

bitquery-automation is a Claude skill for automating Bitquery tasks through Composio's Rube MCP server. It is designed for workflows that need blockchain data from Bitquery but should not rely on hardcoded tool names or stale schemas. The skill's central rule is simple: search available Rube tools first, then run Bitquery actions only after the current schema and connection state are known.

Best fit for Workflow Automation teams

The bitquery-automation skill is best for developers, analysts, and automation builders who already use Claude with MCP tools and want repeatable Bitquery workflows. Typical jobs include exploring available Bitquery actions, checking wallet or token data, building blockchain data retrieval flows, and turning a natural-language analytics request into a tool-backed execution plan.

Key differentiator: schema discovery first

Unlike a generic prompt that guesses API fields, bitquery-automation tells the agent to call RUBE_SEARCH_TOOLS before execution. That matters because MCP tool schemas can change, Bitquery actions may expose specific required fields, and a wrong assumption can lead to failed calls or incomplete data. The skill is small, but its value is in enforcing the right sequence: discover tools, verify connection, execute, then handle returned data.

Adoption constraints to know

This skill is not a standalone Bitquery SDK, crawler, or dashboard. It requires Rube MCP and an active Bitquery connection managed through Composio. The repository path contains only SKILL.md, so there are no helper scripts, examples, or bundled references to lean on. Install it if you want a disciplined agent workflow for Rube-powered Bitquery automation, not if you need a complete application template.

How to Use bitquery-automation skill

bitquery-automation install and setup

Install the skill from the Composio skills repository:

npx skills add ComposioHQ/awesome-claude-skills --skill bitquery-automation

Then configure Rube MCP in your client by adding the MCP server endpoint:

https://rube.app/mcp

Before using the skill, confirm that RUBE_SEARCH_TOOLS is available. Next, use RUBE_MANAGE_CONNECTIONS with toolkit bitquery and complete the returned authentication flow if the connection is not ACTIVE. Do not ask the agent to run Bitquery tasks until the connection is active; most failures will come from missing MCP access or an incomplete Bitquery connection rather than the prompt itself.

Inputs the skill needs from you

For good bitquery-automation usage, give the agent the specific blockchain question, target chain or network, entity type, identifiers, time range, and output format. Weak input is “get token activity.” Strong input is:

“Use bitquery-automation to find recent transfer activity for token contract 0x... on Ethereum for the last 24 hours. First discover the current Bitquery tools through Rube, verify the Bitquery connection, then return the fields available for transfers and summarize the top 10 transfers in a table.”

This works better because the agent can search tools for a concrete use case, map your request to the current schema, and avoid guessing required fields.

Recommended workflow in practice

A reliable bitquery-automation guide follows four steps:

1. Ask the agent to invoke the skill for a specific Bitquery task.
2. Require RUBE_SEARCH_TOOLS first, using your actual use case as the query.
3. Check RUBE_MANAGE_CONNECTIONS for toolkit bitquery and confirm ACTIVE.
4. Execute the selected Bitquery tool using the schema returned by discovery.

If the first tool search returns multiple candidates, ask the agent to explain which tool it chose and why before running it. This is especially useful for analytics prompts where “transaction,” “trade,” “transfer,” and “balance” may map to different Bitquery capabilities.

Files to read before relying on it

Start with composio-skills/bitquery-automation/SKILL.md. It contains the complete operating model: prerequisites, Rube MCP setup, tool discovery, connection management, and the core execution pattern. There are no README.md, rules/, resources/, references/, or scripts/ files in this skill path, so the upstream SKILL.md is the source of truth. For toolkit-specific behavior, also check the linked Bitquery toolkit documentation at composio.dev/toolkits/bitquery.

bitquery-automation skill FAQ

Is bitquery-automation enough to use Bitquery from Claude?

It is enough if your Claude environment can access Rube MCP and you have an active Bitquery connection through Composio. The skill does not include Bitquery credentials, custom queries, or a local data pipeline. It teaches the agent how to discover and call the available Bitquery tools safely.

How is it better than a normal prompt?

A normal prompt may hallucinate tool names or invent fields. bitquery-automation improves reliability by requiring live tool discovery with RUBE_SEARCH_TOOLS. That is the main reason to install it: the agent should adapt to the current Rube/Bitquery schema instead of relying on memory.

Is this beginner friendly?

It is beginner friendly for users who understand MCP basics, but not for someone who has never configured an MCP server. The setup is short, yet the workflow assumes you can connect Rube MCP, authorize the Bitquery toolkit, and inspect tool responses when something fails.

When should I not use this skill?

Do not use it for tasks that do not need Bitquery, for offline blockchain analysis from your own database, or for production workflows that require audited deterministic code without agent decisions. It is also a poor fit if your organization cannot authorize third-party MCP connections or Composio-managed toolkit access.

How to Improve bitquery-automation skill

Improve prompts for bitquery-automation

The fastest way to improve results is to make the task operational, not conversational. Include the chain, asset, wallet, contract, time window, filters, and desired output. Also state whether you want raw returned fields, a summarized answer, or a reusable workflow.

Better prompt pattern:

“Use bitquery-automation for Workflow Automation. Discover current Bitquery tools first. Check the Bitquery connection. Then retrieve [data type] for [chain/entity] over [time range], using only fields confirmed by the discovered schema. If required fields are missing, ask before execution.”

Avoid common failure modes

The most common failure is skipping discovery and guessing the tool schema. The second is attempting execution before the Bitquery connection is active. A third is asking a vague analytics question without specifying network, identifiers, or time range. Prevent these by explicitly requiring discovery, connection verification, and a short execution plan before the first Bitquery call.

Iterate after the first output

After the initial response, ask the agent to show which tool slug and schema fields were used. If the result is too broad, narrow by chain, contract, block range, timestamp, transaction type, or address list. If it is too sparse, ask the agent to rerun discovery with a more precise use case rather than forcing the same tool call.

Extend the skill for team workflows

Teams can improve bitquery-automation by adding internal examples around their most common Bitquery tasks: token monitoring, wallet investigations, DEX trade summaries, or compliance review exports. Keep those examples schema-aware: tell the agent to rediscover tools every time instead of freezing old field names in prompts. This preserves the skill's main advantage while making repeated workflows faster to run.