router-contract-change
Use when changing a request-visible router contract across configuration, signals, decisions, algorithms, or recipe-scoped plugins in vLLM Semantic Router.
71
89%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
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.
- Repository
vllm-project/semantic-router
- Revision
a00f4b2
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.