router-models — Claude Code skill for model selection
router-models is a skill for Claude Code and Codex that lists Weave Router models and lets you enable, disable, or rank them.
Apache-2.0 ★ 5,622 updated 2026-11-10
npx skills add weave-os/router --skill router-models -a claude-codeWhat router-models does
The skill lists available models by provider, marking selectable ones with [x] and the rest with [ ]. You can ask it to enable or disable models or an entire provider; it then prints the updated list. It can also set a model preference order or clear that ranking.
These settings match the checkboxes on the router dashboard. Disabling a model affects the router’s next routing decision, so no restart is needed. With a Weave-hosted router, model selection is managed for the organization at https://router.workweave.ai/models. That listing has no enabled-state markers, so the skill presents it as a plain list.
What it helps with
- check which models the router can select
- enable or disable models by ID
- change availability for a whole provider
- set or clear the preferred model order
Example prompts for the agent
- Show the models available to Weave Router.
- Disable
model-idand show the updated list. - Rank
model-aahead ofmodel-b.
How to install router-models
1Skills CLI (Vercel)
npx skills add weave-os/router --skill router-models -a claude-code2Manually: put the files in place
~/.claude/skills/router-models/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/router-models/
1Skills CLI (Vercel)
npx skills add weave-os/router --skill router-models -a codex2Manually: put the files in place
.agents/skills/router-models/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add weave-os/router --skill router-models -a cursor2Manually: put the files in place
.cursor/skills/router-models/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install weave-os/router install/codex-skills/router-models2Manually: put the files in place
.github/skills/router-models/SKILL.md1Skills CLI (Vercel)
npx skills add weave-os/router --skill router-models -a gemini-cli2Platform CLI
gemini skills install https://github.com/weave-os/router --path install/codex-skills/router-modelsManually: put the files in place
.devin/skills/router-models/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about router-models
How do I install router-models in Claude Code?
Run npx skills add weave-os/router --skill router-models -a claude-code. The skill file is available at ~/.claude/skills/router-models/SKILL.md.
What does router-models do?
It lists the models Weave Router can choose and lets you change their availability or preference order. After a change, it displays the refreshed list.
When does disabling a model take effect?
On the router’s next routing decision. A restart is not needed.
Source text
SKILL.md · Apache-2.0
---
name: router-models
description: "List the models the Weave Router may route to, and turn them on or off."
---
<!-- weave-router managed router-models skill -->
# Weave Router model selection
When the user invokes `$router-models`, show which models this
installation lets the router pick from, and change that selection when asked.
This is the same list — and the same stored setting — as the checkboxes on the
router dashboard's settings page.
Start by running:
```bash
npx --package @weave-os/router -y -- weave-router models --codex{{SCOPE}}
```
That prints every deployed model grouped by provider, with `[x]` for models the
router may pick and `[ ]` for models it may not. Present it back as a compact
checklist in that same `[x]` / `[ ]` form, keeping the provider grouping and the
exact model ids — the user selects models by id.
Then:
- If the user named models or providers, work out whether they want them on or
off from how they phrased it, and apply it with
`weave-router models enable <id>... --codex{{SCOPE}}` or
`weave-router models disable <id>... --codex{{SCOPE}}` (add `providers` before
`enable`/`disable` to switch a whole provider). Several ids can go in one
call. Then re-run the list and show the result.
- If they named nothing, stop after the list and ask which ones to change.
Never change anything they did not ask for.
Other things they might ask for:
- Rank models by preference:
`weave-router models prefer <id> <id>... --codex{{SCOPE}}` (order matters), or
`weave-router models prefer clear --codex{{SCOPE}}` to drop the ranking.
- Providers only: `weave-router models providers --codex{{SCOPE}}`.
If the command reports that this router doesn't expose model selection, that's a
Weave-hosted router: model selection belongs to the whole organization there, so
tell the user to change it at https://app.weaveos.com/organization/settings/weave-router/models —
don't try to work around it. Its listing carries no on/off state, so present it
as a plain list; don't infer which models are enabled.
Disabling a model takes effect on the router's next routing decision; no restart
is needed.
© weave-os · Apache-2.0 · weave-os/router