api2pdf-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/api2pdf-automation --openclawApi2pdf 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_CONNECTIONSwith toolkitapi2pdf - 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 toolkitapi2pdf - 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_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 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
Source
git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/api2pdf-automation/SKILL.mdView on GitHub Overview
This skill automates Api2pdf tasks through Composio's Api2pdf toolkit using the Rube MCP platform. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before each workflow and ensuring an ACTIVE Api2pdf connection via RUBE_MANAGE_CONNECTIONS to execute tools reliably.
How This Skill Works
Discovery uses RUBE_SEARCH_TOOLS to list available Api2pdf tools, followed by verifying the connection with RUBE_MANAGE_CONNECTIONS, and then executing the chosen tool via RUBE_MULTI_EXECUTE_TOOL with the discovered slug and schema-compliant arguments. Always include the memory parameter (even if empty {}) and reuse the session_id to preserve context across steps.
When to Use It
- Automate batch Api2pdf conversions for a project by discovering tools and executing them in sequence.
- Set up and test a new Api2pdf connection via RUBE_MANAGE_CONNECTIONS before workflows.
- Validate current tool schemas before hardcoding any slugs or arguments.
- Coordinate multiple tool runs in one session to optimize performance.
- Troubleshoot issues by checking that RUBE_SEARCH_TOOLS returns available tools and that the connection is ACTIVE.
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server and confirm RUBE_SEARCH_TOOLS responds.
- Step 2: Connect the toolkit: RUBE_MANAGE_CONNECTIONS with toolkits: ['api2pdf'] and complete any auth to ACTIVE.
- Step 3: Discover tools with RUBE_SEARCH_TOOLS and execute one with RUBE_MULTI_EXECUTE_TOOL using the discovered slug, proper arguments, and memory; reuse session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS before executing tools.
- Ensure RUBE_MANAGE_CONNECTIONS shows ACTIVE status before running tools.
- Use exact field names and types from tool schemas.
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
- Reuse session IDs within a workflow; generate new ones only for new workflows.
Example Use Cases
- Automate a batch of Api2pdf conversions by discovering tools at runtime and executing them in a single session.
- Authenticate with the api2pdf toolkit via RUBE_MANAGE_CONNECTIONS and then run a single conversion task.
- Run multiple Api2pdf operations using RUBE_MULTI_EXECUTE_TOOL and store results in memory.
- Paginate through tool discovery results with RUBE_SEARCH_TOOLS to fetch all available Api2pdf tools and test execution.
- Reuse an existing session to chain several Api2pdf tasks in a single workflow.
