leiga-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/leiga-automation --openclawLeiga Automation via Rube MCP
Automate Leiga operations through Composio's Leiga toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/leiga
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Leiga connection via
RUBE_MANAGE_CONNECTIONSwith toolkitleiga - 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 toolkitleiga - 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: "Leiga 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 Leiga task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["leiga"]
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 Leiga-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit leiga |
| 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/leiga-automation/SKILL.mdView on GitHub Overview
This skill automates Leiga operations by connecting Rube MCP to the Leiga toolkit. It emphasizes discovering current tool schemas first to avoid stale slugs and arguments, and provides setup, discovery, and execution guidance.
How This Skill Works
Connect to the Rube MCP endpoint and verify RUBE_SEARCH_TOOLS is available. Manage Leiga connections with RUBE_MANAGE_CONNECTIONS for the leiga toolkit, then discover tools using RUBE_SEARCH_TOOLS with the Leiga use_case. After confirming the connection is ACTIVE, execute a selected tool via RUBE_MULTI_EXECUTE_TOOL with the required arguments and a memory object, always including the session_id. Tool schemas, slugs, and inputs are obtained dynamically to avoid hardcoding.
When to Use It
- When starting a Leiga workflow, first search for current tool schemas to avoid stale slugs.
- Before executing any tool, ensure the Leiga connection is ACTIVE via RUBE_MANAGE_CONNECTIONS.
- When automating a batch of Leiga operations, discover multiple tools and run them in sequence.
- If tool schemas change or you need new capabilities, re-run RUBE_SEARCH_TOOLS to refresh inputs.
- During long-running Leiga tasks, reuse session IDs and include an explicit memory object.
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server and verify RUBE_SEARCH_TOOLS.
- Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["leiga"] and activate the connection.
- Step 3: Discover tools with RUBE_SEARCH_TOOLS, then execute a chosen tool with RUBE_MULTI_EXECUTE_TOOL using memory and session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to fetch current tool slugs and schemas.
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before any executions.
- Use exact field names and types from discovery results; avoid hardcoding.
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even when empty.
- Reuse session IDs within a workflow and generate new IDs for new workflows.
Example Use Cases
- Automate a Leiga data fetch: discover tools with use_case 'Leiga operations', pick a slug, and run it with the required arguments.
- Set up a persistent Leiga connection, then execute a recurring tool daily using a stored session_id and memory.
- Orchestrate two Leiga tools in one run by discovering multiple tool slugs and executing them in sequence via RUBE_MULTI_EXECUTE_TOOL.
- Handle schema changes by re-running RUBE_SEARCH_TOOLS before updating a workflow that uses a tool slug.
- Batch Leiga tasks using RUBE_REMOTE_WORKBENCH and run_composio_tool() to streamline execution.
