cabinpanda-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/cabinpanda-automation --openclawCabinpanda Automation via Rube MCP
Automate Cabinpanda operations through Composio's Cabinpanda toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/cabinpanda
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Cabinpanda connection via
RUBE_MANAGE_CONNECTIONSwith toolkitcabinpanda - 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 toolkitcabinpanda - 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: "Cabinpanda 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 Cabinpanda task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["cabinpanda"]
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 Cabinpanda-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit cabinpanda |
| 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/cabinpanda-automation/SKILL.mdView on GitHub Overview
Automate Cabinpanda operations through Composio's Cabinpanda toolkit via Rube MCP. The skill emphasizes discovering up-to-date tool schemas before workflow execution to avoid stale slugs. It streamlines setup, connection validation, and tool execution for reliable automation.
How This Skill Works
Start by discovering available Cabinpanda tools with RUBE_SEARCH_TOOLS to get current slugs and input schemas. Then establish and verify an ACTIVE connection using RUBE_MANAGE_CONNECTIONS for the cabinpanda toolkit. Finally, execute selected tools with RUBE_MULTI_EXECUTE_TOOL using a valid session and including the memory parameter.
When to Use It
- When you need up-to-date tool schemas before running Cabinpanda tasks
- When incorporating Cabinpanda into automated workflows and reusing sessions
- When validating and establishing an active Cabinpanda connection prior to execution
- When executing multiple Cabinpanda tools in sequence within a single session
- When debugging tool discovery or handling schema and pagination changes
Quick Start
- Step 1: Add the Rube MCP endpoint https://rube.app/mcp in your client configuration
- Step 2: Run RUBE_SEARCH_TOOLS with a Cabinpanda use case to fetch current tool slugs and schemas
- Step 3: Establish a cabinpanda connection with RUBE_MANAGE_CONNECTIONS and execute tools using RUBE_MULTI_EXECUTE_TOOL with a session and memory
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 the search results; avoid hardcoding
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
- Reuse session IDs within a workflow and generate new ones for new workflows
Example Use Cases
- Discover Cabinpanda tools for a task and execute the corresponding tool slug with required arguments
- Establish a cabinpanda connection and confirm ACTIVE before automation runs
- Execute multiple Cabinpanda tools in a single session using memory and a session_id
- Perform bulk Cabinpanda operations via RUBE_REMOTE_WORKBENCH run_composio_tool
- Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS and adapt automation to new fields