cdr-platform-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/cdr-platform-automation --openclawCdr 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
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Cdr Platform connection via
RUBE_MANAGE_CONNECTIONSwith toolkitcdr_platform - 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 toolkitcdr_platform - 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: "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_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 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
Source
git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/cdr-platform-automation/SKILL.mdView on GitHub Overview
Automate Cdr Platform operations using Composio’s Rube MCP toolkit. This skill orchestrates discovery of current tool schemas, establishes a Cdr Platform connection, and executes tasks in a controlled workflow. Always perform tool discovery first to ensure up-to-date inputs and avoid hardcoding slugs.
How This Skill Works
It discovers available tools via RUBE_SEARCH_TOOLS with a Cdr Platform use_case, then validates and establishes the Cdr Platform connection using RUBE_MANAGE_CONNECTIONS. Finally, it executes the selected tool through RUBE_MULTI_EXECUTE_TOOL, including a memory payload and a valid session_id; memory must be provided even if empty.
When to Use It
- You need to automate a Cdr Platform task and want current tool schemas before execution.
- You must verify the Cdr Platform connection is ACTIVE before running workflows.
- You want to explore available tools and their input schemas prior to scripting a task.
- You plan to run bulk or chained tool executions via RUBE_REMOTE_WORKBENCH.
- You need to fetch full tool schemas or regenerate execution plans using RUBE_GET_TOOL_SCHEMAS.
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server in your client configuration (no API keys needed).
- Step 2: Verify RUBE_SEARCH_TOOLS is available and discover Cdr Platform tools.
- Step 3: Check connection with RUBE_MANAGE_CONNECTIONS, then execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and a memory payload.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to get up-to-date tool slugs and schemas.
- Ensure RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing any tools.
- Use exact field names and types as returned by the tool schemas.
- Include a non-empty memory payload in every RUBE_MULTI_EXECUTE_TOOL call (even if empty {}).
- Reuse session IDs within a workflow and generate new ones for separate runs.
Example Use Cases
- Discover tools for Cdr Platform tasks, verify an ACTIVE connection, and execute a chosen tool with a memory object and a session_id.
- Automate a sequence of Cdr Platform operations by reusing a session_id across multiple tool executions.
- Perform bulk operations using RUBE_REMOTE_WORKBENCH to run several discovered tools in one workflow.
- Handle pagination in tool discovery responses and continue fetching until all tools are retrieved.
- Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS to prep for a new automation task and prevent schema drift.
