$ ~/registry/skill/composiohq-composio-skills-pdf-co-automation

SKILL

pdf-co-automation

Name: pdf-co-automation
Author: Composio

Automate PDF tasks like conversion, extraction, merging, and data handling.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill is essentially an open-source prompt/instruction file with no embedded secrets, scripts, or local execution logic. The main consideration is that it directs users to connect to remote Rube MCP/Composio services and handle PDF-related operations through external tools, so the overall posture is mostly low risk to caution.

CredentialsCaution

The material says no API keys are needed, but the README explicitly requires establishing a `pdf_co` connection via `RUBE_MANAGE_CONNECTIONS` and following an auth link if the connection is not active, which implies third-party credentials may be managed by Rube/Composio. The skill itself does not directly request secrets, so exposure is limited, but there is still the usual risk of over-authorizing an external connection.

Network egressCaution

The README instructs users to configure `https://rube.app/mcp` as an MCP server and perform actions through Composio/PDF co tools, meaning user requests and potentially PDF data may be processed by remote services. The endpoint is explicitly identified in the material, and there is no clear red flag of exfiltration to unrelated or unknown domains, but this external transmission still warrants caution regarding data minimization and compliance.

Code executionLow risk

Based on the provided material, this is a prompt-only skill consisting mainly of invocation order and workflow instructions, with no executable scripts, install commands, or requirement to spawn local processes. It may direct the use of MCP tools, but the skill itself does not claim direct local code execution capability.

Data accessCaution

The skill is intended to automate PDF co operations, so by function it may handle user-provided PDFs or related document content; however, the README does not define local file paths, persistence scope, or clear least-privilege boundaries. There is no obvious sign of excessive local authorization, but sending documents to external tools still requires caution based on data sensitivity.

Supply chainLow risk

The source is an open-source GitHub repository, `ComposioHQ/awesome-claude-skills`, with very high community adoption (64.7k stars), which are strong risk-reducing signals. Although the license is not stated and maintenance status is unknown, and the skill depends on the external Rube/Composio ecosystem, there is no clear sign here of a closed-source drop, spoofed origin, or other major supply-chain red flags.

Recommendations

Only connect to `rube.app/mcp` when there is a real business need, and review the exact permission scope requested by the `pdf_co` authorization flow.
Avoid uploading sensitive or regulated PDFs to this workflow; redact and minimize data first when possible.
Review the privacy, data retention, and logging policies of Rube, Composio, and PDF co before production use.
Test the skill and its external connection behavior in an isolated environment before using it with real 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-co-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/pdf-co-automation/SKILL.md
2. Save it as ~/.claude/skills/pdf-co-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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

Automate Craftmypdf PDF generation and document workflows through Rube MCP.

ComposioGet→

$ loading_