Openrouter
Design, build, debug, and optimize OpenRouter API integrations. Use for any OpenRouter API work, including models, reasoning, routing, media, tools, structured output, cost, or performance.
Install
npx skills add davidondrej/skills --skill openroutergit clone --depth 1 https://github.com/davidondrej/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/openrouter ~/.claude/skills/openrouterPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# OpenRouter Make model behavior explicit. Preserve the user's quality, cost, privacy, and reliability requirements across every route and retry. ## Before changing configuration 1. Inspect the actual outgoing request, SDK version, existing configuration, and user preferences. Redact credentials and content. A setting in a UI or config file does not prove the SDK sends it. 2. Verify exact model IDs and live capabilities through the [models API](https://openrouter.ai/api/v1/models). Inspect the selected model's provider endpoints too. Check input/output modalities, context and output limits, supported parameters, reasoning options, prices, and provider availability for **both primary and fallback models**. 3. Choose and record an explicit reasoning setting for each reasoning model. Use the user's requested effort. If unspecified, choose a supported value for the task and state the choice; do not silently inherit a provider default or impose one effort on every model. Read [reasoning and output](references/reasoning-and-output.md) before setting these fields. 4. Set an output ceiling, total deadline, bounded retry policy, and cost limits appropriate to the workload. Reasoning uses output tokens too. A model's context window is not its maximum output length. 5. Read the relevant reference below. Consult current official docs for unfamiliar fields; do not invent model IDs, provider slugs, parameter support, or SDK syntax. ## Rules that prevent expensive mistakes
Details
- Skill name
openrouter- Repository
- davidondrej/skills
- Path
skills/openrouter/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Openrouter skill do?
Design, build, debug, and optimize OpenRouter API integrations. Use for any OpenRouter API work, including models, reasoning, routing, media, tools, structured output, cost, or performance.
How do I install the Openrouter skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add davidondrej/skills --skill openrouter. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Openrouter popular?
It lives in davidondrej/skills, which has 4,336 GitHub stars and 628 forks.
Related skills
Browser Harness
4.3kdavidondrej/skills
Direct browser control via CDP. Use when the user wants to automate, scrape, test, or interact with web pages. Connects to the user's already-running Chrome.
4x4
4.3kdavidondrej/skills
Pull 16 fast decisions out of the user with 4 sets of 4 open questions, then present an implementation plan. Only for risky changes, large product decisions, or large refactors. Run when the user types /4x4. Agents may suggest it in one line but never start it on their own.
Adr Verbatim
4.3kdavidondrej/skills
Record concise ADRs that preserve the user's decisions without conversational noise. Use for "adr-verbatim", "new ADR", "document that as an ADR", "record this decision", or supplied ADR wording.
Threejs Debug Profiler
2.8kmajidmanzarpour/threejs-game-skills
Debug and profile Three.js browser games: blank canvases, render and runtime bugs, asset and audio loading, animation, resize, mobile input, plus performance profiling of draw calls, triangles, textures, memory, shader and post-processing cost, and bundle size.
File Tree
4.3kdavidondrej/skills
Manually-invoked skill that prints a nice file tree of the current topic in a code block. Use when the user says "file-tree" or "file tree".
Threejs Gameplay Systems
2.8kmajidmanzarpour/threejs-game-skills
Build and iterate playable Three.js game systems: starter scaffold, architecture, design briefs, core loops, level and encounter design, entities, input, camera, collision and physics, scoring, objectives, and game feel. Use for first playable slices, new Vite/TypeScript/Three.js setups, level/arena/track/wave/hole/puzzle design, combat encounters, difficulty tuning, and juice.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.