$ ~/registry/skill/composiohq-composio-skills-openperplex-automation

SKILL

openperplex-automation

Name: openperplex-automation
Author: Composio

Automate Openperplex workflows via Rube MCP with schema-first tool discovery.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.9k

Summary

This skill is essentially prompt/workflow guidance and does not itself require local secrets, code execution, or file access. However, it depends on external Rube MCP and an Openperplex connection, so actual use will send operations and related data to third-party services and requires attention to external permissions and data flows.

CredentialsCaution

The material says 'No API keys needed', but it also requires creating an ACTIVE `openperplex` connection via `RUBE_MANAGE_CONNECTIONS` and completing an auth link. This suggests credentials are likely delegated or hosted on the Rube/Openperplex side rather than truly absent; review third-party authorization scope and token handling.

Network egressCaution

It explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and executing actions through Composio/Openperplex tools. Queries, session IDs, tool arguments, and potentially business data will be sent to those declared external services. This is normal network egress for a remote MCP setup, with no additional suspicious covert exfiltration described.

Code executionLow risk

Based on the material, this skill is guidance on the order of Rube MCP tool calls and does not describe spawning local processes, running shell/scripts, or requesting system-level execution privileges; it is a prompt-only style skill.

Data accessLow risk

It does not claim to read or write local files, databases, clipboard contents, or operating system resources. Data access is primarily limited to sending queries, connection state, and tool arguments to the remote MCP. Based on the provided material, there is no sign of excessive local data access.

Supply chainLow risk

The source is a GitHub open-source repository with strong community adoption (64.9k stars), which are meaningful risk-reducing factors. What is shown here is skill documentation rather than an executable install script. The missing license declaration and unknown maintenance status are worth checking, but they are not enough on their own to raise this to high risk.

Recommendations

Before connecting to `https://rube.app/mcp`, verify the privacy policy, data retention, and authorization scope of Rube and Openperplex.
Create the Openperplex connection only when needed, prefer least-privilege accounts, and periodically revoke unused connections.
Avoid sending unnecessary sensitive data in tool arguments or queries until you confirm what third parties process or store.
Check the repository license, recent maintenance activity, and Composio/Openperplex documentation to confirm long-term maintainability.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "openperplex-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/openperplex-automation/SKILL.md
2. Save it as ~/.claude/skills/openperplex-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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

Automate Refiner workflows via Rube MCP using current tool schemas first.

ComposioGet→

$ loading_