Docupilot Automation
This skill automates Docupilot operations using Composio's Docupilot toolkit via Rube MCP. It's designed for users who need to streamline document generation...
Install
npx promptshop add docupilot-automationDetails
What This Skill Does
This skill automates Docupilot operations using Composio's Docupilot toolkit via Rube MCP. It's designed for users who need to streamline document generation and management workflows. The skill ensures proper setup, tool discovery, and execution while avoiding common pitfalls.
When to Use
Key Features
Automates Docupilot via Rube MCP. Uses RUBE_SEARCH_TOOLS for tool discovery. Manages connections via RUBE_MANAGE_CONNECTIONS. Executes tools using RUBE_MULTI_EXECUTE_TOOL. Provides setup instructions for Rube MCP. Offers guidance on avoiding common pitfalls.
Manual Installation
- Manual installation
- View Full Skill Content
- The complete markdown content that gets installed
- 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
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", }] memory: {} session_id: "your_session_id"
Known Pitfalls
Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools 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
- 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
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", }] memory: {} session_id: "your_session_id"
Known Pitfalls
Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools 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 |