What is pdf-co-automation?

It is a workflow pattern that automates PDF co operations using Composio's pdf_co toolkit via the Rube MCP, with best practices like discovering current schemas before execution.

What prerequisites are required?

Rube MCP must be connected; RUBE_SEARCH_TOOLS must be available; a pdf_co connection must be ACTIVE via RUBE_MANAGE_CONNECTIONS; and you should always search tool schemas before use.

How do I perform a typical run?

Step 1: Discover tools with RUBE_SEARCH_TOOLS. Step 2: Ensure the pdf_co connection is ACTIVE with RUBE_MANAGE_CONNECTIONS. Step 3: Execute the tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug, appropriate arguments, memory, and session_id.

pdf-co-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

PDF co Automation via Rube MCP

Automate PDF co operations through Composio's PDF co toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/pdf_co

Prerequisites

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

Step 2: Check Connection

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

Overview

PDF co automation uses Composio's PDF co toolkit via Rube MCP to automate PDF co operations. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS, establishing an ACTIVE pdf_co connection with RUBE_MANAGE_CONNECTIONS, and then executing the discovered tools. This approach avoids hardcoding tool slugs and adapts to changing schemas.

How This Skill Works

Begin by running RUBE_SEARCH_TOOLS to fetch available PDF co tool slugs and their input schemas. Then verify the pdf_co connection is ACTIVE via RUBE_MANAGE_CONNECTIONS. Finally, execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and a memory object, reusing session IDs as appropriate.

When to Use It

When you need to automate repetitive PDF co tasks (e.g., extraction, conversion, or manipulation) using available tools.
When tool schemas change, requiring a fresh discovery instead of hardcoding slugs or arguments.
When you must ensure an ACTIVE pdf_co connection before running any workflow steps.
When you want to reuse a session ID across multiple steps in a single workflow.
When performing bulk or batch PDF operations that can leverage remote execution benches.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server and verify RUBE_SEARCH_TOOLS responds.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["pdf_co"] and ensure status is ACTIVE.
Step 3: Discover tools with RUBE_SEARCH_TOOLS, then execute a chosen tool via RUBE_MULTI_EXECUTE_TOOL using the memory object and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas before any execution.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status for the pdf_co toolkit prior to running tools.
Use exact field names and types from the discovered tool schemas; do not hardcode values.
Include a memory object in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
Reuse session IDs within a workflow and generate new ones only for separate workflows.

Example Use Cases

Discover a PDF co tool for data extraction and execute it with the correct input schema to automate invoice data capture.
Check that the pdf_co connection is ACTIVE before running a sequence of PDF co tools in a multi-step workflow.
Re-run RUBE_SEARCH_TOOLS after a tool update to avoid broken automation due to schema changes.
Batch several PDF co tasks using RUBE_REMOTE_WORKBENCH and run_composio_tool for bulk processing.
Inspect full tool schemas with RUBE_GET_TOOL_SCHEMAS to compare schemaRef and plan compatible executions.

Frequently Asked Questions

Add this skill to your agents