What is required to start Docmosis automation?

Rube MCP must be connected, RUBE_SEARCH_TOOLS must be available, and an active Docmosis connection must exist (RUBE_MANAGE_CONNECTIONS with toolkit 'docmosis').

Do tool slugs and input fields change?

Yes—always call RUBE_SEARCH_TOOLS to fetch current schemas before executing tools. Do not hardcode slugs or fields.

Is API key needed for MCP?

No API keys are needed; you only configure the MCP endpoint (e.g., https://rube.app/mcp) in your client.

docmosis-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Docmosis Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/docmosis

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["docmosis"]
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 Docmosis-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `docmosis`
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/docmosis-automation/SKILL.mdView on GitHub

Overview

Automate Docmosis operations through Composio's Docmosis toolkit via Rube MCP. The workflow relies on live tool schemas fetched with RUBE_SEARCH_TOOLS and requires an active Docmosis connection managed via RUBE_MANAGE_CONNECTIONS. Setup involves adding the MCP server, verifying connectivity, and then running Docmosis tasks with RUBE_MULTI_EXECUTE_TOOL.

How This Skill Works

Start by discovering tools with RUBE_SEARCH_TOOLS for your Docmosis use case, then verify and activate the Docmosis connection with RUBE_MANAGE_CONNECTIONS. Once ready, execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, providing the memory object and a session_id, and ensure you supply exact field names from the discovered input schema.

When to Use It

Automating batch Docmosis document generation tasks from a data source
Validating and running tools only after confirming current schemas via RUBE_SEARCH_TOOLS
Maintaining and reusing an active Docmosis connection through RUBE_MANAGE_CONNECTIONS
Executing multiple Docmosis operations in a single workflow using RUBE_MULTI_EXECUTE_TOOL
Handling large or paginated results by iterating tool discovery and execution

Quick Start

Step 1: Discover tools with RUBE_SEARCH_TOOLS for Docmosis tasks
Step 2: Ensure the Docmosis connection is ACTIVE with RUBE_MANAGE_CONNECTIONS
Step 3: Execute a tool via RUBE_MULTI_EXECUTE_TOOL using the discovered slug and memory, with a valid session_id

Best Practices

Always call RUBE_SEARCH_TOOLS before every run to get current tool slugs and input fields
Ensure RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing any tools
Include the memory parameter in RUBE_MULTI_EXECUTE_TOOL, even if empty
Reuse session_id within a workflow to enable smooth step-to-step execution
Do not hardcode tool slugs or schema fields; rely on the live tool schemas

Example Use Cases

Generate a batch of PDFs from a customer dataset by using a discovered Docmosis tool slug
Validate tool schemas with RUBE_SEARCH_TOOLS before integrating into automated pipelines
Establish and maintain an active Docmosis connection via RUBE_MANAGE_CONNECTIONS for uninterrupted runs
Process multiple documents in a sequence by reusing a single session_id across steps
Bulk-run multiple Docmosis tools in one workflow with RUBE_MULTI_EXECUTE_TOOL

Frequently Asked Questions

Add this skill to your agents