What is pdfless-automation?

A skill to automate Pdfless tasks via Rube MCP by discovering current tool schemas, establishing an ACTIVE Pdfless connection, and executing tools.

Do I need to search tools first?

Yes. Always call RUBE_SEARCH_TOOLS to get the latest tool slugs and input schemas before any execution.

How do I execute a tool?

Use RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug, provide schema-compliant arguments, include a memory object, and specify the session_id.

pdfless-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/pdfless-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Pdfless Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/pdfless

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["pdfless"]
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 Pdfless-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `pdfless`
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/pdfless-automation/SKILL.mdView on GitHub

Overview

Automate Pdfless operations through Composio's Pdfless toolkit via Rube MCP. Always search tool schemas first to ensure you use current tool slugs and inputs. This skill coordinates discovery, connection management, and tool execution for reliable Pdfless workflows.

How This Skill Works

You first discover available Pdfless tools with RUBE_SEARCH_TOOLS to get current input schemas. Next, verify the Pdfless connection is ACTIVE with RUBE_MANAGE_CONNECTIONS. Finally, execute the chosen tool using RUBE_MULTI_EXECUTE_TOOL, supplying the discovered slug, exact schema fields, memory, and session_id to run the workflow.

When to Use It

When you need to automate a Pdfless operation end-to-end and rely on current tool schemas.
When tool slugs and input fields change and you must fetch them before running.
When you must verify the Pdfless connection is ACTIVE prior to execution.
When reusing a session ID across a multi-step Pdfless workflow.
When performing bulk Pdfless tasks via RUBE_REMOTE_WORKBENCH and run_composio_tool().

Quick Start

Step 1: Verify RUBE_SEARCH_TOOLS responds and fetch Pdfless tools (queries: [{use_case: "Pdfless operations"}]).
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["pdfless"] and confirm ACTIVE status.
Step 3: Execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL, including memory: {} and the session_id from Step 2.

Best Practices

Always search for tools first with RUBE_SEARCH_TOOLS to get current slugs and inputs.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from the search results; avoid hardcoding.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow but generate new ones for new workflows and handle pagination tokens if present.

Example Use Cases

End-to-end Pdfless automation: discover a Pdfless tool, connect, and execute with the correct schema.
Weekly Pdfless data extraction: automate extraction tasks and aggregate results using discovered tool inputs.
Scheduled job validation: run RUBE_SEARCH_TOOLS first to confirm slugs before triggering a workflow.
Session-optimized workflows: reuse a single session_id across multiple Pdfless operations to save setup time.
Bulk document processing: use RUBE_REMOTE_WORKBENCH with run_composio_tool() to handle large Pdfless batches.

Frequently Asked Questions

Add this skill to your agents