home / skills / composiohq / awesome-claude-skills / dpd2-automation

dpd2-automation skill

/dpd2-automation

This skill automates Dpd2 tasks via Composio's Rube MCP, discovering current tool schemas first to ensure accurate executions.

npx playbooks add skill composiohq/awesome-claude-skills --skill dpd2-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
2.8 KB
---
name: dpd2-automation
description: "Automate Dpd2 tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Dpd2 Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/dpd2](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `dpd2`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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](https://composio.dev)*

Overview

This skill automates Dpd2 tasks by orchestrating Composio’s Dpd2 toolkit through a Rube MCP server. It provides a clear discovery-first workflow to find current tool schemas, verify connections, and execute Dpd2 operations reliably. Built around RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, and RUBE_MULTI_EXECUTE_TOOL calls, it enforces schema compliance and session handling.

How this skill works

First, it queries RUBE_SEARCH_TOOLS to discover available Dpd2 tool slugs, input schemas, and execution plans. Next, it verifies or creates an active Dpd2 connection using RUBE_MANAGE_CONNECTIONS. Finally, it executes one or more toolkit calls with RUBE_MULTI_EXECUTE_TOOL (including memory and session_id), handling pagination and reusing sessions when appropriate.

When to use it

  • Automating repetitive Dpd2 operations that require toolkit API calls
  • Building workflows that must adapt to changing tool schemas at runtime
  • Running bulk or remote Dpd2 jobs via Composio from an agent
  • Orchestrating multi-step Dpd2 processes that need reliable connection checks
  • Integrating Dpd2 functionality into broader agent-driven automation

Best practices

  • Always call RUBE_SEARCH_TOOLS first; do not hardcode tool slugs or argument shapes
  • Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
  • Pass exact field names and types from the returned schema to avoid errors
  • Always include a memory object (even if empty) in RUBE_MULTI_EXECUTE_TOOL calls
  • Reuse session IDs for related steps and generate new sessions for independent workflows
  • Check responses for pagination tokens and iterate until all results are fetched

Example use cases

  • Discover and run a Dpd2 data import tool after confirming connection status
  • Execute a batch operation across many items using RUBE_REMOTE_WORKBENCH run_composio_tool()
  • Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS before building a dynamic UI
  • Create a multi-step workflow that checks connection, retrieves tools, and executes dependent tasks
  • Automate scheduled Dpd2 maintenance tasks while handling schema changes gracefully

FAQ

Do I need API keys to use Rube MCP?

No. Add https://rube.app/mcp as an MCP server in your client configuration; no additional API keys are required.

What if a tool schema changes mid-workflow?

You must call RUBE_SEARCH_TOOLS again to get the updated schema and adapt arguments; never assume schemas remain static.