Rube MCP is Composio's multi-tool orchestration platform used to search tools, manage connections, and execute tool workflows.

Do I need API keys to use text-to-pdf-automation?

No. You only need to add the MCP endpoint (e.g., https://rube.app/mcp) to your client configuration.

What if tool schemas change?

Always call RUBE_SEARCH_TOOLS before executing and do not hardcode tool slugs or arguments; adapt to the latest schemas.

text-to-pdf-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/text-to-pdf-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Text To PDF Automation via Rube MCP

Automate Text To PDF operations through Composio's Text To PDF toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/text_to_pdf

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["text_to_pdf"]
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 Text To PDF-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `text_to_pdf`
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/text-to-pdf-automation/SKILL.md

View on GitHub

Overview

Automates Text To PDF tasks using Composio's Rube MCP toolkit. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS, establishing an active text_to_pdf connection via RUBE_MANAGE_CONNECTIONS, and executing tools through RUBE_MULTI_EXECUTE_TOOL to keep integrations up-to-date.

How This Skill Works

The workflow starts by discovering available tools and their input schemas with RUBE_SEARCH_TOOLS. After confirming an ACTIVE connection to the text_to_pdf toolkit via RUBE_MANAGE_CONNECTIONS, you execute a chosen tool using RUBE_MULTI_EXECUTE_TOOL, providing the required memory and a session_id. This approach keeps tool definitions dynamic and ensures reliable execution within automated workflows.

When to Use It

You need up-to-date tool schemas before running a Text To PDF task.
You must verify the toolkit connection is ACTIVE before execution.
You want to run a discovered tool with proper memory and session handling.
You're integrating PDF generation into an automated workflow using Rube MCP.
You're performing bulk or batch PDF generation and need programmatic control over tools.

Quick Start

Step 1: Ensure Rube MCP is reachable and RUBE_SEARCH_TOOLS responds.
Step 2: Discover tools with RUBE_SEARCH_TOOLS for Text To PDF operations and note the tool_slug and input schema.
Step 3: Confirm ACTIVE connection via RUBE_MANAGE_CONNECTIONS and run RUBE_MULTI_EXECUTE_TOOL with memory: {} and the session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS before selecting tools.
Check connection status ACTIVE via RUBE_MANAGE_CONNECTIONS prior to executing.
Use exact field names and types from the live tool schemas; avoid hardcoding.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and paginate results if needed.

Example Use Cases

Invoice generation: Convert order text to PDF invoices using a Text To PDF tool discovered via RUBE_SEARCH_TOOLS.
Customer reports: Transform JSON narratives into PDFs using a templated layout.
Batch reports: Schedule nightly PDF generation in a workflow with persistent sessions.
On-demand documents: Generate a single PDF from chat prompts using a discovered tool.
Document packaging: Merge multiple text blocks into a single PDF through a tool workflow.

Frequently Asked Questions

Add this skill to your agents