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

SKILL

documint-automation

Name: documint-automation
Author: Composio

Automate Documint document generation and processing tasks through Rube MCP.

Stars

★ 67,807

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This appears to be an open-source prompt-style wrapper with strong community adoption signals. However, it relies on external Rube MCP/Composio and a Documint connection, while the materials do not fully describe data flows, authorization scope, or maintenance status, so the overall posture is low-to-moderate risk with caution.

CredentialsCaution

The material says the skill itself needs no API key, but it requires an active Documint connection via `RUBE_MANAGE_CONNECTIONS` and an external auth flow, indicating third-party account authorization in practice. The scope requested, token storage, and least-privilege details are not described.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and executing operations through Composio/Documint tools, so user requests and related business data are likely transmitted through these stated external services. The documentation does not fully specify what data leaves the client or its boundaries.

Code executionLow risk

The system flags it as `prompt-only`, and the material does not describe local code execution, process spawning, or requests for system-level execution permissions. Based on the available facts, it behaves more like workflow guidance than a locally executable component.

Data accessCaution

This skill targets Documint operations and performs tasks through remote tools such as `RUBE_MULTI_EXECUTE_TOOL` and `RUBE_REMOTE_WORKBENCH`, implying access to data the user authorizes in Documint. However, the documentation does not define the specific read/write scope, access limits, or safeguards against overbroad authorization.

Supply chainLow risk

The source is an open GitHub repository with high community adoption (~64.7k stars), which is a strong risk-reducing signal. No closed-source distribution, suspicious install script, or clear deceptive content is evident here. Still, the missing license declaration and unknown maintenance status should be reviewed further.

Recommendations

Before connecting, verify the exact permission scopes requested by the Rube/Composio and Documint authorization flow, and grant only the minimum needed.
Avoid sending unnecessary sensitive documents or personal data through this workflow, and review the external services' data retention and logging policies.
Inspect the actual skill contents, update history, and issues in the linked repository before production use, especially to confirm it is still maintained.
For enterprise use, monitor or proxy outbound traffic to `rube.app` and related services to audit data transmission.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Documint Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/documint

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["documint"]
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 Documint-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `documint`
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

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

ComposioGet→

$ loading_