Fleet Sim Change
Developmentfleet-sim-changeFleet Sim Change is an Agent Skill for development published in the vllm-project/semantic-router repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
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/.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/vllm-project/semantic-router/blob/HEAD/tools/agent/skills/fleet-sim-change/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/fleet-sim-change, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Fleet Sim Change
Trigger
- Change the fleet simulator package, API service, CLI entrypoints, or release workflow
- Change simulator-owned docs or static assets that must stay aligned with the maintained subsystem
Workflow
- Read the fleet-sim local rules and change-surface contract
- Modify the simulator package, workflow, or owned docs and assets as one subsystem
- Run
make agent-report ENV=cpu CHANGED_FILES="..."to verify routing and validation scope - Run the simulator validation path and any affected harness checks
- Confirm simulator runtime and owned docs or assets still describe the same maintained surface
Gotchas
src/fleet-sim/**is a first-class subsystem now; do not route it through generic fallback reasoning or treat its docs as repo-generic prose.- Moves inside
fleet_simstill require public import and entrypoint stability, even when the visible change looks like a small API-handler edit.
Must Read
Standard Commands
make agent-report ENV=cpu CHANGED_FILES="..."make vllm-sr-sim-testmake agent-ci-gate CHANGED_FILES="..."
Acceptance
- Simulator package, API entrypoints, and owned docs or assets stay aligned
- Simulator release or runtime contract changes update the maintained workflow and validation path