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

SKILL

docupost-automation

Name: docupost-automation
Author: Composio

Automate Docupost document and delivery workflows via Rube MCP with schema-first tool discovery.

Stars

★ 67,807

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

The material itself is a prompt-style document and does not declare local code execution, file access, or direct API key handling. However, it is designed to connect to remote Rube MCP/Composio services and operate Docupost workflows, so it warrants moderate caution rather than high risk.

CredentialsCaution

The material says there are no API keys, but it requires an active Docupost connection via `RUBE_MANAGE_CONNECTIONS` and asks the user to follow an auth link. This implies third-party account authorization or session credentials are involved; no explicit credential abuse is shown, but the authorization scope should be reviewed.

Network egressCaution

The README explicitly instructs adding the remote MCP endpoint `https://rube.app/mcp` and using Composio/Rube to invoke Docupost-related tools. User requests, tool arguments, and workflow context will likely be sent to these declared external services. The endpoint is identified, so this is normal egress rather than suspicious exfiltration, but it still merits caution.

Code executionLow risk

The system flags this as prompt-only, and the material only describes a tool-calling workflow. It does not state that local executables, scripts, or elevated system privileges are required; based on the provided material, no local code execution surface is apparent.

Data accessCaution

The document does not declare local file or system data access, but it performs 'Docupost operations' through remote tools. The effective data scope depends on the connected Docupost account and the discovered tool schemas, so there is a normal business-data access surface that should be constrained by least privilege.

Supply chainLow risk

The source is an open GitHub repository with strong community adoption (64.7k stars), which is a meaningful risk-reducing signal. The material itself is auditable and does not show obfuscated install scripts, suspicious dependencies, or misleading high-risk instructions. The missing license declaration and unknown maintenance status do not by themselves justify a high-risk rating.

Recommendations

Before connecting to `rube.app/mcp`, confirm what context and data your client will send to the MCP service.
When authorizing Docupost, review the OAuth/connection scopes and grant only the permissions actually needed.
Inspect the schemas returned by `RUBE_SEARCH_TOOLS` before execution to avoid sending unnecessary sensitive fields to remote tools.
Validate the workflow with a test or low-sensitivity account before using it with production business data.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Docupost Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/docupost

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["docupost"]
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 Docupost-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `docupost`
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 PostGrid tasks through Rube MCP for faster mailing workflows.

ComposioGet→

$ loading_