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

SKILL

pilvio-automation

Name: pilvio-automation
Author: Composio

Automate Pilvio tasks through Rube MCP using current tool schemas first.

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 an open-source prompt wrapper with relatively strong source credibility, and it does not declare local code execution or local file access. The main security consideration is that it directs users to connect Rube MCP and a Pilvio account, sending task data to declared remote services, so the overall posture is mostly low risk to caution.

CredentialsCaution

The material states there are no local API keys or environment variables, but it requires an active Pilvio connection via `RUBE_MANAGE_CONNECTIONS` and an auth link if the connection is not active. This implies reliance on third-party account authorization/OAuth-like credentials; no explicit leakage or abuse mechanism is shown, but delegated credentials are still involved and their scope and storage should be reviewed.

Network egressCaution

The README explicitly instructs users to add the remote MCP endpoint `https://rube.app/mcp` and execute operations through Composio/Pilvio tooling. User queries, tool arguments, session IDs, and related business data are therefore likely sent to these declared remote services; the endpoints are stated and relevant to the function, but data egress does occur.

Code executionLow risk

Based on the material, this is a prompt/instructional skill and does not declare starting local processes, running scripts, or invoking system-level capabilities on the host. `RUBE_MULTI_EXECUTE_TOOL` refers to remote MCP/tool execution rather than local code execution.

Data accessCaution

There is no stated access to the local filesystem, clipboard, or device resources, so the local data surface appears limited; however, once connected, the skill can query or act on a Pilvio account, and the README mentions bulk operations and pagination, indicating that effective data access depends on the granted Pilvio tool permissions and should be checked against least privilege.

Supply chainLow risk

The known source is an open-source GitHub repository with strong community adoption (64.7k stars), which are meaningful risk-reducing signals. Although the license is unspecified, maintenance is unknown, and the actual implementation of external services like Rube/Composio cannot be fully audited from this material alone, there are no clear supply-chain red flags in the skill material itself.

Recommendations

Review the privacy policy, data handling, and authorization scope of Rube MCP and Composio/Pilvio before connecting.
Grant only the minimum Pilvio permissions required, and regularly review or revoke unused connections.
Avoid sending unnecessary sensitive business data in tool arguments, especially personal data or highly sensitive operational information.
Validate the actual tool capabilities and parameters returned by `RUBE_SEARCH_TOOLS` in a test environment before using a production account.

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 "pilvio-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/pilvio-automation/SKILL.md
2. Save it as ~/.claude/skills/pilvio-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Pilvio Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/pilvio

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["pilvio"]
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 Pilvio-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `pilvio`
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 AI/ML API workflows via Rube MCP, checking latest tool schemas first.

ComposioGet→

$ loading_