$ ~/registry/skill/composiohq-composio-skills-pdf-api-io-automation

SKILL

pdf-api-io-automation

Name: pdf-api-io-automation
Author: Composio

Automate PDF API IO workflows via Rube MCP using current tool schemas first.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

This skill appears to be a prompt-style wrapper for driving the Rube MCP/Composio toolchain, and its open-source/community signals lower overall risk. The main caution is that it directs users to connect to a remote MCP and external PDF tooling, so real data egress, authorization scope, and processing boundaries depend on those downstream services.

CredentialsCaution

The material says the skill itself needs no API keys, but actual use requires activating a `pdf_api_io` connection via `RUBE_MANAGE_CONNECTIONS` and possibly completing external authorization through a returned auth link. So while the skill does not directly collect secrets, there is still the usual caution around third-party connection tokens/OAuth scopes and potential over-granting.

Network egressCaution

The README explicitly instructs users to add the remote MCP endpoint `https://rube.app/mcp` and execute actions through Composio/PDF API IO tooling. This means PDF-related requests, and possibly document content, may be processed by remote services. Such remote calls are normal for this type of tool, but the material does not detail data flows, retention, or downstream processing boundaries.

Code executionLow risk

Based on the known checks, this is a prompt-only skill. The material does not show local script installation, shell execution, background process spawning, or system-level code execution by the skill itself; it mainly instructs how to call existing MCP tools.

Data accessCaution

The skill is meant to automate PDF API IO operations, which typically implies sending PDFs or related content to remote tools for processing. The material does not claim direct local filesystem read/write access, nor does it show access beyond what a PDF workflow would normally need. However, if users provide sensitive documents, the effective visibility extends to the Rube/Composio/`pdf_api_io` service chain.

Supply chainLow risk

The source is an open GitHub repository, and the system provides positive signals of being open-source with strong community adoption (64.7k stars). In the provided material, there is no sign of a closed-source dropper, suspicious installer, or obvious prompt-injection-style red flag. The missing license declaration and unknown maintenance status are worth noting, but the current evidence still supports a low-risk rating.

Recommendations

Only connect to `rube.app/mcp` when there is a real business need, and review Composio/PDF API IO privacy, retention, and authorization details first.
Avoid uploading highly sensitive PDFs; if necessary, redact them first and verify whether documents are stored remotely or included in logs.
Apply least-privilege principles when authorizing the `pdf_api_io` connection, and periodically review/revoke unused connections.
Before production use, test with non-sensitive documents to verify which tools are actually invoked and what services receive the data.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "pdf-api-io-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/pdf-api-io-automation/SKILL.md
2. Save it as ~/.claude/skills/pdf-api-io-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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

Automate Craftmypdf PDF generation and document workflows through Rube MCP.

ComposioGet→

$ loading_