placid-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/placid-automation --openclawPlacid Automation via Rube MCP
Automate Placid operations through Composio's Placid toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/placid
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Placid connection via
RUBE_MANAGE_CONNECTIONSwith toolkitplacid - 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 toolkitplacid - 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: "Placid 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 Placid task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["placid"]
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 Placid-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit placid |
| 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/placid-automation/SKILL.mdView on GitHub Overview
Automate Placid operations through Composio's Placid toolkit via Rube MCP. Always search tools first to obtain current schemas, ensuring your workflows stay aligned with tool updates. This approach reduces errors and keeps Placid automations reliable.
How This Skill Works
Connect Rube MCP to Placid by verifying RUBE_SEARCH_TOOLS, then manage the placid toolkit connection with RUBE_MANAGE_CONNECTIONS. Discover available tool slugs and schemas using RUBE_SEARCH_TOOLS, then execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, including the memory parameter and a session_id. This pattern ensures up-to-date schemas, proper session handling, and repeatable executions.
When to Use It
- You need to automate a Placid operation end-to-end while ensuring current tool schemas are used.
- You’re setting up a new Placid integration and must establish an ACTIVE connection using the placid toolkit.
- A multi-step workflow requires reusing a session (session_id) across steps for continuity.
- Planning a bulk Placid operation that runs multiple discovered tools, possibly via bulk ops.
- You suspect schema drift and want to refresh tool schemas before executing any tool.
Quick Start
- Step 1: Ensure RUBE_SEARCH_TOOLS responds to confirm tool schema availability.
- Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["placid"] and verify ACTIVE status.
- Step 3: Use RUBE_MULTI_EXECUTE_TOOL with a discovered tool slug, memory: {}, and a session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to fetch current Placid tool schemas.
- Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
- Use exact field names and types from the search results; avoid hardcoding slugs or args.
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even when empty (memory: {}).
- Reuse session IDs within a workflow; generate new session IDs only for new workflows.
Example Use Cases
- Automate a daily Placid status check by discovering the relevant tool, confirming an ACTIVE connection, and executing the tool.
- If a workflow stalls, re-authenticate with RUBE_MANAGE_CONNECTIONS and continue using the existing session.
- Run a Placid cleanup task by discovering the correct tool slug and executing with a memory payload.
- Execute multiple Placid tools in bulk using RUBE_REMOTE_WORKBENCH and run_composio_tool for efficiency.
- Update a multi-step Placid workflow by refreshing tool schemas with RUBE_SEARCH_TOOLS before adding new steps.
