agentleFS
SonyHarvSonyHarv/claude-polyrouter/skills/route/SKILL.md

route

Skill2 starsChanged 8 months agoMITView on GitHub

Manually route a query to the optimal Claude model (Haiku/Sonnet/Opus)

18 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use prototype.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • GoogleSkill

    prototype

    Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If a model name is given, find which level maps to that model in the active config

    line 13
  2. Distinctive:

    If a query follows, spawn the appropriate subagent with that query

    line 14
  3. Distinctive:

    If no query follows, inform the user that subsequent queries will use that tier

    line 15

“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Manual Route Override

The user wants to manually specify which model tier to use.

Instructions

  1. Parse the first argument as either a level name (fast, standard, deep) or a model name (haiku, sonnet, opus)
  2. If a model name is given, find which level maps to that model in the active config
  3. If a query follows, spawn the appropriate subagent with that query
  4. If no query follows, inform the user that subsequent queries will use that tier

Level-to-Model Mapping (defaults)

  • fast / haiku → polyrouter:fast-executor
  • standard / sonnet → polyrouter:standard-executor
  • deep / opus → polyrouter:deep-executor

Action

Spawn the appropriate subagent:

Agent(subagent_type="polyrouter:<agent>", prompt="<user's query>", description="Manual route to <model>")

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.