Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts Docugenerate Automation via Rube MCP

agent tool_use skill risk: high

Docugenerate Automation via Rube MCP

Instructs on automating Docugenerate operations through Composio's Docugenerate toolkit via Rube MCP, including prerequisites, setup steps, tool discovery with RUBE_SEARCH_TOOLS, c…

  • Policy sensitive
  • Human review
  • External action: high

SKILL 1 file

SKILL.md
---
name: docugenerate-automation
description: "Automate Docugenerate tasks via Rube MCP (Composio). Always search tools first for current schemas."
---
# Docugenerate Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/docugenerate](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `docugenerate`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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](https://composio.dev)*

REQUIRED CONTEXT

  • RUBE_SEARCH_TOOLS availability
  • active docugenerate connection via RUBE_MANAGE_CONNECTIONS

OPTIONAL CONTEXT

  • existing session_id

TOOLS REQUIRED

  • RUBE_SEARCH_TOOLS
  • RUBE_MANAGE_CONNECTIONS
  • RUBE_MULTI_EXECUTE_TOOL
  • RUBE_REMOTE_WORKBENCH
  • RUBE_GET_TOOL_SCHEMAS

ROLES & RULES

  1. Always search tools first for current schemas.
  2. Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
  3. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
  4. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `docugenerate`
  5. Confirm connection status shows ACTIVE before running any workflows
  6. Always discover available tools before executing workflows
  7. Always search first
  8. Check connection
  9. Use exact field names and types from the search results
  10. Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty
  11. Reuse session IDs within a workflow
  12. Generate new ones for new workflows
  13. Check responses for pagination tokens and continue fetching until complete

EXPECTED OUTPUT

Format
markdown
Schema
table · Operation, Approach
Constraints
  • always search tools first
  • verify active connection before execution
  • use exact schemas from search results

SUCCESS CRITERIA

  • Search for current tool schemas before any execution
  • Verify ACTIVE Docugenerate connection
  • Use schema-compliant arguments from search results
  • Reuse session IDs within a workflow

FAILURE MODES

  • Hardcoding tool slugs or arguments without calling RUBE_SEARCH_TOOLS
  • Executing tools before connection is ACTIVE
  • Omitting the memory parameter in RUBE_MULTI_EXECUTE_TOOL
  • Failing to handle pagination

EXAMPLES

Includes multiple example tool invocation blocks for RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS and RUBE_MULTI_EXECUTE_TOOL plus a quick-reference table.

CAVEATS

Dependencies
  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Docugenerate connection via RUBE_MANAGE_CONNECTIONS
Missing context
  • Target audience / technical background assumed
  • Concrete example task with full end-to-end call sequence
  • Error handling or retry strategy
Ambiguities
  • Example in Tool Discovery uses `generate_id: true` while Step 1 uses `id: "existing_session_id"` without clarifying when to generate vs reuse.
  • Does not specify desired output length or format for workflow results.

QUALITY

OVERALL
0.79
CLARITY
0.85
SPECIFICITY
0.78
REUSABILITY
0.72
COMPLETENESS
0.80

IMPROVEMENT SUGGESTIONS

  • Replace inline code blocks with explicit placeholders such as {{USE_CASE}} and {{SESSION_ID}} to improve reusability.
  • Add a minimal complete example showing one full successful workflow from search to execution.

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR AGENT