メニュー
Install vLLM Semantic Router in agent-safe mode, import supported OpenClaw model providers into canonical VSR config, and rewrite OpenClaw to target VSR.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | openclaw-vsr-bridge |
| description | Install vLLM Semantic Router in agent-safe mode, import supported OpenClaw model providers into canonical VSR config, and rewrite OpenClaw to target VSR. |
| user-invocable | true |
openclaw.json should be moved under VSR management.config.yaml is written successfully.curlbashCheck whether VSR is already installed with command -v vllm-sr.
If VSR is missing, run the supported installer in agent-safe mode:
curl -fsSL https://vllm-sr.ai/install.sh | bash -s -- --mode cli --runtime skip --no-launch
Locate the OpenClaw config in this order unless the user already gave you a path:
$OPENCLAW_CONFIG_PATH./openclaw.json~/.openclaw/openclaw.jsonImport the OpenClaw model providers into canonical VSR config:
vllm-sr config import --from openclaw --source <openclaw.json> --target config.yaml
Do not pass --force unless the user explicitly approves overwriting existing backup files.
After a successful import, report:
Suggest the next validation commands:
vllm-sr validate config.yaml
vllm-sr config router --config config.yaml
If the user wants runtime verification after validation, suggest:
vllm-sr serve --config config.yaml
curl http://127.0.0.1:8899/v1/models
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.
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.
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.
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 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.
Calibrates routing changes against a live router endpoint with executable probes, local DSL validation, versioned deploys, and structured failure review. Use when tuning signals, projections, decisions, or maintained route examples against a real apiserver.