cdr-platform-automation
by ComposioHQcdr-platform-automation helps Claude automate Cdr Platform tasks through Composio Rube MCP by discovering live tool schemas, checking the cdr_platform connection, and executing safer workflow automation.
This skill scores 64/100, which means it is acceptable for directory listing but should be treated as a lightweight integration guide rather than a fully developed workflow skill. Directory users get enough information to know it is for Cdr Platform automation via Composio/Rube MCP and how an agent should begin safely, but the repository evidence suggests limited Cdr Platform-specific operational detail.
- Valid skill frontmatter and a clear description identify the intended trigger: automating Cdr Platform tasks through Rube MCP.
- Prerequisites and setup steps are explicit, including requiring RUBE_SEARCH_TOOLS, an active cdr_platform connection via RUBE_MANAGE_CONNECTIONS, and confirming ACTIVE status before workflows.
- The skill instructs agents to discover current tool schemas first, which reduces risk of stale or incorrect tool calls.
- Workflow guidance appears mostly generic to Rube MCP tool discovery rather than Cdr Platform-specific operations, so users may still need to infer exact task flows from discovered schemas.
- Repository evidence shows no support files, references, scripts, README, or install command beyond MCP setup guidance in SKILL.md.
Overview of cdr-platform-automation skill
What cdr-platform-automation does
cdr-platform-automation is a Claude skill for automating Cdr Platform operations through Composio’s Rube MCP toolkit. Instead of hard-coding outdated API assumptions, the skill’s central rule is to search Rube tools first, retrieve the current Cdr Platform tool schemas, confirm the active connection, and then execute the task through the discovered tool plan.
Best-fit users and workflows
This skill is best for operators, support teams, RevOps-style automation builders, and developers who already use Claude with MCP and want safer Cdr Platform workflow automation. It fits tasks where you need Claude to inspect available Cdr Platform actions, choose the right Rube tool, map your inputs to the current schema, and explain what it is about to run before execution.
Key differentiator: schema-first execution
The practical value of the cdr-platform-automation skill is not a long built-in playbook; it is the guardrail that the agent should call RUBE_SEARCH_TOOLS before acting. That matters because Composio tool schemas and supported Cdr Platform operations can change. A generic prompt may invent parameters, while this skill pushes the agent to discover current tool slugs, required fields, execution plans, and known pitfalls first.
What to verify before installing
Install this skill only if your Claude client can use MCP and you can add the Rube MCP server. The upstream skill contains a single SKILL.md and no helper scripts, resources, or local validation utilities, so adoption depends on your live Rube MCP connection and Cdr Platform authorization rather than bundled repository code.
How to Use cdr-platform-automation skill
cdr-platform-automation install and setup path
Install the skill from the repository with:
npx skills add ComposioHQ/awesome-claude-skills --skill cdr-platform-automation
Then add Rube MCP to your client using the endpoint https://rube.app/mcp. In the skill source, the required MCP server is rube, and the expected first available tool is RUBE_SEARCH_TOOLS. Before asking for automation, use RUBE_MANAGE_CONNECTIONS with toolkit cdr_platform and complete the returned authorization flow if the connection is not ACTIVE.
Inputs the skill needs for reliable usage
For strong cdr-platform-automation usage, give Claude the business task, target records or filters, required outputs, and safety limits. Weak input is “update Cdr Platform.” Stronger input is: “Using Cdr Platform via Rube MCP, find the current tools for updating customer records, verify the cdr_platform connection is active, show the required schema, then update only records matching these IDs. Do not create or delete anything unless you ask me first.”
That extra context helps the skill choose the right discovered tool, avoid destructive actions, and ask for missing fields instead of guessing.
Prompt pattern that invokes the skill well
A practical prompt should make the discovery step explicit:
“Use the cdr-platform-automation skill for Workflow Automation. First call RUBE_SEARCH_TOOLS for this specific use case: [task]. Reuse the returned session ID, check the cdr_platform connection status with RUBE_MANAGE_CONNECTIONS, summarize the selected tool schema, list any required fields I have not provided, and wait for confirmation before executing changes.”
This pattern is especially useful when the task may modify Cdr Platform data. It turns the skill into a controlled tool-discovery and execution workflow rather than a one-shot instruction.
Repository files to read first
Start with composio-skills/cdr-platform-automation/SKILL.md. It contains the real operating instructions: prerequisites, Rube MCP setup, tool discovery, and the core workflow pattern. There are no README.md, rules/, resources/, references/, or scripts/ folders in the current skill path, so do not spend time looking for hidden implementation logic. The live Rube tool discovery response is the source of truth for available actions.
cdr-platform-automation skill FAQ
Is cdr-platform-automation beginner-friendly?
It is beginner-friendly only if you are comfortable configuring MCP in your AI client and completing an external connection flow. The skill’s instructions are short, but successful use depends on understanding that Claude must call Rube tools, not merely describe an automation plan.
How is this better than an ordinary prompt?
An ordinary prompt can ask Claude to automate Cdr Platform tasks, but it may rely on stale assumptions. The cdr-platform-automation skill adds a repeatable sequence: discover tools with RUBE_SEARCH_TOOLS, confirm the cdr_platform connection, inspect the live schema, then execute. That reduces guesswork and makes failures easier to diagnose.
When should I not use this skill?
Do not use it if your environment cannot connect to Rube MCP, if your Cdr Platform connection cannot be authorized, or if you need offline automation without live tool calls. It is also a poor fit for highly regulated production changes unless you add your own approval, logging, and rollback procedures around the agent workflow.
Does it include ready-made Cdr Platform scripts?
No. The skill is not a script package. It is an agent instruction layer for using Composio’s Cdr Platform toolkit through Rube MCP. The concrete operations available to you come from the live RUBE_SEARCH_TOOLS response, not from checked-in scripts in the repository.
How to Improve cdr-platform-automation skill
Improve cdr-platform-automation results with better task framing
The skill performs best when you describe the exact Cdr Platform outcome, scope, and constraints. Include IDs, date ranges, field names, allowed actions, and whether the agent should only read, draft, update, or execute. If you are unsure of the field names, ask Claude to search tools first and return the schema before requesting any write action.
Add safety gates for write operations
For production workflow automation, require a preview step. A strong instruction is: “Before executing, show the selected Rube tool slug, required input object, affected record count if available, and a plain-English risk summary.” This compensates for the skill’s minimal repository structure and helps prevent accidental broad updates.
Handle common failure modes
If Claude cannot proceed, check three things in order: RUBE_SEARCH_TOOLS is available, the cdr_platform connection is ACTIVE, and the task description matches a supported Cdr Platform tool returned by discovery. If a parameter error occurs, ask Claude to re-run discovery for the same session and compare your provided fields against the returned schema.
Iterate after the first output
After the first run, save the discovered tool slug, required fields, and successful prompt pattern for your team. The next cdr-platform-automation guide prompt can then say: “Use the same workflow as the previous approved run, but re-check current schemas before execution.” This keeps the workflow repeatable without assuming the Composio toolkit has stayed unchanged.