CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

70%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.

The body delivers exceptional actionability and clearly sequenced, validation-rich workflows for a complex report-only domain, with accurate references to real bundle files. Its main weaknesses are token efficiency — a ~763-line body with repeated rationale and version-specific narrative — and progressive disclosure, since parameter references and operational-lifecycle detail that belong in reference files are inlined rather than split out.

Suggestions

Move the full parameter tables for Get-ReleaseReadiness.ps1 and Get-PreviewReadiness.ps1 into references/parameters.md, keeping only required parameters and one example invocation per mode in SKILL.md.

Relocate the shipped/hotfix lifecycle and create-once semantics, the NightlyFeed module internals, and the tag-existence edge cases into references/methodology.md (or a new references/lifecycle.md), leaving a short summary plus pointer per topic.

Consolidate the repeated fail-open/public-safe caveats into a single section and isolate version-specific examples (SR8/SR9, preview6, PR numbers) into a clearly labeled historical-examples section so mainline guidance stays lean.

DimensionReasoningScore

Conciseness

The ~763-line body is noticeably verbose: long narrative paragraphs on shipped/hotfix lifecycle semantics, NightlyFeed banner internals, and candidate-integration workflow rationale repeat fail-open and create-once semantics several times, and time-sensitive specifics (SR8/SR9/preview6, definition 1095, PR #35433/#35879) are woven through main sections rather than isolated. It is not a 1 because there is no padding with concepts Claude already knows — the density is domain-specific — but it clearly falls in 'several unnecessary explanations or padded sections' territory rather than merely 'could be tightened'.

2 / 5

Actionability

Fully executable, copy-paste-ready guidance throughout: complete pwsh invocations with real flags for every entry point, a working gh+jq tracker-search command, a PAT-provisioning bash sequence with credential hygiene (read -s, unset), diff examples for the PatchVersion bump, and per-parameter tables. Common cases (SR in-flight, SR candidate, Preview in-flight/candidate, RC, handoff) are each covered by a concrete example.

5 / 5

Workflow Clarity

Multi-step processes are explicitly sequenced with validation checkpoints: the PAT flow (create → set env var → run → unset), the five-step prerelease action ordering, the numbered tracker-refresh workflow with its 'validate' PR gate that 'Does not create or modify issues', and explicit error-recovery guidance (failed-or-stale build handling, fetch-instruction failures instead of silently empty trackers). The skill is report-only and encodes refusal boundaries for risky operations, and tests are listed. Not a 4: checkpoints and feedback loops (validate → fix → re-validate, smoke-diagnostic NOT RUN handling) are explicit, not implicit.

5 / 5

Progressive Disclosure

Structure and navigation are good (clear headers, anchor links, both references/methodology.md and references/release-handoff.md exist and are well signaled with inline summaries), and references are one level deep. However, the vast majority of detail — full parameter tables, tag-existence lifecycle semantics, NightlyFeed module documentation, nightly-lane rules — is inlined in SKILL.md when it clearly belongs in reference files; this matches 'content that should be separate is inline' better than the 'most content is appropriately placed' 4 anchor.

3 / 5

Total

15

/

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 description: third-person voice, concrete capability statements, and an explicit 'Use for' clause with natural trigger phrases including a quoted user-style request. The only weakness is that a few common natural phrasings (e.g. 'ready to ship', 'is SR8 ready') that the body's 'When to Use' section covers are absent from the description itself.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'Assesses ship-readiness for .NET MAUI release branches', 'produces public-safe, copy-ready release handoffs or Loop-page drafts', 'Surveys CI and release delta, classifies regressions' — comprehensively covering what the skill does. It is not below the 4 anchor because coverage of the skill's capabilities (verdicts, regression classification, handoff generation) is complete rather than having minor gaps.

5 / 5

Completeness

Both 'what' (assesses ship-readiness for SR and Preview branches, surveys CI and release delta, classifies regressions, produces release handoffs) and 'when' are explicitly and clearly answered via the 'Use for readiness verdicts, release blockers, Preview/SR status, release handoff pages, manual validation instructions, or "make the SR10/Preview N release page."' clause with concrete trigger phrases. Not a 4 because the 'when' is already explicit and specific, not merely present.

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'readiness verdicts', 'release blockers', 'Preview/SR status', 'release handoff pages', 'manual validation instructions', and the quoted user phrasing "make the SR10/Preview N release page". A few natural variants users would say are missing (e.g. 'ready to ship', 'is SR8 ready', 'regression backport'), keeping it just below the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The niche is highly specific — .NET MAUI Servicing Releases (SR) and Previews on dotnet/maui release branches — with distinct triggers (SR/Preview status, release handoff pages) that no generic skill would claim. Minimal conflict risk with closely related skills; the body even disambiguates against find-regression-risk.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (773 lines); consider splitting into references/ and linking

Warning

relative_links

Relative link issues: 1 missing, 4 suspicious

Warning

Total

14

/

16

Passed

Repository

dotnet/maui

Path

.github/skills/release-readiness/SKILL.md

Reviewed

Table of Contents

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.