What is plisio-automation?

A workflow to automate Plisio tasks via Composio's Plisio toolkit using Rube MCP.

What are the prerequisites?

Rube MCP must be connected and expose RUBE_SEARCH_TOOLS; an active Plisio connection with toolkit 'plisio' is required; always call RUBE_SEARCH_TOOLS first.

How do I execute a Plisio tool?

Discover tools with RUBE_SEARCH_TOOLS, ensure the connection is ACTIVE with RUBE_MANAGE_CONNECTIONS, then run RUBE_MULTI_EXECUTE_TOOL using the discovered tool_slug and include memory and a session_id.

plisio-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Plisio Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/plisio

Prerequisites

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

Step 2: Check Connection

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

Overview

Automates Plisio operations through Composio's Plisio toolkit using Rube MCP. It requires an active Plisio connection and you must always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.

How This Skill Works

The workflow starts by discovering available tools with RUBE_SEARCH_TOOLS, then verifies the Plisio connection with RUBE_MANAGE_CONNECTIONS, and finally executes the chosen tool via RUBE_MULTI_EXECUTE_TOOL. Memory must be included and tool schemas must be used from the search results rather than hard-coded slugs.

When to Use It

When you need to automate a Plisio operation but tool schemas may change, so always fetch current schemas first.
When you must verify the Plisio connection is ACTIVE before running any workflow.
When orchestrating a sequence of tools in a single session using a shared session_id.
When performing bulk operations or multi-tool execution using RUBE_MULTI_EXECUTE_TOOL or RUBE_REMOTE_WORKBENCH.
When you need the latest full tool schemas or to handle pagination tokens during discovery.

Quick Start

Step 1: Confirm RUBE MCP connectivity by calling RUBE_SEARCH_TOOLS to fetch current tool schemas.
Step 2: Manage the Plisio connection with RUBE_MANAGE_CONNECTIONS for toolkit 'plisio' and ensure status is ACTIVE.
Step 3: Discover tools, then execute a tool using RUBE_MULTI_EXECUTE_TOOL with the discovered slug, proper arguments, memory, and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from search results; do not hardcode slugs or arguments.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty (memory: {}).
Reuse session IDs within a workflow and fetch additional pages if pagination tokens are present.

Example Use Cases

Discover available Plisio tools with RUBE_SEARCH_TOOLS for use_case 'Plisio operations' and then execute a chosen tool slug with proper arguments.
Check that the Plisio connection is ACTIVE using RUBE_MANAGE_CONNECTIONS before proceeding with a workflow.
Run multiple Plisio tools in a single session via RUBE_MULTI_EXECUTE_TOOL with the discovered tool slugs and memory.
Perform bulk tasks by invoking RUBE_REMOTE_WORKBENCH and using run_composio_tool() for batching.
Retrieve the full tool schemas with RUBE_GET_TOOL_SCHEMAS to refresh schemas that include schemaRef.

Frequently Asked Questions

Add this skill to your agents