home / skills / composiohq / awesome-claude-skills / cabinpanda-automation

cabinpanda-automation skill

safe

/cabinpanda-automation

This skill automates Cabinpanda tasks via Rube MCP, guiding you to discover current tool schemas first and execute tooling reliably.

npx playbooks add skill composiohq/awesome-claude-skills --skill cabinpanda-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: cabinpanda-automation
description: "Automate Cabinpanda tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Cabinpanda Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/cabinpanda](https://composio.dev/toolkits/cabinpanda)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Cabinpanda connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `cabinpanda`
- 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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `cabinpanda`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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_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 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](https://composio.dev)*

Overview

This skill automates Cabinpanda operations by orchestrating Composio’s Cabinpanda toolkit through a Rube MCP server. It provides a repeatable pattern for discovering current tool schemas, managing Cabinpanda connections, and executing toolkit tools reliably. The emphasis is on always querying the MCP for live schemas and validating connections before running workflows.

How this skill works

First, call RUBE_SEARCH_TOOLS to discover available Cabinpanda tools, their input schemas, and recommended execution plans. Next, use RUBE_MANAGE_CONNECTIONS to ensure an active Cabinpanda connection. Finally, execute the desired operations via RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH for bulk runs), supplying schema-compliant arguments and a memory object.

When to use it

Automating routine Cabinpanda tasks like creating or updating records
Building workflows that orchestrate multiple Cabinpanda toolkit tools
Running bulk operations or remote workbench jobs through Composio
Integrating Cabinpanda actions into larger Claude agent workflows
When you need up-to-date tool schemas before executing operations

Best practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool slugs and input schemas
Verify connection status with RUBE_MANAGE_CONNECTIONS and follow auth links if needed
Use exact field names and types from the returned schemas—do not hardcode inputs
Include a memory parameter (even an empty {}) in RUBE_MULTI_EXECUTE_TOOL calls
Reuse session IDs within a workflow; generate new session IDs for separate workflows
Handle pagination in tool-search or schema responses and iterate until complete

Example use cases

Discover the latest Cabinpanda tool for creating invoices, then execute it with validated fields
Run a sequence that updates customer records and triggers downstream notifications
Perform bulk data transformations using RUBE_REMOTE_WORKBENCH run_composio_tool()
Embed Cabinpanda operations inside a Claude agent workflow that coordinates sales and support actions

FAQ

Do I need API keys to use Rube MCP?

No API keys are required for the MCP endpoint; add https://rube.app/mcp as an MCP server in your client configuration.

What if a tool schema changes after I coded my workflow?

Always re-run RUBE_SEARCH_TOOLS before execution. Update your inputs to match the latest schema fields and types returned by the search.