beaconchain-automation
npx machina-cli add skill ComposioHQ/awesome-claude-skills/beaconchain-automation --openclawBeaconchain Automation via Rube MCP
Automate Beaconchain operations through Composio's Beaconchain toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/beaconchain
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Beaconchain connection via
RUBE_MANAGE_CONNECTIONSwith toolkitbeaconchain - 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 toolkitbeaconchain - 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: "Beaconchain 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 Beaconchain task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["beaconchain"]
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 Beaconchain-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit beaconchain |
| 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/beaconchain-automation/SKILL.mdView on GitHub Overview
This skill automates Beaconchain operations using Composio's Beaconchain toolkit through Rube MCP. It emphasizes discovering current tool schemas first and ensuring an ACTIVE connection before execution, enabling reliable, repeatable Beaconchain workflows.
How This Skill Works
The workflow starts by discovering available tools with RUBE_SEARCH_TOOLS to fetch current slugs and input schemas. It then verifies an ACTIVE Beaconchain connection via RUBE_MANAGE_CONNECTIONS and finally executes the chosen tool with RUBE_MULTI_EXECUTE_TOOL, including a memory payload and the appropriate session_id. This pattern minimizes hardcoded values and adapts to schema changes in real time.
When to Use It
- When you need to perform a specific Beaconchain operation after fetching up-to-date tool schemas.
- When setting up a new Beaconchain workflow and you must connect and authorize the toolkit.
- When you want to run multiple Beaconchain operations in a single session using a multi-tool execution flow.
- When you need to bulk-run operations or test a series of tools via remote bench.
- When tool schemas change and you must re-fetch slugs before executing.
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server in your client, then run RUBE_SEARCH_TOOLS to fetch current Beaconchain tool schemas.
- Step 2: Run RUBE_MANAGE_CONNECTIONS with toolkits: ["beaconchain"] and ensure the connection status is ACTIVE.
- Step 3: Run RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug and arguments from the search results, including memory: {} and your session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS before executing any workflow to obtain current tool slugs and schemas.
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools.
- Use exact field names and types from the search results; avoid hardcoding slugs or args.
- Include the memory parameter in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
- Reuse session IDs within a workflow and handle pagination tokens if tool lists are long.
Example Use Cases
- Discover the Beaconchain tools for a health check and run a status tool within a single session.
- Establish a Beaconchain toolkit connection, verify it's ACTIVE, then execute a synchronization tool with discovered args.
- Test a new workflow by discovering a tool, connecting, and performing a single execution with an empty memory payload.
- Bulk-run a sequence of Beaconchain operations in one workflow using RUBE_MULTI_EXECUTE_TOOL across multiple discovered tools.
- Handle pagination while searching tools: fetch pages until you obtain the desired tool slug before execution.
