How do I ensure I always have current tool schemas?

Always run RUBE_SEARCH_TOOLS before executing any tool to fetch up-to-date tool slugs and input schemas.

What if my connection isn't ACTIVE?

Use RUBE_MANAGE_CONNECTIONS to check the status, and follow the returned auth link to complete setup until ACTIVE appears.

Is memory required for tool execution?

Yes. Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if it’s an empty object, to meet the required schema.

docugenerate-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

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

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/docugenerate-automation/SKILL.md

View on GitHub

Overview

Automate Docugenerate operations through Composio's Docugenerate toolkit via Rube MCP. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS and validating connections before execution, ensuring up-to-date inputs.

How This Skill Works

The workflow starts by confirming RUBE_SEARCH_TOOLS is available, then establishing a docugenerate connection with RUBE_MANAGE_CONNECTIONS and ensuring ACTIVE status. Next, discover tools and their current schemas via RUBE_SEARCH_TOOLS, and finally execute a chosen tool through RUBE_MULTI_EXECUTE_TOOL using the provided memory and session_id.

When to Use It

Automating recurring Docugenerate workflows where you need up-to-date tool schemas before each run.
When tool schemas change and hardcoding tool slugs or arguments could break workflows.
Before performing a workflow that benefits from session reuse or requires new session IDs.
To verify an ACTIVE connection to the Docugenerate toolkit before executing any tools.
For bulk or batch Docugenerate operations that leverage multi-tool execution and tool discovery.

Quick Start

Step 1: Ensure Rube MCP is connected and RUBE_SEARCH_TOOLS responds.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit 'docugenerate' and verify ACTIVE status.
Step 3: Discover tools with RUBE_SEARCH_TOOLS and execute a chosen tool via RUBE_MULTI_EXECUTE_TOOL using the discovered schema.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas and avoid stale inputs.
Never hardcode tool slugs or arguments; rely on discovered schemas from RUBE_SEARCH_TOOLS.
Check that RUBE_MANAGE_CONNECTIONS reports ACTIVE before running tools.
Include the memory parameter in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
Reuse session IDs within a single workflow but generate new ones for separate workflows and manage pagination when fetching tool lists.

Example Use Cases

Automate monthly Docugenerate report generation by discovering the latest tool slugs and executing a prepared workflow.
Update templates and fields automatically when tool schemas refresh via RUBE_SEARCH_TOOLS.
Validate and establish the docugenerate connection, then run a sequence of tools for a client deliverable.
Run a multi-tool Docugenerate pipeline to assemble a document and fetch outputs in one session.
Bulk generate documents using RUBE_REMOTE_WORKBENCH with run_composio_tool() after schema discovery.

Frequently Asked Questions

Add this skill to your agents