$ ~/registry/skill/composiohq-composio-skills-docupilot-automation

SKILL

docupilot-automation

Name: docupilot-automation
Author: Composio

Search current schemas first, then automate Docupilot document generation workflows.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

This skill appears to be an open-source prompt/instruction wrapper with strong community trust and no direct malicious indicators. The main caveat is that it explicitly depends on third-party Rube MCP and a Docupilot connection, so real data access and egress would occur through those external services.

CredentialsCaution

The material claims 'No API keys needed', but it still requires activating a `docupilot` connection via `RUBE_MANAGE_CONNECTIONS` and following an auth link, which implies third-party account authorization/session credentials. The skill itself does not ask for local plaintext secrets, but the external connection introduces normal credential-abuse exposure.

Network egressCaution

The README explicitly instructs adding `https://rube.app/mcp` as an MCP server and executing Docupilot tools through Composio/Rube; therefore user requests, tool arguments, session data, and potentially business data are sent to external services. The material does not provide further endpoint inventory or data-minimization details.

Code executionLow risk

Per the objective checks, this is prompt-only, and the material does not describe local install scripts, shell commands, process spawning, or arbitrary code execution. Its role is mainly to instruct how to call external MCP tools.

Data accessCaution

The skill aims to 'Automate Docupilot operations' and supports tool search, connection management, bulk execution, and a remote workbench; once authorized, the external tools may access documents/templates/workflow data in the Docupilot account. The material does not define least-privilege scope or resource boundaries, so normal data-access caution is warranted.

Supply chainLow risk

The source is an open GitHub repository with high community trust (about 64.7k stars), which are strong risk-reducing signals. The visible content is mainly README/skill instructions, so supply-chain risk is relatively low. The missing license declaration and unknown maintenance status are worth noting, but not enough on their own to raise this to high risk.

Recommendations

Only connect to `rube.app/mcp` when necessary, and review its privacy policy, logging retention, and data-handling practices first.
Grant Docupilot the minimum required permissions, ideally using a test or low-sensitivity account for initial validation.
Review the exact tools and arguments returned by `RUBE_SEARCH_TOOLS` before execution to avoid sending unnecessary sensitive document content to external services.
Prefer pinned trusted revisions or snapshots of the repository, and monitor future maintenance and changes.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "docupilot-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/docupilot-automation/SKILL.md
2. Save it as ~/.claude/skills/docupilot-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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

Automate Documenso signing, templates, and status tracking through Rube MCP.

ComposioGet→

$ loading_