/router-contract-change

Use when changing a request-visible router contract across configuration, signals, decisions, algorithms, or recipe-scoped plugins in vLLM Semantic Router.

BOOST

vllm-project@vllm-project

GitHub

From plugin

semantic-router

6.2k4 skills

Install

$ npx -y skills add vllm-project/semantic-router --skill router-contract-change --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/router-contract-change

Context preview

The summary Claude sees to decide when to auto-load this skill.

Use when changing a request-visible router contract across configuration, signals, decisions, algorithms, or recipe-scoped plugins in vLLM Semantic Router.

SKILL.md

router-contract-change.SKILL.md

name: router-contract-change
description: Use when changing a request-visible router contract across configuration, signals, decisions, algorithms, or recipe-scoped plugins in vLLM Semantic Router.

Router contract changes

Read the nearest `AGENTS.md` for every touched subtree and `tools/agent/docs/change-surfaces.md` for the affected contract.

Keep the request-facing entrypoint, isolated recipe, signal/projection inputs, decision or algorithm, and selected backend/plugin behavior consistent. Update canonical config, generated or schema-derived artifacts, and user-visible docs only where that contract changes.

Run `make check` first. Use `make verify DOMAIN=<domain>` for the affected integration contract, or `make verify PROFILE=<profile>` when behavior crosses the deployment boundary. A pure refactor does not need new E2E coverage.

Read it on GitHub ↗

Ships withsemantic-router

An open, programmable decision layer for models and compute.

Get the whole plugin

Stats

HTML Bash Docker Kubernetes GitHub

+2 tags

Hugging Face Slack

6,193

Stars

1,049

Forks