pilvio-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/pilvio-automation --openclawPilvio 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_CONNECTIONSwith toolkitpilvio - 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 toolkitpilvio - 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_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 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
Source
git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/pilvio-automation/SKILL.mdView on GitHub Overview
Automate Pilvio operations through Composio's Pilvio toolkit via Rube MCP. The workflow relies on always discovering current tool schemas before execution to prevent broken integrations. Requires an active Rube MCP connection and an active Pilvio connection, with a prerequisite to run RUBE_SEARCH_TOOLS first.
How This Skill Works
The skill uses a three-step core workflow: first, discover available Pilvio tools using RUBE_SEARCH_TOOLS to obtain up-to-date tool slugs and input schemas; second, verify the Pilvio connection with RUBE_MANAGE_CONNECTIONS and ensure the session is active; third, execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL with the proper memory payload and the discovered schema fields. Always include memory in execute calls and reuse session IDs when appropriate.
When to Use It
- You need to automate Pilvio tasks without hardcoding tool slugs or arguments.
- Tool schemas change frequently and you must fetch current schemas before execution.
- Setting up a new Pilvio task or workflow that relies on current tool definitions.
- You want to validate and maintain an active connection to Pilvio before running tools.
- You are orchestrating multiple Pilvio tools in a sequence or bulk operation.
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server in your client configuration and verify RUBE_SEARCH_TOOLS responds.
- Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit 'pilvio' and ensure the session is ACTIVE.
- Step 3: Use RUBE_MULTI_EXECUTE_TOOL with the discovered tool slug and a memory payload, reusing your session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS before executing any workflow to get current tool slugs and input schemas.
- Check that RUBE_MANAGE_CONNECTIONS reports ACTIVE before running tools.
- Use exact field names and types from the search results; avoid hardcoding arguments.
- Always include the memory parameter in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
- Reuse session IDs within a workflow; generate new sessions only for separate workflows.
Example Use Cases
- Discover Pilvio tools with RUBE_SEARCH_TOOLS, select a data-fetch tool, establish an ACTIVE Pilvio connection, and run the tool using RUBE_MULTI_EXECUTE_TOOL with the required memory payload.
- For a multi-step Pilvio task, reuse a session ID across steps to maintain context and execute subsequent tools.
- Handle pagination by iterating over results from RUBE_SEARCH_TOOLS and continuing with new tool executions until completion.
- Execute a bulk set of Pilvio operations via RUBE_REMOTE_WORKBENCH and the run_composio_tool() flow using discovered tool slugs.
- Switch to a different Pilvio task by re-running RUBE_SEARCH_TOOLS to obtain updated tool schemas before execution.
