release-readiness

Assesses ship-readiness for .NET MAUI release branches — Servicing Releases (SR) and Previews. Surveys CI pipelines, computes what's actually NEW in the branch (commits + source PRs with revert detection), and cross-references open `regressed-in-*` issues against branch contents to identify port candidates, rejected backports, and unresolved regressions. Supports both in-flight and pre-cut (candidate) modes for SR and Preview branches.

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/release-readiness/SKILL.md

Quality

Content

85%

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

The body is highly actionable and well-sequenced with explicit validation checkpoints and clean one-level-deep progressive disclosure; its main weakness is verbosity in the Preview-specific sections, where rationale and cross-reference scaffolding could be trimmed.

Suggestions

Tighten the "Preview: authoritative blessed-build source" and "is the branch actually plumbed" sections by moving more of the access-tier narrative into dependency-flow and keeping only the decision branch + one-line outcomes inline.

Collapse the "Don't maintain a standing table" paragraph into a one-line rule to reduce rationale prose that restates the CI body's behavior.

Dimension	Reasoning	Score
Conciseness	The ~440-line body is dense with genuinely necessary domain-specific knowledge (tag-existence rule, no-preview8 cadence, BAR feed/Assessment workflow) rather than concepts Claude already knows, but the Preview blessed-build and subscription-wiring sections contain rationale prose and repeated cross-reference scaffolding that could be tightened.	2 / 3
Actionability	Provides fully executable, copy-paste-ready commands throughout — complete pwsh invocations with parameters, `gh issue list` queries, git/cherry-pick commands, and a concrete `PatchVersion` diff example with exact PR titles.	3 / 3
Workflow Clarity	Multi-step processes are clearly sequenced (detect-trackers → per-tracker-report → validate) with explicit checkpoints — an activity gate, idempotent body-hash refresh/create paths, error-recovery fallbacks (conflict → manual `git cherry-pick -x`), and tabular checklists (ship-readiness checks, verdict classification).	3 / 3
Progressive Disclosure	Well-structured overview with one-level-deep references that are real and clearly signaled — [references/methodology.md](references/methodology.md) for the gotchas and sibling skills (dependency-flow, find-regression-risk, azdo-build-investigator) for their specialized mechanics, avoiding duplication; scripts are listed and linked.	3 / 3
	Total	11 / 12 Passed

Description

67%

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 specific, actionable, and clearly niche-scoped, but it omits an explicit "Use when..." trigger clause and leans on technical jargon rather than natural user phrasing, capping completeness and trigger-term quality at 2.

Suggestions

Append an explicit trigger clause, e.g. "Use when asked whether a .NET MAUI SR or Preview branch is ready to ship, what's new in a release, or which regression fixes to backport."

Soften jargon with a couple of natural user utterances ("Is SR8 ready to ship?", "What's new in preview6?") so trigger-term quality reflects how users actually ask.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Surveys CI pipelines", "computes what's actually NEW in the branch (commits + source PRs with revert detection)", "cross-references open regressed-in-* issues" to identify port candidates, rejected backports, and unresolved regressions.	3 / 3
Completeness	Strongly answers "what" (assess ship-readiness, survey CI, compute NEW, cross-reference regressions) but provides no explicit "Use when..." clause; the "when" is only implied from domain context, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Covers relevant domain terms a release captain would say ("ship-readiness", "Servicing Releases (SR)", "Previews", "backports", "regressed-in-*"), but the phrasing is jargon-dense and lacks the natural question-style utterances (e.g. "Is SR8 ready to ship?") that appear only in the body.	2 / 3
Distinctiveness Conflict Risk	Highly specific niche (".NET MAUI release branches — Servicing Releases (SR) and Previews", "regressed-in-* issues", "candidate modes") with distinct triggers unlikely to fire for an unrelated skill; the body further disambiguates from find-regression-risk.	3 / 3
	Total	10 / 12 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 missing, 6 suspicious	Warning

	Total	15 / 16 Passed

Repository: dotnet/maui
Path: .github/skills/release-readiness/SKILL.md
Commit: 6a24ec5

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.