Why must I always search tools first?

Tool schemas change over time. RUBE_SEARCH_TOOLS fetches current tool slugs and required arguments; never hardcode them.

How should I manage sessions during a workflow?

Reuse the same session_id within a workflow for continuity; generate a new session_id for separate workflows and include it in tool calls. Also confirm pagination tokens if present.

docupost-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/docupost-automation --openclaw

Files (1)

SKILL.md

2.9 KB

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

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/docupost-automation/SKILL.mdView on GitHub

Overview

Automate Docupost operations using Composio's Docupost toolkit through Rube MCP. This approach requires an active Rube MCP connection and an active Docupost connection, and you must always search for current tool schemas before running workflows to ensure compatibility and correctness.

How This Skill Works

Discover available Docupost tools with RUBE_SEARCH_TOOLS using the use_case Docupost operations. Verify the Docupost connection status with RUBE_MANAGE_CONNECTIONS and then execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, providing the schema-compatible arguments and memory payload. Never hardcode tool slugs or arguments; tool schemas can change and should be refreshed before each run.

When to Use It

Initialize a Docupost automation by discovering current tools and their schemas before running any workflow.
Ensure the Docupost connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before executing tools.
Execute a discovered tool with the correct arguments using RUBE_MULTI_EXECUTE_TOOL in a single session.
Reuse a session_id within a multi-step Docupost workflow to maintain context and continuity.
Re-discover tool schemas with RUBE_SEARCH_TOOLS before updates or after changes to tool definitions to avoid failures.

Quick Start

Step 1: RUBE_SEARCH_TOOLS with use_case Docupost operations to fetch current tool schemas.
Step 2: RUBE_MANAGE_CONNECTIONS with toolkits: [docupost] and check that the session is ACTIVE.
Step 3: RUBE_MULTI_EXECUTE_TOOL with the chosen tool_slug and schema-compliant arguments, including memory: {} and your session_id.

Best Practices

Always run RUBE_SEARCH_TOOLS first to fetch current tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools.
Use exact field names and types from the search results; avoid hardcoding.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Reuse session IDs within a workflow and generate new IDs for new workflows; watch for pagination tokens

Example Use Cases

Discover Tools promise, connect Docupost, and execute a single Docupost task with proper arguments.
Batch processing: discover tools and run multiple operations via RUBE_MULTI_EXECUTE_TOOL in sequence.
Establish a new Docupost connection and perform an initial test execution using a sample tool.
Handle a tool schema change by re-discovering tools before running a Docupost task.
Process a long-running workflow with session reuse and pagination-aware tool discovery.

Frequently Asked Questions

Add this skill to your agents