CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

70

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

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.

The body is exceptionally actionable and workflow-safe — copy-paste commands, explicit gates, and ordered sequences throughout — with genuine progressive-disclosure discipline (real one-level references, no duplication of sibling-skill content). Its one real weakness is token efficiency: several inlined sections hedge and repeat well past what the guidance needs.

Suggestions

Move the NightlyFeed.ps1 function-by-function table and the shipped-mode/hotfix lifecycle prose into references/methodology.md (or a new reference), keeping only the banner's meaning and the ❌-feed pointer in SKILL.md.

Tighten the tracker-refresh and post-ship-lifecycle paragraphs by cutting repeated caveats (e.g. the create-once/idempotency rules are stated three times in different words); state each rule once.

Trim the buffered build-candidate discovery prose to the classification outcome (red / partial-success / stale / in-progress / unknown plus failed-or-stale) and move the acceptance/skip heuristics into the script's own docs or a reference.

DimensionReasoningScore

Conciseness

The 665-line body is mostly non-obvious domain knowledge Claude cannot know (tag-existence rule, hotfix lifecycle, no-preview8 cadence), so it avoids score-1/2 padding — but passages like the post-ship lifecycle, buffered build-candidate semantics, the NightlyFeed function table, and tracker-issue refresh rules are hedged and restated well past necessity and could be tightened or moved to references. Fits "mostly efficient but includes some unnecessary explanation or could be tightened" rather than 4's "minor instances".

3 / 5

Actionability

Fully executable, copy-paste-ready guidance throughout: concrete pwsh invocations with real parameter values for every mode, PAT provisioning via read -s/export/unset, the jq tracker-marker filter, the exact PatchVersion diff, and complete per-script parameter tables. Not 4: specific examples cover the common cases with no gaps.

5 / 5

Workflow Clarity

Multi-step processes are clearly sequenced with explicit validation checkpoints and error-recovery guidance: the numbered prerelease action ordering, the 4-step authenticated-feed procedure with credential cleanup, the installability gate table (installable/missing/mismatched/unknown → READY/BLOCKED/UNKNOWN), and fail-open/UNKNOWN-instead-of-guess rules. The skill is report-only, so the destructive-batch cap does not apply.

5 / 5

Progressive Disclosure

References (references/methodology.md, references/release-handoff.md) are real files, one level deep, and clearly signaled at point of use; sibling-skill detail is cross-linked rather than duplicated. Not 5: substantial detail — NightlyFeed internals, shipped-mode lifecycle semantics, workflow refresh mechanics, full parameter tables — is inlined in SKILL.md where a leaner overview pointing into references would fit better.

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 description: third-person, concrete about capabilities, with an explicit "Use for" clause containing natural quoted trigger phrases. Only minor headroom in synonym coverage of user phrasings.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — "Assesses ship-readiness", "produces public-safe, copy-ready release handoffs or Loop-page drafts", "Surveys CI and release delta, classifies regressions" — with comprehensive coverage of the skill's scope. Not 4: no meaningful action in scope is missing.

5 / 5

Completeness

Explicitly answers both what ("Assesses ship-readiness for .NET MAUI release branches — Servicing Releases (SR) and Previews — and produces public-safe, copy-ready release handoffs") and when ("Use for readiness verdicts, release blockers, Preview/SR status… or 'make the SR10/Preview N release page'") with concrete trigger phrases, mirroring the anchor-5 example's structure.

5 / 5

Trigger Term Quality

Good natural coverage — "readiness verdicts", "release blockers", "Preview/SR status", "release handoff pages", "make the SR10/Preview N release page" — matching phrases users would actually say. Not 5: a few common synonyms/verbatim phrasings (e.g. "is SR8 ready to ship", "release notes", "ship readiness") are absent; not 3: coverage goes well beyond a couple of generic keywords.

4 / 5

Distinctiveness Conflict Risk

Clear niche (.NET MAUI SR/Preview release branches) with distinct triggers and minimal conflict risk — the SR/Preview vocabulary is unlikely to fire a generic skill. Not 4: the domain scoping leaves no realistic overlap with unrelated skills.

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 (665 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
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.