openrouter-automation

Automate Openrouter API operations through Rube MCP toolkits and structured execution workflows.

74.2k|8.5k|Updated Oct 17, 2025
One-click install
npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill openrouter-automation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openrouter-automation
Source: https://github.com/ComposioHQ/awesome-claude-skills/tree/main/composio-skills/openrouter-automation
Command: npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill openrouter-automation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the complexity of manually managing Openrouter API connections and tool schemas by providing a standardized, automated workflow for discovery and execution.

Core Features & Use Cases

  • Dynamic Tool Discovery: Automatically fetches current Openrouter tool schemas and execution plans via Rube MCP.
  • Connection Management: Validates and maintains active authentication states for Openrouter toolkits.
  • Use Case: Use this to programmatically execute Openrouter tasks, such as model routing or usage tracking, without hardcoding tool slugs or manually verifying connection status.

Quick Start

Use the openrouter-automation skill to discover available tools and execute a specific task using the Rube MCP gateway.

Frequently Asked Questions about openrouter-automation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I execute Openrouter tasks with this skill?

First, call RUBE_SEARCH_TOOLS to identify available Openrouter tools, then verify your connection status with RUBE_MANAGE_CONNECTIONS, and finally use RUBE_MULTI_EXECUTE_TOOL to run your desired operations.

What should I do if my Openrouter connection is inactive?

Call RUBE_MANAGE_CONNECTIONS with the openrouter toolkit parameter. If the status is not ACTIVE, follow the provided authentication link to re-authorize your connection.

Why must I call RUBE_SEARCH_TOOLS before executing?

Tool schemas and slugs change frequently. Calling RUBE_SEARCH_TOOLS ensures you are using the most current input schemas and execution parameters, preventing runtime errors.

Can I reuse session IDs for different workflows?

No, you should generate new session IDs for distinct workflows to maintain state isolation, though you should reuse the same session ID within a single multi-step workflow.

What is the purpose of the memory parameter?

The memory parameter is required by RUBE_MULTI_EXECUTE_TOOL to maintain context across tool calls. Always include it as an empty object {} if no specific state needs to be passed.