home / skills / composiohq / awesome-claude-skills / beaconchain-automation

beaconchain-automation skill

safe

/beaconchain-automation

This skill automates Beaconchain tasks via Rube MCP, discovering current tool schemas before execution to ensure up-to-date workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill beaconchain-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: beaconchain-automation
description: "Automate Beaconchain tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Beaconchain Automation via Rube MCP

Automate Beaconchain operations through Composio's Beaconchain toolkit via Rube MCP.

**Toolkit docs**: [composio.dev/toolkits/beaconchain](https://composio.dev/toolkits/beaconchain)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Beaconchain connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `beaconchain`
- 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 `beaconchain`
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: "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_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 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](https://composio.dev)*

Overview

This skill automates Beaconchain operations using Composio's Beaconchain toolkit via Rube MCP. It provides a reliable workflow pattern to discover tools, verify connections, and execute composable Beaconchain tasks programmatically. The skill emphasizes always searching tools first to stay compatible with changing tool schemas.

How this skill works

First call RUBE_SEARCH_TOOLS to fetch current tool slugs, input schemas, and recommended execution plans. Use RUBE_MANAGE_CONNECTIONS to ensure the beaconchain toolkit connection is ACTIVE. Execute actions with RUBE_MULTI_EXECUTE_TOOL (including an explicit memory object and session_id) or run bulk jobs via RUBE_REMOTE_WORKBENCH when needed.

When to use it

Automating Beaconchain node or validator tasks that require composable tool calls
Building repeatable workflows that must adapt to changing tool schemas
Running bulk or remote Beaconchain operations via Composio toolkits
Integrating Beaconchain operations into an agent that uses Rube MCP
Prototyping or orchestrating multi-step Beaconchain procedures programmatically

Best practices

Always call RUBE_SEARCH_TOOLS first and use the returned schemas; never hardcode tool slugs or arguments
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE for the beaconchain toolkit before any execution
Include a memory object (empty {} if unused) in every RUBE_MULTI_EXECUTE_TOOL call
Reuse session_id across the same workflow; generate a new session for distinct workflows
Handle pagination in search responses and follow schemaRef responses with RUBE_GET_TOOL_SCHEMAS

Example use cases

Discover available Beaconchain admin tools and run a maintenance command using RUBE_MULTI_EXECUTE_TOOL
Connect a new Beaconchain environment via RUBE_MANAGE_CONNECTIONS, complete auth flow, then run verification checks
Perform bulk validator operations using RUBE_REMOTE_WORKBENCH with run_composio_tool() for parallel tasks
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS before building a custom orchestration agent

FAQ

Do I need API keys to use Rube MCP?

No. Add https://rube.app/mcp as an MCP server in your client configuration; the MCP endpoint works without API keys.

What should I do if a tool call fails due to schema mismatch?

Run RUBE_SEARCH_TOOLS again to retrieve the current schema, adjust your arguments to match exact field names and types, and retry.