$ ~/registry/skill/composiohq-composio-skills-api2pdf-automation

SKILL

api2pdf-automation

Name: api2pdf-automation
Author: Composio

Automate Api2pdf workflows for PDF generation, conversion, and document handling.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

The material itself is a prompt-style document and does not declare local execution, file access, or fixed external endpoints. However, it is intended to discover and invoke remote Api2pdf tools through Rube MCP/Composio, so actual use involves external service connectivity and dynamic tool capabilities and should be treated with moderate caution.

CredentialsCaution

The material says 'No API keys needed,' but also requires an ACTIVE `api2pdf` connection via `RUBE_MANAGE_CONNECTIONS` and completing a returned auth link, indicating likely third-party account authorization or token binding in practice. No details are provided about credential storage, scope, or least-privilege controls.

Network egressCaution

The README explicitly requires connecting to the remote MCP endpoint `https://rube.app/mcp` and using Composio/Api2pdf-related services for tool discovery, connection management, and execution. Task arguments and workflow context may be sent to those declared services, but the material does not detail data flows, logging retention, or specific downstream endpoints.

Code executionLow risk

Based on the provided material, this is a prompt-style skill description and does not declare launching local processes, running scripts, or requesting system-level execution privileges. The described execution occurs at the MCP tool layer rather than through any auditable local code execution logic in the skill itself.

Data accessCaution

The material does not declare direct local file or system data access, but session IDs, memory parameters, tool arguments, and potentially business document content may be passed to remote tools through Rube/Composio. There is no clear statement of accessible data scope, data minimization, or isolation boundaries.

Supply chainLow risk

The source is a public open-source GitHub repository entry with high community adoption (about 64.9k stars), both strong risk-reducing signals. The current material is mainly a README/prompt asset; while the license is undeclared and maintenance status is unknown, there are no signs of closed-source distribution, suspicious install scripts, or obvious deceptive red flags.

Recommendations

Before connecting, verify the authorization scope for Rube MCP and the Api2pdf account, and grant only the minimum permissions needed for PDF automation.
Avoid placing unnecessary sensitive data in tool arguments, memory, or session context, and verify the remote services' data retention policies.
Test the skill in an isolated environment first to observe the actual tools invoked, endpoints contacted, and authentication flow returned.
Before production use, review the official privacy policies, audit information, and maintenance status of Composio, Rube, and Api2pdf.

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 "api2pdf-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/api2pdf-automation/SKILL.md
2. Save it as ~/.claude/skills/api2pdf-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Api2pdf Automation via Rube MCP

Automate Api2pdf operations through Composio's Api2pdf toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/api2pdf

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["api2pdf"]
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 Api2pdf-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `api2pdf`
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

Automatically convert text into PDFs for faster document creation and archiving.

ComposioGet→

$ loading_