What prerequisites are required to use this skill?

RUBE MCP must be connected and ready, with an active Blocknative connection and RUBE_SEARCH_TOOLS available.

Do I need API keys to use this skill?

No API keys are required. Add the MCP endpoint and authenticate via the Rube MCP workflow.

How do I keep tool definitions up to date?

Always call RUBE_SEARCH_TOOLS before executing any tool to fetch current tool slugs and input schemas.

blocknative-automation

npx machina-cli add skill ComposioHQ/awesome-claude-skills/blocknative-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Blocknative Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/blocknative

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Blocknative connection via RUBE_MANAGE_CONNECTIONS with toolkit blocknative
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 blocknative
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: "Blocknative 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 Blocknative task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["blocknative"]
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 Blocknative-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `blocknative`
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/blocknative-automation/SKILL.md

View on GitHub

Overview

Automate Blocknative operations through Composio's Blocknative toolkit using Rube MCP. This skill centers on discovering up-to-date tool schemas with RUBE_SEARCH_TOOLS and establishing a verified connection with RUBE_MANAGE_CONNECTIONS before running workflows.

How This Skill Works

Connect to Rube MCP and ensure an active Blocknative toolkit connection. Discover available tools with RUBE_SEARCH_TOOLS to get current slugs and input schemas. Execute selected tools using RUBE_MULTI_EXECUTE_TOOL with the correct arguments and include memory, reusing session IDs where appropriate.

When to Use It

When you need to automate Blocknative tasks without hardcoding tool slugs, ensuring tool schemas are always current.
When tool schemas change and you must fetch fresh inputs via RUBE_SEARCH_TOOLS before execution.
When building scripted workflows that perform multiple Blocknative actions in sequence.
When confirming the Blocknative connection is ACTIVE before running workflows.
When you want to re-use a session across related Blocknative tasks to improve continuity.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration and verify RUBE_SEARCH_TOOLS responds.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["blocknative"] and complete any required auth to ensure ACTIVE status.
Step 3: Use RUBE_SEARCH_TOOLS to discover tools for Blocknative, then run a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and properly formed arguments, including memory.

Best Practices

Always run RUBE_SEARCH_TOOLS first to fetch current tool slugs and schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing any tool.
Use exact field names and types from the tool schemas returned by RUBE_SEARCH_TOOLS.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
Reuse session IDs within a workflow and fetch pagination tokens until complete.

Example Use Cases

Discover Blocknative tools with RUBE_SEARCH_TOOLS and run a chosen tool via RUBE_MULTI_EXECUTE_TOOL using the returned slug.
Establish a Blocknative connection with RUBE_MANAGE_CONNECTIONS, then execute a sequence of tools in one session.
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS to validate inputs before execution.
Bulk operations with RUBE_REMOTE_WORKBENCH and run_composio_tool() for multiple tasks.
Review tool options and pitfalls; adjust inputs according to the current tool schemas.

Frequently Asked Questions

Add this skill to your agents