Name: update-os-coverage
Rating: 72.8 (1 reviews)
Author: dotnet

update-os-coverage

Update OS version references in Helix queue definitions to add new versions, replace EOL versions, or audit coverage against the supported-os matrix. USE FOR: adding new OS versions to Helix queues, replacing EOL OS versions, upgrading "oldest" or "latest" version references, auditing Helix coverage. DO NOT USE FOR: creating new container images (that's dotnet-buildtools-prereqs-docker), updating supported-os.json (that's the update-supported-os skill in dotnet/core).

Quality

90%

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

88%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 thorough, highly actionable operational skill with concrete commands, exact naming tables, and a well-validated multi-step workflow. The main weaknesses are mild verbosity in the When-to-use sections and a monolithic structure that does not leverage separate reference files.

Suggestions

Trim the 'When to use' / 'When NOT to use' body sections where they restate the frontmatter description to reduce token cost.

Consider moving the large CI-pipeline-coverage tables (step 6) and the naming-convention table into a references/ file linked from SKILL.md to improve progressive disclosure.

Add one fully-worked end-to-end example with concrete values filled in (e.g., a complete Fedora 43→44 replacement walkthrough) to anchor the parameterized commands.

Dimension	Reasoning	Score
Conciseness	Mostly efficient concrete tables and copy-paste commands with domain context Claude would not know (November release cadence, in-flux image-info transition), but some 'When to use' prose duplicates the frontmatter and a few explanatory paragraphs could be trimmed.	4 / 5
Actionability	Fully executable curl/jq/grep/gh/git commands with exact naming-convention tables (Alpine, Debian, Fedora, etc.) and a worked audit example table, covering the common cases in copy-paste-ready form.	5 / 5
Workflow Clarity	A clear 9-step sequence with an explicit validation checklist (step 5: no stale references, syntactic consistency, tag existence, unchanged variable names), a re-run-grep feedback loop, and a stop-and-inform guard for missing image tags — the batch operation has validation so it is not capped.	5 / 5
Progressive Disclosure	Well-organized sections with a clearly signaled ## Reference list of external links, but the skill is a monolithic single SKILL.md with no bundle files, so content is not split across one-level-deep reference files as the top anchor describes.	4 / 5
	Total	18 / 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 highly specific, well-triggered description that clearly states what the skill does, when to use it, and where its boundaries are relative to neighboring skills. The only minor gap is trigger-term synonym breadth, which keeps it just below a perfect trigger_term_quality score.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'add new versions, replace EOL versions, or audit coverage against the supported-os matrix' plus a USE FOR list of four distinct operations, giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers 'what' (update OS version references in Helix queue definitions) and 'when' via a concrete USE FOR clause with trigger phrases, plus a DO NOT USE FOR boundary — matching the top anchor.	5 / 5
Trigger Term Quality	Strong natural domain terms ('EOL OS versions', 'oldest'/'latest' version references', 'auditing Helix coverage') that users would plausibly say, but not quite the exhaustive synonym/file-extension coverage of the top anchor.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (OS version references in Helix queue definitions) and explicitly disambiguates from sibling skills ('that's dotnet-buildtools-prereqs-docker', 'that's the update-supported-os skill in dotnet/core'), minimizing conflict risk.	5 / 5
	Total	19 / 20 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: 2 suspicious	Warning

	Total	15 / 16 Passed

Repository: dotnet/runtime
Path: .github/skills/update-os-coverage/SKILL.md
Commit: b030ed4

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