basin-automation
npx machina-cli add skill ComposioHQ/awesome-claude-skills/basin-automation --openclawBasin Automation via Rube MCP
Automate Basin operations through Composio's Basin toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/basin
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Basin connection via
RUBE_MANAGE_CONNECTIONSwith toolkitbasin - 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 toolkitbasin - 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: "Basin 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 Basin task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["basin"]
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 Basin-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit basin |
| 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/basin-automation/SKILL.mdView on GitHub Overview
This skill automates Basin operations using Composio's Basin toolkit through Rube MCP. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before executing workflows to avoid stale configurations.
How This Skill Works
It first discovers available Basin tools with RUBE_SEARCH_TOOLS and reviews their input schemas. Then it verifies the Basin connection with RUBE_MANAGE_CONNECTIONS and ensures it is ACTIVE before running any workflow with RUBE_MULTI_EXECUTE_TOOL, always including a memory payload.
When to Use It
- Automating Basin operations without manual scripting
- When tool schemas change frequently and you must fetch latest definitions
- Executing multiple Basin tasks in a single session with session reuse
- Verifying connection status prior to tool execution
- Integrating Basin tasks into broader automated workflows
Quick Start
- Step 1: Verify RUBE MCP is available and RUBE_SEARCH_TOOLS responds
- Step 2: Manage Basin connection with RUBE_MANAGE_CONNECTIONS and ensure ACTIVE
- Step 3: Discover tools with RUBE_SEARCH_TOOLS and execute a tool with RUBE_MULTI_EXECUTE_TOOL, including memory
Best Practices
- Always call RUBE_SEARCH_TOOLS before any execution
- Do not hardcode tool slugs or arguments; rely on current schemas
- Check RUBE_MANAGE_CONNECTIONS for ACTIVE status before running tools
- Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty
- Reuse session IDs within a workflow and handle pagination tokens if present
Example Use Cases
- Automate a Basin backup by discovering tools, connecting, and executing the backup tool
- Run Basin cleanup and maintenance tasks in a single session using RUBE_MULTI_EXECUTE_TOOL
- Update Basin configurations by fetching new schemas and re-running with updated args
- Audit Basin operations across scheduled jobs with tool discovery first
- Retry failed Basin tool executions by reusing sessions and re-validating connections