release-readiness

Assesses ship-readiness for .NET MAUI release branches — Servicing Releases (SR) and Previews — and produces public-safe, copy-ready release handoffs or Loop-page drafts from the resulting evidence. Use for readiness verdicts, release blockers, Preview/SR status, release handoff pages, manual validation instructions, or "make the SR10/Preview N release page." Surveys CI and release delta, classifies regressions, and keeps Preview and servicing semantics distinct.

Quality

86%

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

81%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-structured skill body with concrete commands and clearly sequenced, validated workflows backed by real bundle files. Its main weakness is conciseness: the ~650-line body restates several concepts and inlines detail that could be trimmed or moved to references.

Suggestions

Consolidate the repeated explanations of the tag-existence rule, shipped/hotfix lifecycle, and blessed-build handling into a single authoritative passage to reduce restatement across sections.

Move the full ship-readiness checks table and the extended blessed-build/subscription/plumbing sections into a reference file, leaving SKILL.md as a tighter overview that points to them.

Tighten the long 'Don't maintain a standing table' paragraph and similar prose-heavy passages to their essential rule plus a one-line rationale.

Dimension	Reasoning	Score
Conciseness	Mostly high-signal, non-obvious domain knowledge that Claude would not already know, but several concepts are restated across sections (tag-existence rule, shipped/hotfix lifecycle, blessed-build handling) and the ~650-line body could be tightened without losing clarity.	3 / 5
Actionability	Copy-paste ready throughout — concrete pwsh/bash commands with real flags, full parameter and output tables, exact '/backport to release/...' command strings, verbatim diff blocks, and exact gh/jq queries covering the common cases.	5 / 5
Workflow Clarity	Multi-step processes are clearly sequenced with explicit validation checkpoints and feedback loops (tracker refresh detect→per-tracker→validate, dependency-ordered Preview action ordering, re-run-after-merge backport flow, fail-open unknown/blocked gating); the skill's report-only stance means the destructive-cap does not apply.	5 / 5
Progressive Disclosure	Good structure with a clear overview (Architecture table, Quick Start) and well-signaled one-level-deep references to real bundle files (references/methodology.md, references/release-handoff.md, scripts/*.ps1) plus sibling-skill cross-references, but large amounts of detail (full ship-readiness checks table, blessed-build/subscription/plumbing sections) are inlined rather than offloaded.	4 / 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 strong, third-person description that concretely states what the skill does and when to use it with natural trigger phrases, occupying a clearly distinct niche. It is slightly below a perfect trigger-term score only because a couple of natural phrasings appear in the body rather than the description itself.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Assesses ship-readiness', 'produces public-safe, copy-ready release handoffs or Loop-page drafts', 'Surveys CI and release delta, classifies regressions', and 'keeps Preview and servicing semantics distinct' — giving comprehensive coverage of the skill's purpose.	5 / 5
Completeness	Explicitly answers both 'what' (assesses readiness, produces handoffs/drafts, surveys CI, classifies regressions) and 'when' ('Use for readiness verdicts, release blockers, Preview/SR status...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural trigger coverage including the imperative command form 'make the SR10/Preview N release page' plus a 'Use for' list (readiness verdicts, release blockers, Preview/SR status, handoff pages), though a few natural phrasings like 'is X ready to ship' live only in the body rather than the description.	4 / 5
Distinctiveness Conflict Risk	A clear, narrow niche (.NET MAUI release branches, SR vs Preview semantics, release handoffs/Loop drafts) with distinct triggers and minimal conflict risk; the body even deflects the adjacent regression-risk question to a sibling 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
skill_md_line_count	SKILL.md is long (653 lines); consider splitting into references/ and linking	Warning
relative_links	Relative link issues: 1 missing, 6 suspicious	Warning

	Total	14 / 16 Passed

Repository: dotnet/maui
Path: .github/skills/release-readiness/SKILL.md
Commit: 90afade

Reviewed: ~18 hours 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.