playbooks

home / skills / composiohq / awesome-claude-skills / cdr-platform-automation

cdr-platform-automation skill

/cdr-platform-automation

This skill automates Cdr Platform tasks via Rube MCP by discovering current tool schemas first and ensuring active connections.

npx playbooks add skill composiohq/awesome-claude-skills --skill cdr-platform-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: cdr-platform-automation
description: "Automate Cdr Platform tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Cdr Platform Automation via Rube MCP

Automate Cdr Platform operations through Composio's Cdr Platform toolkit via Rube MCP.

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

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["cdr_platform"]
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 Cdr Platform-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `cdr_platform` |
| 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 Cdr Platform tasks through Composio's Rube MCP integration. It provides a repeatable pattern for discovering tools, verifying connections, and executing toolkit operations while enforcing live schema checks. Use it to run single or bulk Cdr Platform workflows with reliable session and memory handling.

How this skill works

The skill always queries RUBE_SEARCH_TOOLS first to retrieve current tool slugs, input schemas, and execution guidance. It then verifies an active connection via RUBE_MANAGE_CONNECTIONS for the cdr_platform toolkit and runs operations with RUBE_MULTI_EXECUTE_TOOL (including memory and a session_id). For bulk work it can call RUBE_REMOTE_WORKBENCH and fetch full schemas with RUBE_GET_TOOL_SCHEMAS.

When to use it

  • Automate Cdr Platform tasks that require up-to-date tool schemas
  • Run ad hoc or scheduled workflows against the Cdr Platform via Composio/Rube MCP
  • Perform bulk operations or complex multi-step processes using discovered tools
  • Build integrations that must avoid hardcoded tool names or argument shapes
  • Orchestrate workflows that require session reuse and consistent memory handling

Best practices

  • Always call RUBE_SEARCH_TOOLS before any execution to get current schemas and recommended plans
  • Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE for toolkit cdr_platform before executing tools
  • Include a memory parameter (can be empty object) in every RUBE_MULTI_EXECUTE_TOOL call
  • Reuse session_id for related workflow steps and generate a new session for distinct workflows
  • Respect exact field names and types from tool search results; handle pagination tokens when listing results

Example use cases

  • Discover available Cdr Platform operations and run a single toolkit tool with schema-compliant arguments
  • Run a bulk data migration or batch update using RUBE_REMOTE_WORKBENCH and run_composio_tool()
  • Automate user onboarding tasks that require multiple Cdr Platform calls reused in one session
  • Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS before building a dynamic UI or CLI integration

FAQ

What must I do before executing any tool?

Always run RUBE_SEARCH_TOOLS to retrieve live tool slugs and schemas, then confirm the cdr_platform connection is ACTIVE with RUBE_MANAGE_CONNECTIONS.

Can I hardcode tool slugs and argument shapes?

No. Tool schemas change; hardcoding will break workflows. Always use search results for exact field names and types.