Install, configure, verify, maintain, troubleshoot and optimize vLLM Semantic Router v0.5 on a Docker host (CPU, AMD or NVIDIA GPU) or a Kubernetes cluster (Helm or the operator), through its CLI and Router API. Use for a first install, configuration and routing changes, checks of routed requests, upgrades and the v0.5 config migration, secrets, logs, health, backup and restore, removal, failure diagnosis, and tuning of the decision model, recipes, caches, latency and cost with sr-bench.
98%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Medium
Suggest reviewing before use
The canonical home for this skill is vllm-sr-agent-operations in vllm-project/semantic-router
The skill prompts the agent to compromise the security or integrity of the user’s machine by modifying system-level services or configurations, such as obtaining elevated privileges, altering startup scripts, or changing system-wide settings.
The skill mainly asks for user approval before system-wide changes, but it does suggest a concrete `sudo apt-get install` and tells the agent to have the user join the `docker` group, which touches privileged machine state.
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
The required workflows mainly read the user's own config, first-party docs, and the user's model endpoints. The one outsider-authored path is the optional Optimize task, which prepares public MMLU-Pro benchmark cases and runs them through sr-bench, so the agent ingests text an outsider authored only after it selects that benchmark.
vllm-project/semantic-router
8a1b356
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.