What is L2s-automation?

A skill that automates L2s operations using Composio's L2s toolkit through Rube MCP, with tool schemas refreshed via RUBE_SEARCH_TOOLS.

What are the prerequisites?

Rube MCP connected (RUBE_SEARCH_TOOLS available) and an ACTIVE L2s connection via RUBE_MANAGE_CONNECTIONS with toolkit l2s.

Do I need to hardcode tool slugs?

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

l2s-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

L2s Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/l2s

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate L2s operations through Composio's L2s toolkit via Rube MCP. It relies on discovering current tool schemas with RUBE_SEARCH_TOOLS before running workflows and ensures a live ACTIVE connection via RUBE_MANAGE_CONNECTIONS.

How This Skill Works

The skill uses RUBE_SEARCH_TOOLS to fetch available L2s tools and their schemas, then validates an ACTIVE L2s connection with RUBE_MANAGE_CONNECTIONS. Workflows are executed with RUBE_MULTI_EXECUTE_TOOL using discovered tool slugs, proper arguments, memory, and a session_id; sessions can be reused within a workflow, and schemas are always taken from the latest search results.

When to Use It

When you need to automate repetitive L2s operations using up-to-date tool schemas
When you must verify a live ACTIVE L2s connection before running workflows
When you want to discover available L2s tools and their input schemas before setup
When chaining multiple tools in a single L2s workflow across a session
When avoiding hard-coded tool details and ensuring schema compliance

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server and verify RUBE_SEARCH_TOOLS can reach tool schemas
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit: ["l2s"] and ensure the session shows ACTIVE
Step 3: Discover a tool with RUBE_SEARCH_TOOLS and execute it via RUBE_MULTI_EXECUTE_TOOL using the provided memory and session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current schemas
Check that RUBE_MANAGE_CONNECTIONS reports ACTIVE before executing
Use exact field names and types from search results
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow and generate new ones for new workflows

Example Use Cases

Automate a data pull from an L2s tool found via RUBE_SEARCH_TOOLS and pass results to a transform tool using its input schema
Set up a workflow that connects to L2s with RUBE_MANAGE_CONNECTIONS and runs several tools in sequence within a single session
Validate tool schemas before execution and handle pagination tokens during tool discovery
Schedule a recurring L2s maintenance task by reusing a session_id and memory parameter
Perform bulk operations with RUBE_REMOTE_WORKBENCH and run_composio_tool using discovered tool slugs

Frequently Asked Questions

Add this skill to your agents