What prerequisites must be met before automation?

Rube MCP must be connected, RUBE_SEARCH_TOOLS must respond to discover Openperplex tools, and an ACTIVE Openperplex connection must exist via RUBE_MANAGE_CONNECTIONS.

Why is searching tool schemas first important?

Tool schemas can change; searching first ensures you use current slugs and correct input fields, preventing run-time errors.

How should I handle tool execution in a workflow?

Use RUBE_MULTI_EXECUTE_TOOL with the discovered tool slug, supply exact inputs from the schema, include memory: {} even if empty, and manage a session_id for continuity.

openperplex-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Openperplex Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/openperplex

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["openperplex"]
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 Openperplex-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `openperplex`
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/openperplex-automation/SKILL.md

View on GitHub

Overview

Automate Openperplex operations with Composio's toolkit through Rube MCP. Always search for current tool schemas before execution, validate ACTIVE connections, and run tools with exact, schema-compliant inputs to ensure reliable workflows.

How This Skill Works

Technically, you verify Rube MCP availability, then discover tools with RUBE_SEARCH_TOOLS to obtain current schemas. After confirming an ACTIVE Openperplex connection, you execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL using the correct slug, schema-compliant arguments, and a memory object, reusing or generating a session_id as needed.

When to Use It

When automating Openperplex tasks that require up-to-date tool schemas
When establishing a new Openperplex connection via Rube MCP
When selecting and validating a specific Openperplex tool before execution
When running multi-tool workflows that rely on memory and session continuity
When handling tool results with pagination or incremental fetches

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration and verify RUBE_SEARCH_TOOLS responds
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit: openperplex and authenticate if required; confirm ACTIVE
Step 3: Run RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug, memory: {}, and session_id from your workflow

Best Practices

Always search first: tool schemas change; avoid hardcoding slugs or arguments without RUBE_SEARCH_TOOLS
Check connection: ensure RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Schema compliance: use exact field names and types from the search results
Memory parameter: 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

Example Use Cases

Schedule a daily Openperplex report by discovering tools, validating the ACTIVE connection, and executing the daily_report tool with proper memory
Onboard a new Openperplex workflow by searching tool schemas, establishing the openperplex connection, and running a starter tool with a session
Perform bulk Openperplex operations via RUBE_MULTI_EXECUTE_TOOL across multiple tools using a shared memory store
Handle paginated tool results by iteratively calling RUBE_SEARCH_TOOLS and continuing until all pages are retrieved
Prevent breakage from schema drift by re-running RUBE_SEARCH_TOOLS before each tool run and updating tool slugs accordingly

Frequently Asked Questions

Add this skill to your agents