home / skills / composiohq / awesome-claude-skills / api2pdf-automation

api2pdf-automation skill

safe

/api2pdf-automation

This skill automates Api2pdf tasks via Rube MCP by discovering tool schemas first and managing connections for reliable workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill api2pdf-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: api2pdf-automation
description: "Automate Api2pdf tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Api2pdf Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/api2pdf](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `api2pdf`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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](https://composio.dev)*

Overview

This skill automates Api2pdf tasks through Composio's Api2pdf toolkit using the Rube MCP workflow manager. It provides a reliable pattern for discovering tools, validating connections, and executing Pdf-related operations programmatically. The skill emphasizes always discovering current tool schemas before execution to prevent schema drift and failures.

How this skill works

Always call RUBE_SEARCH_TOOLS first to retrieve available tool slugs, input schemas, recommended execution plans, and pagination tokens. Use RUBE_MANAGE_CONNECTIONS to verify an active Api2pdf connection, then run RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH for bulk work) with schema-compliant arguments and an explicit memory object. Reuse session IDs for a single workflow and generate new sessions for separate flows.

When to use it

Generate PDFs, convert HTML to PDF, or perform other Api2pdf operations in automated workflows.
Build CI/CD tasks that create, merge, or manipulate documents programmatically.
Run bulk PDF operations using remote workbench or multi-execute patterns.
Integrate Api2pdf into multi-step agent flows where tool schemas may change.
Automate recurring report generation where sessions and memory help maintain state.

Best practices

Always run RUBE_SEARCH_TOOLS before using a tool to fetch the latest schema and tool slug.
Verify the Api2pdf connection via RUBE_MANAGE_CONNECTIONS and ensure status is ACTIVE.
Pass exact field names and types returned by the tool schema; do not hardcode arguments.
Include a memory object (even empty {}) in RUBE_MULTI_EXECUTE_TOOL calls to avoid errors.
Handle pagination: check for tokens in responses and fetch until completion.
Reuse session_id for a single workflow; create a fresh session for independent workflows.

Example use cases

Automate weekly report PDFs from HTML templates and push results to storage.
Batch-convert a set of HTML invoices to PDFs using RUBE_MULTI_EXECUTE_TOOL with discovered tool slugs.
Create a web endpoint that triggers Rube MCP workflows to generate and return a PDF on demand.
Run large-scale document merges via RUBE_REMOTE_WORKBENCH and run_composio_tool() for parallelism.
Validate and test Api2pdf tool schemas in CI by first calling RUBE_SEARCH_TOOLS and RUBE_GET_TOOL_SCHEMAS.

FAQ

What must I call first when using this skill?

Always call RUBE_SEARCH_TOOLS first to discover current tool slugs and input schemas.

What if RUBE_MANAGE_CONNECTIONS shows the connection is not ACTIVE?

Follow the returned auth link to complete setup, then re-check until the status is ACTIVE before executing tools.