What are the prerequisites to start this skill?

You need a connected Rube MCP (RUBE_SEARCH_TOOLS available) and an active Ocrspace connection via RUBE_MANAGE_CONNECTIONS with the ocrspace toolkit.

Why must I always search tools before executing?

Tool schemas can change; RUBE_SEARCH_TOOLS returns current slugs and input fields, preventing misaligned arguments.

Do I have to include memory in every tool call?

Yes. Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if it's an empty object, to maintain workflow state.

ocrspace-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Ocrspace Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/ocrspace

Prerequisites

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

Step 2: Check Connection

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

Overview

This skill automates Ocrspace operations through Composio's Ocrspace toolkit using Rube MCP. It relies on discovering current tool schemas with RUBE_SEARCH_TOOLS, establishing a connection via RUBE_MANAGE_CONNECTIONS, and executing tools through RUBE_MULTI_EXECUTE_TOOL. Keeping schemas up-to-date ensures correct tool slugs and arguments.

How This Skill Works

First, discover available OCR tools with RUBE_SEARCH_TOOLS to obtain current tool slugs and input schemas. Then verify an ACTIVE Ocrspace connection with RUBE_MANAGE_CONNECTIONS. Finally, run tools via RUBE_MULTI_EXECUTE_TOOL, including memory and session_id, to complete the workflow.

When to Use It

When you need to automate OCR tasks end-to-end for documents using Ocrspace within a Composio workflow
When tool schemas change and you must fetch new tool slugs and arguments before running workflows
When processing multiple OCR jobs in sequence and you want to reuse a session ID
When establishing a new Ocrspace connection and validating it before execution
When you need to batch-run OCR tasks with consistent memory handling

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server and verify RUBE_SEARCH_TOOLS responds
Step 2: Use RUBE_SEARCH_TOOLS to discover available Ocrspace tools and capture tool_slug and input schema
Step 3: Run RUBE_MANAGE_CONNECTIONS for the ocrspace toolkit, then execute RUBE_MULTI_EXECUTE_TOOL with memory and a session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool schemas and avoid hardcoding slugs
Check that the Ocrspace connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before execution
Use exact field names and types from the search results to ensure schema compliance
Include a memory object in every RUBE_MULTI_EXECUTE_TOOL call (even if empty {})
Reuse session IDs within a workflow and generate new IDs for new workflows

Example Use Cases

Automate OCR extraction for a batch of scanned invoices by discovering the tool, connecting, and executing with a single session
Process PDFs to extract text using updated Ocrspace tool slugs retrieved from RUBE_SEARCH_TOOLS
Validate and run multiple OCR tasks across different document types with consistent memory handling
Set up a reusable workflow that handles city-wide document OCR without hardcoding tool names
Handle pagination in tool schema discovery and continue executing all required OCR steps

Frequently Asked Questions

Add this skill to your agents