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

SKILL

docsumo-automation

Name: docsumo-automation
Author: Composio

Automate Docsumo document extraction and processing tasks 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 is essentially a prompt-style usage guide for Rube MCP/Composio, with no direct evidence of local code execution, embedded secrets, or explicit local file access. The main security consideration is that it directs users to connect a third-party hosted MCP service and a Docsumo account, so the overall posture is low-to-moderate risk with mostly caution-level findings.

CredentialsCaution

The material states the skill itself requires no environment variables or API keys, but actual use requires an active Docsumo connection via RUBE_MANAGE_CONNECTIONS and an authorization-link flow, implying third-party account tokens/session authorization are involved. There is no evidence the skill itself stores credentials, but credentials are handled by the external MCP/connection system.

Network egressCaution

The README explicitly instructs adding the remote MCP endpoint https://rube.app/mcp and performing actions through Composio's Docsumo toolkit. This means task inputs, session information, and potentially Docsumo business data may be sent to external services relevant to the stated function. The endpoint usage appears aligned with the declared purpose, with no clear signs of unrelated or covert exfiltration.

Code executionLow risk

The system marks this as prompt-only, and the material mainly describes a tool-calling workflow. There is no indication it asks to run local scripts, install local binaries, or request additional system privileges. Its capabilities depend on external MCP tools rather than the skill directly executing code.

Data accessCaution

No local filesystem read/write is described, but the skill drives queries and executions against the connected Docsumo toolkit and reuses session/memory parameters, so its access scope is mainly the remote business data the user authorizes to Docsumo/Composio/Rube. The material does not show requests for local data permissions beyond its stated purpose.

Supply chainCaution

Positive signals include a GitHub source, visible open-source repository, and high community adoption (64.7k stars), which materially reduce supply-chain risk. However, the license is unspecified, maintenance status is unknown, and actual operation depends on third-party hosted rube.app/composio services whose backends are not fully auditable from the provided material, so caution is appropriate rather than risk.

Recommendations

Before connecting to https://rube.app/mcp, verify its privacy policy, data retention practices, and the scope of Docsumo OAuth/connection permissions.
Connect only a least-privilege Docsumo account or a test environment to avoid exposing unnecessary production data to the MCP flow.
Review the actual schemas and tool list returned by RUBE_SEARCH_TOOLS before execution to confirm that no sensitive fields are being sent.
Prefer pinned trusted sources/versions and monitor the repository plus Rube/Composio service change and maintenance notices.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Docsumo Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/docsumo

Prerequisites

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

Step 2: Check Connection

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