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

SKILL

openrouter-automation

Name: openrouter-automation
Author: Composio

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

Stars

★ 67,807

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill appears to be mainly procedural guidance rather than standalone executable code. It does not declare local secrets or direct local code execution, but it depends on external Rube MCP/Composio/Openrouter connections and remote tool execution, so actual data flow and permissions should be verified in the connected MCP tools; given its open-source source and strong community adoption, the overall posture is low risk to caution.

CredentialsCaution

The material states that no API key is needed to add Rube MCP, but it also requires an active `openrouter` connection via `RUBE_MANAGE_CONNECTIONS` and asks the user to complete an auth link. This implies possible third-party account authorization or token handling, but the credential type, storage method, and scope are not described.

Network egressCaution

This skill depends on the remote MCP endpoint `https://rube.app/mcp` and performs remote search, connection management, and tool execution through Composio/Openrouter-related tools. User inputs, tool arguments, session IDs, and possibly business data are expected to be sent to those stated services, though the material does not provide more detailed egress boundaries.

Code executionCaution

As a prompt-only skill, the material does not show direct local process spawning or code execution by itself. However, it explicitly uses remote execution capabilities such as `RUBE_MULTI_EXECUTE_TOOL` and `RUBE_REMOTE_WORKBENCH`, meaning actions may be triggered indirectly via external MCP tools, with actual execution privileges depending on the remote toolset.

Data accessCaution

The material does not claim direct read/write access to local files or local data. Its primary access surface is data handled through Rube MCP sessions, search results, connection states, and remote tool parameters. There is no clear sign of excessive local authorization beyond its stated purpose, though remote tools may process user-submitted task data.

Supply chainLow risk

The source is an open GitHub repository with very strong community adoption (64.7k stars), and the system also marks it as prompt-only and open-source. Although the license is not stated and maintenance status is unknown, the available material suggests good auditability and source credibility, with no obvious supply-chain red flags.

Recommendations

Treat `https://rube.app/mcp` as an external service and verify its privacy policy, log retention, and data-handling scope before connecting it.
When completing Openrouter/Composio authorization, use least-privilege accounts where possible and review the granted scopes carefully.
Review the specific tools and schemas returned by `RUBE_SEARCH_TOOLS` before execution to avoid sending sensitive data to unnecessary remote tools.
If possible, use it only in a controlled workspace and periodically review or revoke connections that are no longer needed.

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 "openrouter-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/openrouter-automation/SKILL.md
2. Save it as ~/.claude/skills/openrouter-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Openrouter Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/openrouter

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["openrouter"]
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 Openrouter-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `openrouter`
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 OpenWeather API queries and weather data workflows via Rube MCP.

ComposioGet→

$ loading_