vllm-semantic-router-harness

Name: vllm-semantic-router-harness
Author: vllm-project/semantic-router

$npx mdskill add vllm-project/semantic-router/vllm-semantic-router-harness

This is a native-discovery bridge. The canonical source of truth remains:

SKILL.md

.github/skills/vllm-semantic-router-harnessView on GitHub ↗

---
name: vllm-semantic-router-harness
description: Bridges native skill discovery into the vLLM Semantic Router repository harness, routing tasks through the canonical agent-report flow, repo-local skill registry, and validation commands. Use when starting any task inside the vLLM Semantic Router repository to resolve the correct primary skill, read canonical docs, and run harness validation.
---

# vLLM Semantic Router Harness

This is a native-discovery bridge. The canonical source of truth remains:

- [`AGENTS.md`](../../../AGENTS.md)
- [`docs/agent/README.md`](../../../docs/agent/README.md)
- [`tools/agent/skill-registry.yaml`](../../../tools/agent/skill-registry.yaml)
- [`tools/agent/maintainer-policy.yaml`](../../../tools/agent/maintainer-policy.yaml)
- [`tools/make/agent.mk`](../../../tools/make/agent.mk)

## When To Use

Use this skill whenever the current workspace is this repository or the task touches files under `src/`, `tools/agent/`, `docs/agent/`, `dashboard/`, or `.github/`.

## Required Flow

1. Read [`AGENTS.md`](../../../AGENTS.md) first.
2. Read [`docs/agent/README.md`](../../../docs/agent/README.md) and the nearest local `AGENTS.md` for hotspot directories.
3. Run `make agent-report ENV=cpu|amd CHANGED_FILES="..."` before non-trivial coding-agent edits.
4. Start from the resolved primary skill under [`tools/agent/skills/`](../../../tools/agent/skills/).
5. For maintainer issue, PR, or release work, use [`docs/agent/maintainer-ops.md`](../../../docs/agent/maintainer-ops.md) and generated local state under `.agent-harness/maintainer/`.
6. Validate with the canonical harness commands from [`tools/make/agent.mk`](../../../tools/make/agent.mk).

## Boundaries

- Do not treat this wrapper as canonical policy text.
- Do not copy or fork skill instructions out of `tools/agent/**`.
- Use `make agent-report` to expose the full routed context pack; this wrapper only improves native startup discovery.

More from vllm-project/semantic-router

Skill	Description
config-platform-change	Synchronizes config representations across router config, Python CLI schema, and dashboard config UI. Use when adding or changing a config concept that spans those surfaces or addressing config representation debt before Kubernetes-facing translation.
cross-stack-bugfix	Diagnoses and fixes bugs that span multiple layers (runtime, CLI, UI, platform, tests) requiring coordinated changes across surfaces. Use when a bug does not map cleanly to a narrower skill, the fix touches more than one surface, or changes need cross-cutting validation.
dashboard-platform-change	Modifies dashboard frontend or backend surfaces that present, configure, or manage router behavior through the console UI. Use when changing dashboard pages or components, backend handlers, console persistence, auth or session flows, or user-visible routing metadata in the dashboard.
fleet-sim-change	Modifies the fleet simulator package, API service, release wiring, or simulator-owned docs and assets as one maintained subsystem. Use when changing src/fleet-sim, simulator release workflow, or fleet-sim-owned docs and assets under website/.
harness-contract-change	Modifies the repository's agent contract including AGENTS.md, docs index, manifests, validation scripts, and contributor-facing harness wrappers. Use when updating agent documentation, changing repo manifests, editing validation scripts, modifying CI/workflow classification, or updating contributor-facing guides like README.md, CONTRIBUTING.md, or the PR template.
k8s-platform-change	Modifies Kubernetes-facing operator, CRD, deployment-profile, or DSL translation behavior for semantic-router platform integration. Use when changing operator APIs or controllers, deployment stack manifests, profile-owned platform wiring, or router-to-Kubernetes translation layers.
maintainer-issue-pr-management	Manages GitHub issue and pull-request lifecycle including creation, updates, triage labelling, and closeout metadata using canonical templates and repository taxonomy. Use when a maintainer asks to create, update, close, or triage GitHub issues or PRs, or when issue creation requires codebase analysis for scope, labels, or acceptance criteria.
maintainer-release-ops	Maintainer release and milestone operating workflow. Use when a maintainer wants to plan a release, create milestone issues, sync GitHub issue or PR state, generate a daily review brief, or manage stale PRs and backlog routing.
openclaw-vsr-bridge	Install vLLM Semantic Router in agent-safe mode, import supported OpenClaw model providers into canonical VSR config, and rewrite OpenClaw to target VSR.
plugin-end-to-end	Implements end-to-end plugin changes spanning router config, post-decision processing, optional CLI/UI exposure, and E2E test coverage. Use when adding a new plugin type, changing plugin config schema or execution semantics, updating plugin chain behavior, or modifying plugin-exposed metadata across surfaces.