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

SKILL

docuseal-automation

Name: docuseal-automation
Author: Composio

Automate Docuseal signing, templates, and document workflows through Rube MCP.

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/template rather than executable local code, with no declared local secrets or direct file access. The main security consideration is its reliance on external Rube MCP/Composio and Docuseal connections for remote actions, so the overall posture is low-to-moderate risk with attention needed for external authorization and data egress boundaries.

CredentialsCaution

The material says the skill itself requires no keys, but actual use depends on establishing a Docuseal connection via RUBE_MANAGE_CONNECTIONS and completing an external auth flow, which likely grants Docuseal access tokens to the Rube/Composio connection layer. The docs do not describe token storage, scope, or revocation, creating a normal third-party authorization exposure, though no explicit red flag is shown.

Network egressCaution

The README explicitly requires adding `https://rube.app/mcp` as an MCP server and using Composio's Docuseal toolkit for operations. This means user requests, tool discovery, session information, and some Docuseal business data may be sent to declared external services. The egress targets are functionally related and disclosed, but this is still a data-outbound scenario that warrants caution.

Code executionLow risk

The system flags this as prompt-only, and the material does not show local script installation, shell execution, process spawning, or system permission requests. Its purpose is to guide calls to existing MCP tools rather than execute code locally, so local code-execution risk is low.

Data accessCaution

There is no indication of local file or host resource access, but once connected it can perform document-signing-related remote operations and access business data within the linked Docuseal account through sessions and tool calls. This scope appears related to the stated function, with no clear evidence of overreach, but the connection should still be constrained by least privilege.

Supply chainLow risk

The source is an open GitHub repository with strong community trust (64.7k stars), which materially lowers supply-chain risk; the material also looks like a skill description rather than an executable binary. Caveats remain: no declared license, unknown maintenance status, and the server-side behavior of Rube/Composio cannot be fully audited from this README alone, but based on current evidence the supply-chain risk is still on the low side.

Recommendations

Before connecting Docuseal, verify the OAuth/authorization publisher, requested scopes, and token revocation path.
Enable this skill only when needed, and validate it with a least-privileged Docuseal account or test environment.
Do not send unnecessary sensitive document content, personal data, or full contracts in tool discovery or execution arguments.
Review the privacy policy, log retention, and data-handling terms of Rube/Composio and Docuseal first.

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 "docuseal-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/docuseal-automation/SKILL.md
2. Save it as ~/.claude/skills/docuseal-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Docuseal Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/docuseal

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["docuseal"]
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 Docuseal-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `docuseal`
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 Eversign document signing tasks and workflow actions through Rube MCP.

ComposioGet→

$ loading_