What do I need to start dpd2-automation?

A connected Rube MCP, the dpd2 toolkit, and an ACTIVE connection. Always start by calling RUBE_SEARCH_TOOLS to fetch current tool schemas.

Why must I call RUBE_SEARCH_TOOLS first?

Tool schemas change over time; searching first prevents hardcoding slugs and arguments.

How do I execute a Dpd2 tool?

Use RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug, provide exact schema-compliant arguments, include memory, and pass the session_id from your workflow.

dpd2-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Dpd2 Automation via Rube MCP

Automate Dpd2 operations through Composio's Dpd2 toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/dpd2

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Dpd2 operations through Composio's Dpd2 toolkit via Rube MCP. Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas and verify an ACTIVE Dpd2 connection before running workflows.

How This Skill Works

Discover available Dpd2 tools with RUBE_SEARCH_TOOLS and use the returned tool slugs and schemas. Validate your connection with RUBE_MANAGE_CONNECTIONS and then execute tools through RUBE_MULTI_EXECUTE_TOOL, supplying memory and a session_id from your workflow.

When to Use It

You are setting up a new Dpd2 operation and need up-to-date tool schemas.
You need to verify the Dpd2 connection is ACTIVE before running a workflow.
You are automating a Dpd2 task chain that requires multiple tool executions in sequence.
You are troubleshooting a workflow and need to refresh tool schemas and session state.
You want to reuse a session across several Dpd2 tool executions and handle pagination if needed.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration.
Step 2: Verify RUBE_SEARCH_TOOLS responds and call RUBE_MANAGE_CONNECTIONS with toolkit 'dpd2'; complete auth if required and ensure ACTIVE.
Step 3: Use RUBE_SEARCH_TOOLS to discover tools, then execute with RUBE_MULTI_EXECUTE_TOOL using the discovered slug, proper arguments, memory, and session_id.

Best Practices

Always search for tools first with RUBE_SEARCH_TOOLS to get current schemas.
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing any tool.
Use exact field names and types from the search results; avoid guessing.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and handle pagination tokens when listing tools.

Example Use Cases

Discover tools for a Dpd2 task, establish an ACTIVE connection, then execute a single tool in a new session.
Run a batch of Dpd2 operations by reusing the same session and memory payload across multiple tool executions.
Debug a failed tool by re-searching the tool schemas, confirming the connection, and retrying with exact schema fields.
Migrate a Dpd2 task to a new workflow by generating a new session_id while reusing discovered tool slugs.
Handle pagination when listing tools with RUBE_SEARCH_TOOLS and fetch all available tool options.

Frequently Asked Questions

Add this skill to your agents