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

SKILL

docugenerate-automation

Name: docugenerate-automation
Author: Composio

Automate Docugenerate document generation workflows through Rube MCP for faster operations.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill appears to be an open-source, prompt-only wrapper with no declared local secrets, code execution, or direct local data access, so overall risk is low. However, it is designed to connect to remote Rube MCP/Composio services and manage downstream Docugenerate integrations, so users should pay attention to network egress and third-party authorization boundaries.

CredentialsCaution

The material claims 'no API keys needed,' but it requires establishing a Docugenerate connection via RUBE_MANAGE_CONNECTIONS and following an auth link when inactive, indicating third-party account authorization/tokens are still involved, even if not locally declared by this skill.

Network egressCaution

The README explicitly instructs adding the remote MCP endpoint https://rube.app/mcp and using Composio/Rube to search tools, manage connections, and execute operations; this means task inputs, session IDs, tool arguments, and related business data may be sent to the stated external service. The endpoint is explicit and relevant to the stated function, with no additional unknown egress targets shown.

Code executionLow risk

The system marks it as prompt-only, and the provided content is mainly procedural guidance and call patterns, with no bundled scripts, install commands, or local execution capability shown. While it mentions remote tool execution, the material does not indicate direct local process spawning or code execution on the user's machine.

Data accessLow risk

There is no declared access to local files, system resources, or device data; data access is primarily framed as operating on Docugenerate-related resources through the remote MCP. Based on the material, it does not request local data permissions beyond its stated function.

Supply chainLow risk

The source is an open GitHub repository with very strong community adoption (64.9k stars), which are clear risk-reducing factors. The material shows no closed-source binary, suspicious installation steps, or obviously distorted provenance; the main gaps are an undeclared license and unknown maintenance status, which should be verified before use.

Recommendations

Use it only if you are comfortable sending task data to rube.app / Composio-related services, and avoid submitting unnecessary sensitive content.
Before completing Docugenerate authorization, verify the auth page domain, requested scopes, and account identity.
Prefer testing in a low-sensitivity or sandbox environment to validate the real tool-call scope and data flows.
Check repository maintenance activity, license status, and related documentation before adoption to confirm long-term auditability.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Docugenerate Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/docugenerate

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["docugenerate"]
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 Docugenerate-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `docugenerate`
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 Docsumo document extraction and processing tasks through Rube MCP.

ComposioGet→

$ loading_