flux-controller-patch-releases

Run the upstream Flux controller patch release procedure for helm-controller, image-automation-controller, image-reflector-controller, kustomize-controller, notification-controller, source-controller, and source-watcher. Use when preparing a new controller patch release from a release series branch, drafting changelog entries, tagging releases, and opening the follow-up changelog PRs back to main.

Quality

88%

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

85%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 strong validation checkpoints for a batch/destructive operation. Its main weakness is progressive disclosure: everything lives in one ~290-line file with no bundle references to split the detailed changelog-building guidance into.

Suggestions

Move the 'How To Build The Changelog Entry' and 'Dependency update PRs' subsections into a references/ file (e.g. references/changelog-building.md) and link to it from the main flow, so SKILL.md stays a lean overview.

Tighten the 'Important rules' section by merging overlapping concurrency guidance (the go-deep rule, the background-watch rule, and the approval-watch rule share the same rationale) to reduce length without losing the constraints.

Add a short 'Quick reference' table mapping each of the 11 steps to its key command, so the numbered flow can be scanned without reading every bullet.

Dimension	Reasoning	Score
Conciseness	The body is operational substance with no padding of concepts Claude already knows, but at ~290 lines several rules (e.g. the approval-watch loop and amend guidance) could be tightened, keeping it just above the midpoint rather than fully lean.	4 / 5
Actionability	Provides copy-paste-ready git/gh commands, exact commit and tag formats, jq and GraphQL snippets, and concrete edge-case handling, fully covering the common and tricky cases.	5 / 5
Workflow Clarity	An 11-step numbered flow with explicit validation checkpoints (fetch before compare, CI green before merge, verify the bump survived amend, do not declare done until the cherry-pick PR is merged), feedback loops, and a final step-by-step completion checklist for this batch/destructive operation.	5 / 5
Progressive Disclosure	Well-sectioned but entirely monolithic: no references/ scripts/ assets/ bundle files exist, and substantial subsections ('How To Build The Changelog Entry', 'Dependency update PRs') that could live one level deep are inlined in SKILL.md.	3 / 5
	Total	17 / 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 tight, well-scoped description that names the domain, the exact controllers, the concrete actions, and an explicit 'Use when' trigger. Trigger-term coverage is strong for the niche but not exhaustive of synonyms.

Dimension	Reasoning	Score
Specificity	Enumerates the seven supported controllers and lists multiple concrete actions ('drafting changelog entries, tagging releases, and opening the follow-up changelog PRs back to main'), matching the comprehensive-coverage anchor.	5 / 5
Completeness	Explicitly states what ('Run the upstream Flux controller patch release procedure for ...') and when ('Use when preparing a new controller patch release from a release series branch, drafting changelog entries, tagging releases ...'), satisfying the top anchor.	5 / 5
Trigger Term Quality	Natural domain terms like 'patch release', 'changelog entries', 'tagging releases', and 'changelog PRs' are present and what a release engineer would say, but coverage stops short of comprehensive synonyms.	4 / 5
Distinctiveness Conflict Risk	Narrow niche (Flux controller patch releases) with explicit scoping to specific controllers and an in-body exclusion of flux2/pkg, giving minimal conflict risk.	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-patch-releases/SKILL.md
Commit: 88fb00c

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