What prerequisites are required?

Rube MCP must be connected with RUBE_SEARCH_TOOLS available, and there must be an ACTIVE Turso connection via RUBE_MANAGE_CONNECTIONS using the 'turso' toolkit.

Do I need to hardcode tool slugs?

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

How do I ensure successful execution?

Verify the Turso connection is ACTIVE, include a memory payload in RUBE_MULTI_EXECUTE_TOOL, reuse a valid session_id, and handle pagination when discovering tools or results.

turso-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Turso Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/turso

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["turso"]
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 Turso-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `turso`
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/turso-automation/SKILL.mdView on GitHub

Overview

Automate Turso operations through Composio's Turso toolkit via Rube MCP. Always fetch current tool schemas with RUBE_SEARCH_TOOLS before running workflows, and follow a guided setup to establish a Turso connection and execute tools safely.

How This Skill Works

Connect to Rube MCP and verify RUBE_SEARCH_TOOLS is responsive, then discover Turso tools for your use case. Establish a Turso connection via RUBE_MANAGE_CONNECTIONS with the 'turso' toolkit and run tools with RUBE_MULTI_EXECUTE_TOOL using the discovered slug, the exact input schema, a memory payload, and a session_id.

When to Use It

When you need the current Turso tool schemas before starting a workflow
When you must verify that a Turso connection is ACTIVE before execution
When discovering available Turso tools and their required inputs
When orchestrating a multi-step Turso workflow that uses session management
When troubleshooting or handling pagination while fetching tool schemas or results

Quick Start

Step 1: Add Rube MCP endpoint https://rube.app/mcp as an MCP server and verify RUBE_SEARCH_TOOLS is available.
Step 2: Connect Turso using RUBE_MANAGE_CONNECTIONS with toolkit 'turso' and ensure the status is ACTIVE.
Step 3: Discover available tools with RUBE_SEARCH_TOOLS and run a tool via RUBE_MULTI_EXECUTE_TOOL using the provided slug, inputs, memory, and session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas
Check that RUBE_MANAGE_CONNECTIONS shows an ACTIVE status before executing tools
Use exact field names and types from the tool schemas returned by search
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow and handle pagination tokens until complete

Example Use Cases

Discover and run a Turso backup tool by querying use_case 'Turso operations' and executing the returned slug with proper arguments
Establish a Turso connection via RUBE_MANAGE_CONNECTIONS and confirm it's ACTIVE before a deployment
Run a sequence of Turso tools in a single workflow using RUBE_MULTI_EXECUTE_TOOL and a shared session_id
Perform bulk Turso tasks with RUBE_REMOTE_WORKBENCH and run_composio_tool
Paginate through tool schemas with RUBE_GET_TOOL_SCHEMAS to enumerate all available tools

Frequently Asked Questions

Add this skill to your agents