What are the prerequisites?

RUBE_SEARCH_TOOLS must be available, RUBE_MANAGE_CONNECTIONS configured for the docupilot toolkit, and an active Docupilot connection via Rube MCP; always search tools first.

Do I need API keys to use this skill?

No API keys are required. You connect through the provided MCP endpoint at rube.app/mcp.

How do I handle changes in tool schemas?

Always call RUBE_SEARCH_TOOLS prior to execution to obtain current tool slugs and input fields; do not hardcode tool details.

docupilot-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Docupilot Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/docupilot

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Docupilot tasks using Composio's Docupilot toolkit via Rube MCP. The skill emphasizes discovering tool schemas first with RUBE_SEARCH_TOOLS, then managing connections and executing tools with RUBE_MULTI_EXECUTE_TOOL. This keeps Docupilot workflows resilient to schema changes.

How This Skill Works

First discover available tools with RUBE_SEARCH_TOOLS to get current tool slugs and input schemas. Then verify the Docupilot connection via RUBE_MANAGE_CONNECTIONS and ensure it is ACTIVE. Finally execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, including memory and the proper session_id, and reuse sessions for related tasks.

When to Use It

Automate routine Docupilot document creation across templates, fills, and exports
Run batch Docupilot operations in a single workflow to process multiple documents
Integrate Docupilot tasks into larger Composio workflows via Rube MCP
When tool schemas change frequently and you need up to date input fields
When you want to verify ACTIVE connections before executing any Docupilot tools

Quick Start

Step 1: RUBE_SEARCH_TOOLS with a Docupilot use case to discover tools
Step 2: RUBE_MANAGE_CONNECTIONS for the docupilot toolkit and ensure ACTIVE
Step 3: RUBE_MULTI_EXECUTE_TOOL with the chosen tool slug, proper arguments, memory, and a session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool schemas
Check that RUBE_MANAGE_CONNECTIONS reports ACTIVE before execution
Use exact field names and types from the search results and avoid hardcoding slugs
Include memory in RUBE_MULTI_EXECUTE_TOOL even if empty
Reuse session IDs within a workflow and fetch pagination tokens if present

Example Use Cases

Create a Docupilot document from a discovered tool slug using memory to populate fields
Batch run multiple Docupilot templates in one session with RUBE_MULTI_EXECUTE_TOOL
Discover, connect, and execute a Docupilot task for a monthly report
Update template data by supplying exact schema fields returned by RUBE_SEARCH_TOOLS
Handle tool listing pagination and continue executing tools until complete

Frequently Asked Questions

Add this skill to your agents