What is Draftable Automation via Rube MCP?

It is a workflow to automate Draftable tasks through Composio's Draftable toolkit using Rube MCP, requiring up-to-date tool schemas fetched via RUBE_SEARCH_TOOLS.

How do I keep tool schemas current?

Always call RUBE_SEARCH_TOOLS before execution to obtain current tool slugs and input schemas; do not hardcode values.

What should I do if the Draftable connection is not ACTIVE?

Use RUBE_MANAGE_CONNECTIONS to verify the status; follow the returned auth link to complete setup, then re-check until the status shows ACTIVE before running workflows.

draftable-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Draftable Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/draftable

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Draftable operations through Composio's Draftable toolkit using Rube MCP. This workflow relies on an active Rube MCP connection (RUBE_SEARCH_TOOLS) and a Draftable toolkit connection, and it emphasizes always discovering current tool schemas before execution.

How This Skill Works

Start by discovering current tool schemas with RUBE_SEARCH_TOOLS, then verify the Draftable connection with RUBE_MANAGE_CONNECTIONS. Finally, execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL, supplying the appropriate memory payload and a session_id from your workflow. Always reference up-to-date schemas and avoid hardcoding tool slugs or arguments.

When to Use It

Need to automate a Draftable task (e.g., diff or compare) across many documents using updated tool schemas.
Setting up a new Draftable workflow and ensuring tool slugs come from RUBE_SEARCH_TOOLS rather than hardcoding.
Batch-processing multiple Draftable operations in a single session with shared memory and session_id.
Validating or auditing document changes in a regulated process with automated checks.
Troubleshooting or updating workflows when tool schemas change or connections become inactive.

Quick Start

Step 1: Configure Rube MCP by adding the MCP server URL (https://rube.app/mcp) and verify RUBE_SEARCH_TOOLS responds.
Step 2: Discover available Draftable tools with RUBE_SEARCH_TOOLS for your use case and note the tool slugs and input schemas.
Step 3: Manage and verify the Draftable connection with RUBE_MANAGE_CONNECTIONS (toolkit: draftable) and execute a chosen tool with RUBE_MULTI_EXECUTE_TOOL using a session_id and memory.

Best Practices

Always run RUBE_SEARCH_TOOLS before executing to fetch up-to-date tool slugs and input schemas.
Ensure RUBE_MANAGE_CONNECTIONS shows ACTIVE before running workflows.
Use exact field names and types from the search results; do not hardcode values.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow and generate new ones for new workflows; monitor for pagination tokens in responses.

Example Use Cases

Batch-compare 100 legal PDFs to surface diffs using the latest Draftable tool slugs discovered via RUBE_SEARCH_TOOLS.
Diff policy documents across departments to ensure consistency before publication.
Automate pre-release QA by comparing draft documents against approved baselines.
Integrate Draftable checks into a CI pipeline to validate document changes on pull requests.
Schedule a nightly audit of document changes and report findings automatically.

Frequently Asked Questions

Add this skill to your agents