What is Rube MCP used for in this skill?

Rube MCP orchestrates tool discovery, connection management and tool execution for Dropbox Sign tasks, ensuring you always use current schemas.

Why must I always call RUBE_SEARCH_TOOLS first?

Tool schemas change; fetching current tool slugs and input fields prevents breakages from hardcoded values.

What if the connection status isn't ACTIVE?

Follow the auth flow from RUBE_MANAGE_CONNECTIONS, wait for ACTIVE, then proceed to discovery and execution.

dropbox-sign-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Dropbox Sign Automation via Rube MCP

Automate Dropbox Sign operations through Composio's Dropbox Sign toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/dropbox_sign

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["dropbox_sign"]
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 Dropbox Sign-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `dropbox_sign`
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/dropbox-sign-automation/SKILL.md

View on GitHub

Overview

This skill automates Dropbox Sign operations through Composio's Rube MCP toolkit. It relies on live tool schemas fetched with RUBE_SEARCH_TOOLS and requires an active Dropbox Sign connection managed by RUBE_MANAGE_CONNECTIONS. By always discovering current tool slugs and input schemas, it prevents breakage from schema drift.

How This Skill Works

Begin by discovering available Dropbox Sign tools with RUBE_SEARCH_TOOLS to obtain current tool slugs and input schemas. Then verify the Dropbox Sign connection is ACTIVE via RUBE_MANAGE_CONNECTIONS and select a tool slug. Finally, execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, supplying memory and a session_id, which enables multi-step workflows while using the latest schema.

When to Use It

Setting up a new Dropbox Sign workflow from scratch and needing current tool schemas
Before executing any workflow, verify the RUBE_SEARCH_TOOLS results and that the Dropbox Sign connection is ACTIVE
Discovering tools for a specific use case such as sending a contract, NDA, or policy update
Reusing a session ID across multiple steps of a signing workflow
Performing bulk Dropbox Sign operations via RUBE_MULTI_EXECUTE_TOOL or RUBE_REMOTE_WORKBENCH

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 activate the Dropbox Sign connection via RUBE_MANAGE_CONNECTIONS with toolkit 'dropbox_sign' (complete auth if prompted)
Step 3: Use RUBE_SEARCH_TOOLS to discover a tool, then run RUBE_MULTI_EXECUTE_TOOL with tool_slug, memory, and session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas
Do not hardcode tool slugs or arguments; rely on the returned schema
Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs for related tasks and watch for pagination tokens

Example Use Cases

Onboard a vendor by discovering the appropriate tool slug and sending an initial contract for signature
Batch-send multiple NDAs to different recipients in a single session
Push an updated policy to employees by discovering the signing tool and issuing the signature request
Audit tool schemas by fetching them with RUBE_GET_TOOL_SCHEMAS and validating input fields
Migrate a workflow away from hardcoded slugs to dynamic discovery to prevent breakage

Frequently Asked Questions

Add this skill to your agents