How do I ensure tool schemas are current?

Always call RUBE_SEARCH_TOOLS before executing and avoid hardcoding tool slugs or arguments.

What if the Control D connection isn't ACTIVE?

Use RUBE_MANAGE_CONNECTIONS to activate the connection and follow the provided auth link.

Is including memory mandatory in executions?

Yes. Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).

control-d-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/control-d-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Control D Automation via Rube MCP

Automate Control D operations through Composio's Control D toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/control_d

Prerequisites

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

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit control_d
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: "Control D 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 Control D task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["control_d"]
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 Control D-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `control_d`
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/control-d-automation/SKILL.mdView on GitHub

Overview

Automate Control D operations through Composio's Control D toolkit via Rube MCP. Always discover current tool schemas before execution to stay in sync with changes.

How This Skill Works

Fetch available tools and schemas with RUBE_SEARCH_TOOLS, then verify an ACTIVE connection using RUBE_MANAGE_CONNECTIONS for the control_d toolkit. Finally, execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, passing the correct arguments and memory payload, reusing sessions when appropriate.

When to Use It

You need to automate a specific Control D operation after discovering the latest tool schemas.
You must verify the Control D connection is ACTIVE before running any workflow.
You want to run a selected Control D tool with exact schema-compliant arguments.
You need to perform bulk operations on multiple tools via a single workflow.
You want to fetch the full tool schemas to compare against current tool slugs and arguments.

Quick Start

Step 1: Get Rube MCP by adding https://rube.app/mcp as an MCP server in your client configuration.
Step 2: Verify RUBE_SEARCH_TOOLS responds and discover Control D tool schemas; then call RUBE_MANAGE_CONNECTIONS for toolkits control_d.
Step 3: Run RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug and proper arguments; include memory and reuse a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS before executing to get current tool slugs and schemas.
Ensure RUBE_MANAGE_CONNECTIONS shows ACTIVE status prior to tool execution.
Use exact field names and types from the search results; do not hardcode slugs or arguments.
Include a memory parameter in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow; generate new ones only for new workflows.

Example Use Cases

Discover available Control D tools with RUBE_SEARCH_TOOLS and run a specific operation using its discovered slug and schema.
Establish an ACTIVE connection to Control D via RUBE_MANAGE_CONNECTIONS and execute a tool for an automated task.
Execute a selected tool using RUBE_MULTI_EXECUTE_TOOL with the correct arguments and a session_id.
Perform bulk operations using RUBE_REMOTE_WORKBENCH with run_composio_tool() to run multiple tools.
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS and compare against current search results to adapt workflows.

Frequently Asked Questions

Add this skill to your agents