$ ~/registry/skill/composiohq-composio-skills-control-d-automation

SKILL

control-d-automation

Name: control-d-automation
Author: Composio

Automate Control D configuration and management tasks through Rube MCP.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

This skill is primarily an instructional/prompt-style wrapper and does not itself declare local secrets or local code execution. However, it is designed around remote Rube MCP and Composio/Control D integrations for tool discovery and execution, so real-world use involves external connectivity and third-party account authorization that should be reviewed carefully.

CredentialsCaution

The material says 'No API keys needed,' but it also requires establishing an ACTIVE `control_d` connection via `RUBE_MANAGE_CONNECTIONS` and completing an auth link, indicating reliance on third-party account authorization/connection tokens. No local plaintext secret collection is shown, but credentials are managed by an external integration layer, which carries ordinary authorization-abuse exposure.

Network egressCaution

It explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and references `composio.dev` documentation. The `RUBE_SEARCH_TOOLS` and `RUBE_MULTI_EXECUTE_TOOL` flow will send task descriptions, parameters, and session data to remote services. The material does not list unrelated exfiltration endpoints, and no obvious covert-exfiltration red flags are present.

Code executionLow risk

System checks identify this as a `prompt-only` skill. The document mainly provides call ordering and argument patterns, and does not declare local process spawning, script execution, or system-level execution privileges. It may trigger remote tool execution, but the material does not show local code execution capability.

Data accessCaution

The skill itself does not declare direct local file read/write access. However, performing Control D 'operations' through the toolkit implies access to authorized Control D account/configuration data, and queries, execution payloads, pagination, and memory/session data may fall within third-party processing scope. No local data permissions beyond the stated purpose are shown.

Supply chainLow risk

The source is a GitHub open-source repository, and the system marks it as open-source; strong community adoption (64.7k stars) is a significant risk-reducing signal. The current material looks more like a skill entry in a well-known repository. The missing license declaration and unknown maintenance status add some uncertainty, but not enough to constitute a high-risk red flag.

Recommendations

Review the privacy policy, logging retention, and data-handling scope for `rube.app/mcp` and Composio before connecting.
Use a least-privilege account for the `control_d` authorization and avoid granting unnecessary administrative rights.
Inspect the actual tool schemas and parameters returned by `RUBE_SEARCH_TOOLS` before execution to avoid unintended changes to sensitive configurations.
Validate the workflow in a test environment or low-privilege tenant before using it against production accounts.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "control-d-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/control-d-automation/SKILL.md
2. Save it as ~/.claude/skills/control-d-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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

Automate Retailed workflows via Rube MCP after checking current tool schemas.

ComposioGet→

$ loading_