Get the FREE Ultimate OpenClaw Setup Guide →

livesession-automation

Scanned
npx machina-cli add skill ComposioHQ/awesome-claude-skills/livesession-automation --openclaw
Files (1)
SKILL.md
2.9 KB

Livesession Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/livesession

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["livesession"]
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

OperationApproach
Find toolsRUBE_SEARCH_TOOLS with Livesession-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit livesession
ExecuteRUBE_MULTI_EXECUTE_TOOL with discovered tool slugs
Bulk opsRUBE_REMOTE_WORKBENCH with run_composio_tool()
Full schemaRUBE_GET_TOOL_SCHEMAS for tools with schemaRef

Powered by Composio

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/livesession-automation/SKILL.mdView on GitHub

Overview

Automate Livesession operations using Composio's Livesession toolkit via Rube MCP. It emphasizes discovering current tool schemas before execution to prevent hardcoded slugs or arguments and to ensure an ACTIVE connection prior to workflows.

How This Skill Works

Connect to Rube MCP at https://rube.app/mcp and verify RUBE_SEARCH_TOOLS responds. Discover available Livesession tools to obtain current slugs and input schemas, then check the connection with RUBE_MANAGE_CONNECTIONS for the livesession toolkit. Execute tools with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and schema-compliant arguments, including a memory object and a session_id; reuse sessions when appropriate.

When to Use It

  • Discover current Livesession tool schemas and slugs before performing any task.
  • Validate that the Livesession connection is ACTIVE before workflow execution.
  • Execute a discovered tool with schema-compliant arguments and memory.
  • Adapt to updated tool schemas by re-running RUBE_SEARCH_TOOLS instead of hardcoding.
  • Perform bulk or sequential tool calls using RUBE_REMOTE_WORKBENCH when needed.

Quick Start

  1. Step 1: Add the MCP server https://rube.app/mcp as an MCP server in your client.
  2. Step 2: Run RUBE_SEARCH_TOOLS to verify availability and inspect tool slugs/schemas.
  3. Step 3: Call RUBE_MANAGE_CONNECTIONS for toolkit 'livesession', ensure ACTIVE, then execute workflows with RUBE_MULTI_EXECUTE_TOOL using the discovered tool slugs and a memory object.

Best Practices

  • Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.
  • Verify RUBE_MANAGE_CONNECTIONS reports ACTIVE before running tools.
  • Use exact field names and types from the search results (schema compliance).
  • Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
  • Reuse session IDs within a workflow; generate new ones for new workflows.

Example Use Cases

  • Discover Livesession operations with RUBE_SEARCH_TOOLS and execute a specific task slug.
  • Establish and verify an ACTIVE Livesession connection using RUBE_MANAGE_CONNECTIONS.
  • Execute a discovered tool with arguments from the tool schema using RUBE_MULTI_EXECUTE_TOOL.
  • Perform multiple tools in a single batch using RUBE_REMOTE_WORKBENCH run_composio_tool.
  • Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS to confirm schemaRef usage.

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers