maintainer-release-ops

Maintainer release and milestone operating workflow. Use when a maintainer wants to plan a release, assess milestone health, coordinate release blockers, or generate a release-focused review brief.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

93%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, executable skill body with concrete commands, clear sequencing, and explicit write-safety validation via dry-runs and maintainer confirmation. The only gap is an explicit error-recovery feedback loop in the workflow.

Dimension	Reasoning	Score
Conciseness	Lean throughout — short bulleted sections (Trigger, Stop Conditions, Gotchas, Acceptance) with no over-explanation of concepts Claude already knows; every section earns its tokens.	5 / 5
Actionability	Standard Commands gives copy-paste-ready invocations ('python3 tools/agent/scripts/maintainer_board.py sync --milestone "<name>"', 'release-report --release-plan ... --write', 'create-issues ... --dry-run') covering the common cases.	5 / 5
Workflow Clarity	Six-step workflow with explicit checkpoints (dry-run flags, 'Generate proposed actions only; do not mutate GitHub by default', 'Apply actions only after maintainer confirmation', Stop Conditions), but lacks an explicit error-recovery feedback loop (validate -> fix -> retry).	4 / 5
Progressive Disclosure	Well-organized overview body with a 'Must Read' section of one-level-deep, clearly signaled references (maintainer-ops.md, maintainer-policy.yaml, .prowlabels.yaml, PULL_REQUEST_TEMPLATE.md) and no nested reference chains.	5 / 5
	Total	19 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, concise description that names the domain and enumerates concrete release/milestone actions with an explicit 'Use when' trigger clause. Minor keyword-synonym gaps keep trigger term quality just below the top anchor.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'plan a release, assess milestone health, coordinate release blockers, or generate a release-focused review brief' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly states both what ('Maintainer release and milestone operating workflow') and when ('Use when a maintainer wants to plan a release...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural maintainer-facing phrases like 'plan a release', 'assess milestone health', and 'coordinate release blockers' are present, but common synonyms ('cut/ship a release', 'release checklist', 'milestone status') are missing.	4 / 5
Distinctiveness Conflict Risk	Clear niche around releases and milestones with distinct triggers; release planning, blocker coordination, and release briefs are unlikely to fire for the sibling issue/PR triage skill.	5 / 5
	Total	19 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 4 suspicious	Warning

	Total	14 / 16 Passed

Repository: vllm-project/semantic-router
Path: tools/agent/skills/maintainer/release-ops/SKILL.md
Commit: adc7455

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.