flux-controller-minor-releases

Run the upstream Flux controller minor release procedure for helm-controller, image-automation-controller, image-reflector-controller, kustomize-controller, notification-controller, source-controller, and source-watcher. Use when cutting a new controller minor release (vX.Y.0): creating the release series branch, drafting the minor changelog, tagging, merging the release branch back to main, and adding the backport label.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

88%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 highly actionable, well-sequenced release runbook with concrete commands and thorough validation checkpoints; its main weakness is only minor verbosity in a few rationale passages. It is self-contained with no bundle files, and its organization is strong for a single-file skill.

Suggestions

Tighten the explanatory rationale blocks (e.g. the 'Why last' paragraph in step 11 and parenthetical asides) into one-line notes to recover token budget without losing the reasoning.

Consider extracting the multi-section 'How To Build The Changelog Entry' procedure into a references file so SKILL.md stays a lean overview while the detailed selection rules live one level deep.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence with git/gh, with no padded concept explanations; a few rationale blocks ('Why last', explanatory parentheticals) could be trimmed slightly without losing clarity.	4 / 5
Actionability	Every step ships concrete, copy-paste-ready git and gh commands (e.g. 'git switch -c release/vX.Y.x main', 'git tag -s -m "api/vX.Y.0" api/vX.Y.0') plus a ready approval-watch shell loop covering the common cases.	5 / 5
Workflow Clarity	An explicit 11-step sequence with validation checkpoints throughout — fetch before comparing, confirm version refs before tagging, push api tag before release tag, CI-green-plus-approval before merge — and clear feedback loops for review fixes.	5 / 5
Progressive Disclosure	No bundle files are present, so the skill is appropriately self-contained and organized into clear sections (Important rules, Preconditions, Release Flow, Changelog, Critical Checks); structure is good though some sub-procedures (changelog building, dependent-controller bumps) are long but legitimately core.	4 / 5
	Total	18 / 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, specific description that clearly conveys both the capability and its trigger conditions for a well-scoped release-engineering task. It names concrete actions and an explicit version-trigger phrase, leaving little ambiguity about when to invoke it.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — 'creating the release series branch, drafting the minor changelog, tagging, merging the release branch back to main, and adding the backport label' — across all seven named controllers, giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers both 'what' (run the upstream Flux controller minor release procedure) and 'when' ('Use when cutting a new controller minor release (vX.Y.0)') with concrete trigger phrasing.	5 / 5
Trigger Term Quality	Natural phrases a user would say are present — 'cutting a new controller minor release (vX.Y.0)', 'changelog', 'tagging', 'release branch' — but a few common synonyms or phrasings users might say are not covered.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (upstream Flux controller minor releases), enumerates the exact controllers, and excludes flux2/pkg, minimizing any chance of triggering for the wrong skill.	5 / 5
	Total	19 / 20 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: fluxcd/agent-skills
Path: internal/skills/flux-controller-minor-releases/SKILL.md
Commit: 88fb00c

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