⏳ This skill is pending AI review.

Scores will appear once the review pipeline completes.

version unknown

maintainer-ops

vllm-project@vllm-project⭐ 6.5k stars· last commit 2d ago· 367 open issues

Use for vLLM Semantic Router issue intake, PR decisions, releases, and reviewed GitHub mutations performed on behalf of maintainers.

Choose how to use this skill

You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.

1. Native installer

This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.

Do not guess an installer command or replace an existing version without reviewing the diff.

2. Complete package recommended

Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.

No complete ProSkills package is published for this listing yet.

3. Prompt-only

Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.

Need only the instruction file?

Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.

No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.

—/10

// RATINGS

⭐GitHub Stars
⭐⭐⭐⭐⭐ 6.5k on GitHubGitHub ↗

Very popular

🟢ProSkills Score
—
📍

Not yet listed on ClawHub or SkillsMP

// README

Main GitHub Release Go Ask DeepWiki


About

Intelligence beyond any one model.

Give your agent harness one API for many models. vLLM Semantic Router selects or combines models for each call, guided by your policy.

Your harness keeps the agent loop, tools, and task state. The Router chooses among configured backends across local, private, and cloud compute.

DimensionFragmented todayWith vLLM SR
ModelsDifferent models excel at different tasks.Select or combine models.
ComputeHardware varies in speed and capacity.Choose among configured backends.
LocationEdge, private, and cloud.Keep calls within approved locations.
PreferencePriorities change by task.Set quality, latency, and cost priorities.

Explore how it works →

Getting Started

Install

curl -fsSL https://vllm-sr.ai/install.sh | bash -s -- --channel stable

For pip, uv, or agent-driven installation, see the Installation Guide.

Try it online

Try System Duo: pick an example and it runs live in your browser, with a free key on first run.

Latest News

More announcements are available on the Blog and Publications pages.

Community

For questions, feedback, or to contribute, please join the #semantic-router channel in vLLM Slack. Track contributors, workgroups, and weekly activity at community.vllm-sr.ai.

Community Meetings

We host two monthly community meetings across APAC and the Americas:

  • APAC-friendly meeting — second Wednesday of the month: 9:00-10:00 AM Singapore time (UTC+8; the same local time in Beijing)
  • Americas-friendly meeting — fourth Wednesday of the month: 8:00-9:00 PM Eastern Time (America/New_York) / 5:00-6:00 PM Pacific Time

Contributing

If you want to contribute, start with CONTRIBUTING.md.

For repository-native development workflow and validation commands, use AGENTS.md as the entrypoint and tools/agent/docs/README.md as the canonical index.

Citation

If you find Semantic Router helpful in your research or projects, please consider citing it:

@misc{semanticrouter2025,
  title={vLLM Semantic Router},
  author={vLLM Semantic Router Team},
  year={2025},
  howpublished={�rl{https://github.com/vllm-project/semantic-router}},
}

// HOW IT'S BUILT

// FILES

2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.

  • tools/agent/skills/maintainer-ops/SKILL.md994 Bupstream ↗
    ---
    name: maintainer-ops
    description: Use for vLLM Semantic Router issue intake, PR decisions, releases, and reviewed GitHub mutations performed on behalf of maintainers.
    ---
    
    # Maintainer operations
    
    Read `tools/agent/docs/maintainer-ops.md` and
    `tools/agent/maintainer-policy.yaml`. Resolve the exact issue, PR, release, and
    head revision before mutating GitHub. Base decisions on current `main`, the
    actual diff, tests, CI, and related history—not on descriptions alone.
    
    Keep discovery read-only. Store local state only under
    `.agent-harness/maintainer/`; acquire the documented resource lease before an
    apply step and release it afterward. Prefer editing a mistaken comment over
    posting a duplicate. Never expose private infrastructure in public artifacts.
    
    For PRs, put blockers first and distinguish suggestions. For issue acceptance,
    use the exact `/accept` comment rather than applying the label directly. For a
    release, verify the immutable commit and artifacts before publication.
    
  • README.mdupstream ↗

    Contents are not inlined in the catalog. Open the upstream file.

Plain-text copy, no login: /skill-bundles/vllm-project-semantic-router-tools-agent-skills-maintainer-ops.md

// REPO STATS

6.5k stars
367 open issues
Last commit: 2d ago