pdf-api-io-automation
Lets your agent interact with the PDF API IO to process PDFs. It's useful for automating the creation or manipulation of documents. This speeds up working with PDF files.
What it does
This tool helps automate tasks with PDF files using a special connection. It allows you to interact with PDF documents programmatically, like extracting information or manipulating content.
When to use it
- ✓When you need to extract text from multiple PDFs at once.
- ✓When trying to convert a PDF to another format.
- ✓To automate the organization or renaming of PDF files.
Example of what to ask your AI
“I want to extract all tables from the PDF report in CSV format.”
Want more? Open the sections below.
How to use
The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.
Skill link
Ready-to-paste message
How it works
First, the tool checks which specific PDF commands are available. Then, it connects to a service called PDF API IO and executes the requested task using the found commands.
Installation
Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.
In the terminal (Claude Code, Codex, Cursor), in your project folder:
npx skills add ComposioHQ/awesome-claude-skills --skill pdf-api-io-automationOr download just the file:
curl -L https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/pdf-api-io-automation/SKILL.md -o SKILL.mdTechnical content (original SKILL.md)
Original text by the author, straight from GitHub.
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_CONNECTIONSwith toolkitpdf_api_io - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitpdf_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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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
FAQ
Do I need to install anything?
You need to set up Rube MCP in your client, but no API keys are required. The connection to PDF API IO is handled through Rube.
How do I know what tasks PDF API IO can perform?
The tool always searches for available options before executing. You can ask it to list operations for PDFs.
What happens if the connection fails?
If the connection is not active, the tool will provide a link for you to complete the setup and authorize access.
Details
Original description by the author
Automate PDF API IO tasks via Rube MCP (Composio). Always search tools first for current schemas.
Popularity
- GitHub stars
- 77k
- Ranking position
- #1418
- License
- —
- Updated
- 9/18/2026
Comments
- …
More skills from this repository
artifacts-builder
Helps your agent build complex user interfaces. It uses modern technologies to create rich, interactive web pages.
ComposioHQ/awesome-claude-skills
brand-guidelines
Helps your agent apply official brand colors and fonts to materials. It's useful for maintaining visual identity in any piece that needs to look like the company's.
ComposioHQ/awesome-claude-skills
canvas-design
Lets your agent create original visual art in .png and .pdf. Use it when the user asks to create a poster, art, or other static design.
ComposioHQ/awesome-claude-skills
changelog-generator
Helps your agent create user-facing release notes from code commits. It transforms technical information into easy-to-understand text.
ComposioHQ/awesome-claude-skills
Similar skills
benchmark
Helps your agent measure code speed and performance. It's useful for ensuring things are fast and finding slowness issues.
affaan-m/ECC
content-hash-cache-pattern
Lets your agent use content hashes to cache file processing results. This avoids repeated processing and auto-invalidates the cache when content changes. Useful for speeding up slow tasks.
affaan-m/ECC
parallel-execution-optimizer
Makes your agent speed up complex tasks by breaking them into smaller parts and running them in parallel. It ensures everything is verified at the end.
affaan-m/ECC