Do I need to configure anything before using this skill?

Yes. Add the RUBE MCP endpoint (https://rube.app/mcp) as your MCP server, then verify RUBE_SEARCH_TOOLS responds and establish an ACTIVE pdf_api_io connection.

Why is it important to search tools first?

Tool schemas change over time. Fetching current slugs and argument names with RUBE_SEARCH_TOOLS prevents mismatches and execution errors.

What if the connection status isn't ACTIVE?

Do not run tools. Follow the auth flow or returned link to activate the connection, then re-check status before proceeding.

pdf-api-io-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

PDF API IO Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/pdf_api_io

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate PDF API IO operations through Composio's PDF API IO toolkit using Rube MCP. It emphasizes discovering current tool schemas first and validating an ACTIVE connection before workflow execution.

How This Skill Works

You start by discovering available PDF API IO tools with RUBE_SEARCH_TOOLS to obtain current tool slugs and schemas. Next, you verify the connection with RUBE_MANAGE_CONNECTIONS for the pdf_api_io toolkit and ensure the status is ACTIVE. Finally, you execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, supplying the discovered slug, exact arguments, and a memory object; reuse sessions where appropriate.

When to Use It

When you need to set up a new PDF IO workflow and must discover current tool schemas before proceeding.
When you are about to run a batch of PDF IO tasks and want to ensure an ACTIVE connection first.
When performing bulk PDF operations (e.g., extract, convert, or merge) across multiple files using discovered tools.
When tool schemas change and you need to fetch fresh slugs and argument names before execution.
When reusing a workflow across steps or sessions to maintain continuity and avoid reconfiguration.

Quick Start

Step 1: Verify Rube MCP availability with RUBE_SEARCH_TOOLS to fetch current tool schemas.
Step 2: Connect to the pdf_api_io toolkit using RUBE_MANAGE_CONNECTIONS and ensure ACTIVE status.
Step 3: Execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL, supplying memory and exact arguments from the search results.

Best Practices

Always call RUBE_SEARCH_TOOLS before any execution to get the latest tool slugs and input schemas.
Check RUBE_MANAGE_CONNECTIONS status and confirm ACTIVE before executing tools.
Use exact field names and types from the search results to avoid schema mismatches.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and generate new ones only for separate workflows.

Example Use Cases

Example: Discover a PDF extraction tool via RUBE_SEARCH_TOOLS, connect with pdf_api_io, and run extraction on a batch of invoices, then parse results from memory.
Example: Find a PDF conversion tool, connect, and convert a set of PDFs to a desired format, storing outputs to a cloud location.
Example: Discover a PDF merge tool, combine multiple PDFs into a single document, and save the merged file to storage.
Example: Retrieve form-field data from PDFs using a discovery tool, and push results into a database via the same workflow.
Example: After a tool schema update, re-search tools, reconnect if needed, and re-run a previously saved workflow with new slugs.

Frequently Asked Questions

Add this skill to your agents