maintainer-ops
Use for vLLM Semantic Router issue intake, PR decisions, releases, and reviewed GitHub mutations performed on behalf of maintainers.
64
76%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./tools/agent/skills/maintainer-ops/SKILL.mdMaintainer 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.
- Repository
- vllm-project/semantic-router
- Commit
c89d5d4
- Last updated
- First committed
Is this your skill?
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.