release-cherry-pick

Cherry-pick merged PRs labeled for a release branch into that branch, then open a PR and apply the cherry-pick-done label. Use when asked to "cherry-pick PRs for release/X.Y.Z", "pick PRs to release branch", or "cherry-pick labeled PRs".

Quality

100%

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

100%Weight 40%Scale 1-3

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

The body is an efficient, fully actionable workflow with concrete commands and an explicit conflict-recovery loop. It is well organized for a single-purpose skill and respects the token budget.

Dimension	Reasoning	Score
Conciseness	Lean throughout with no padding or explanations of concepts Claude already knows; every step is a direct instruction or executable command.	3 / 3
Actionability	Provides concrete, executable gh/git commands (search API call, cherry-pick -s, gh pr create, gh pr edit) that are copy-paste ready rather than pseudocode.	3 / 3
Workflow Clarity	Seven clearly numbered steps in merge order with an explicit conflict-recovery feedback loop ('tell the user which PR caused the conflict... git cherry-pick --continue') for this batch operation.	3 / 3
Progressive Disclosure	A short (under 50 lines) single-purpose skill with well-organized titled sections and no need for external references; structure is clear and one-level.	3 / 3
	Total	12 / 12 Passed

Description

100%Weight 40%Scale 1-3

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

The description is concise, concrete, and complete, naming specific actions and giving explicit trigger guidance in third person. It is clearly distinguishable from other skills and unlikely to cause conflicts.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Cherry-pick merged PRs labeled for a release branch into that branch', 'open a PR', and 'apply the cherry-pick-done label' — rather than vague language.	3 / 3
Completeness	Explicitly states both what the skill does (cherry-pick, open PR, apply label) and when to use it via an explicit 'Use when' clause.	3 / 3
Trigger Term Quality	Includes several natural phrasings a user would say: "cherry-pick PRs for release/X.Y.Z", "pick PRs to release branch", and "cherry-pick labeled PRs".	3 / 3
Distinctiveness Conflict Risk	Targets a narrow, well-defined niche (release-branch cherry-picking) with distinct trigger phrasings unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: NVIDIA/Model-Optimizer
Path: .agents/skills/release-cherry-pick/SKILL.md
Commit: 33d05b0

Reviewed: 15 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.