$ ~/registry/skill/composiohq-composio-skills-plisio-automation

SKILL

plisio-automation

Name: plisio-automation
Author: Composio

Automate Plisio tasks and connect payment workflows through Rube MCP.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

This skill appears to be primarily a prompt/instruction wrapper for using the Rube MCP and Composio Plisio toolkit, with no embedded code, secrets, or local execution logic visible. The main security consideration is that it directs users to connect to a remote MCP service and authorize an external Plisio connection, so overall risk is low with caution around network and account-connection aspects.

CredentialsCaution

The material states the skill itself needs no environment variables or API keys, but the README explicitly requires creating and activating a Plisio connection via `RUBE_MANAGE_CONNECTIONS`, which typically means the user grants account access through an external authorization flow. No direct secret collection or exposure is shown in the skill itself, but there is the standard credential-use risk through the third-party connection layer.

Network egressCaution

The README instructs users to add `https://rube.app/mcp` as an MCP server and execute actions through Composio/Plisio tools; this means user requests, tool arguments, and potentially business data may be sent to the declared remote service. The endpoint is explicitly identified and generally aligned with the stated purpose, making this a normal external-service caution rather than a clear suspicious exfiltration red flag.

Code executionLow risk

Based on the material, this is a prompt-only skill consisting mainly of workflow instructions and tool-calling order, with no auditable local scripts, install commands, or direct system execution capability. It relies on external MCP tools, but the skill text itself does not request privileged local execution.

Data accessCaution

The skill itself does not declare direct access to local files or system data, but through Rube MCP and an authorized Plisio connection it may access payment or business data within that account scope. The material does not specify exact least-privilege boundaries, so this should be treated as normal caution for external account data access rather than assumed overbroad authorization.

Supply chainLow risk

The objective checks indicate this is prompt-only and open source, sourced from the high-adoption GitHub repository `ComposioHQ/awesome-claude-skills` (64.7k stars), which materially reduces supply-chain risk. Although the license is not declared and maintenance status is unknown, and the material looks more like a catalog entry than a standalone implementation repo, there is no sign of a closed-source payload, spoofed origin, or obvious injection red flag.

Recommendations

Only connect to `https://rube.app/mcp` after confirming you trust Rube/Composio's terms and data-handling practices.
Use the least-privileged Plisio account or scope possible, and regularly review or revoke connections you no longer need.
Verify tool names and parameters returned by `RUBE_SEARCH_TOOLS` before execution to avoid sending sensitive business data to the wrong tool.
Test first in an isolated environment or low-sensitivity account before using it with production payment data.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "plisio-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/plisio-automation/SKILL.md
2. Save it as ~/.claude/skills/plisio-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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

Automate searching, creating, and updating Plain workflows and tasks.

ComposioGet→

$ loading_