open-sea-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/open-sea-automation --openclawOpen Sea Automation via Rube MCP
Automate Open Sea operations through Composio's Open Sea toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/open_sea
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Open Sea connection via
RUBE_MANAGE_CONNECTIONSwith toolkitopen_sea - 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 toolkitopen_sea - 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: "Open Sea 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 Open Sea task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["open_sea"]
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 Open Sea-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit open_sea |
| 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/open-sea-automation/SKILL.mdView on GitHub Overview
Automate Open Sea tasks using Composio's Open Sea toolkit through Rube MCP. This skill emphasizes discovering current tool schemas before execution to avoid hardcoding slugs, ensuring robust, repeatable workflows. It orchestrates discovery, connection checks, and tool execution for Open Sea operations.
How This Skill Works
Tools are first discovered with RUBE_SEARCH_TOOLS to fetch current slugs and input schemas. Then you verify the Open Sea connection is ACTIVE via RUBE_MANAGE_CONNECTIONS and execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, always including memory. Workflows reuse session IDs and rely on live schemas rather than hardcoded values.
When to Use It
- When starting a new Open Sea automation, to fetch up-to-date tool schemas before execution.
- When you need to verify an ACTIVE Open Sea connection prior to running any workflow.
- When you want to discover available tools and their input schemas before coding.
- When automating multi-step Open Sea tasks that should reuse a session within a single workflow.
- When handling large results or paginated responses and continuing fetches until completion.
Quick Start
- Step 1: Add the MCP server (https://rube.app/mcp) and confirm RUBE_SEARCH_TOOLS works.
- Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit open_sea and check ACTIVE status.
- Step 3: Run RUBE_MULTI_EXECUTE_TOOL with a discovered tool_slug and memory: {} using a session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before any execution.
- Use exact field names and types from the search results; avoid hardcoding.
- Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
- Reuse session IDs within a workflow and generate new ones only for new tasks.
Example Use Cases
- Discover tools for an Open Sea task, then run the first matching tool slug with its required arguments.
- Establish an ACTIVE connection to Open Sea, then execute a transfer or listing tool.
- Process a paginated batch of assets by iterating RUBE_SEARCH_TOOLS results and executing tools with next-page tokens.
- Reuse a single session ID across several linked Open Sea tasks in one workflow.
- Update and re-run a workflow after tool schemas change, starting with RUBE_SEARCH_TOOLS.
