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

basin-automation skill

safe

/basin-automation

This skill automates Basin tasks via Rube MCP by discovering current tool schemas first, ensuring reliable, up-to-date workflows.

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

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

Files (1)

SKILL.md

2.8 KB

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

# Basin Automation via Rube MCP

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

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

## Prerequisites

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

Overview

This skill automates Basin operations by orchestrating Composio’s Basin toolkit through the Rube MCP endpoint. It standardizes discovery, connection checks, and tool execution so workflows remain robust as tool schemas evolve. It emphasizes always querying RUBE_SEARCH_TOOLS first to fetch current tool slugs and input schemas.

How this skill works

The skill first calls RUBE_SEARCH_TOOLS to retrieve available Basin tool descriptions, input schemas, and recommended execution plans. It then confirms an active Basin connection via RUBE_MANAGE_CONNECTIONS and runs actions using RUBE_MULTI_EXECUTE_TOOL (including an explicit memory object and session_id). The pattern enforces schema compliance, session reuse, and pagination handling to avoid runtime failures.

When to use it

Automating repetitive Basin tasks that must call Composio tools reliably.
When tool schemas or available actions may change frequently and you need live discovery.
Before running multi-step workflows that require session state and proper memory handling.
For bulk operations or remote workbench runs that must use discovered tool slugs.
When integrating Basin actions into larger Claude-driven automation flows.

Best practices

Always call RUBE_SEARCH_TOOLS at the start of every workflow — never hardcode tool slugs or arguments.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE for the basin toolkit before executing any tool.
Use exact field names and types returned in the tool schema; validate inputs against the schema.
Include a memory object (even empty {}) in RUBE_MULTI_EXECUTE_TOOL calls and reuse session_id for the workflow.
Check for pagination tokens in search responses and fetch until complete; generate new session IDs for new workflows.

Example use cases

Discover available Basin export/import tools and run a data migration using RUBE_MULTI_EXECUTE_TOOL.
Validate and activate a Basin connection for a new tenant, following the auth link returned by RUBE_MANAGE_CONNECTIONS.
Batch-run composio Basin operations from a remote workbench using RUBE_REMOTE_WORKBENCH and run_composio_tool().
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS to build a UI form dynamically before executing a user-triggered Basin task.

FAQ

Do I need API keys to use Rube MCP?

No API keys are required; add https://rube.app/mcp as an MCP server in your client configuration and use the Rube MCP endpoints.

What happens if tool schemas change mid-workflow?

If schemas change, subsequent RUBE_SEARCH_TOOLS calls will return updated schemas. Avoid hardcoding arguments and re-run search before executing additional steps to stay schema-compliant.