CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dotnet-release-ga

Reviews .NET documentation for a new major release that has reached general availability. Use to remove stale release-stage labels while preserving valid preview references, and to review updateeachrelease articles.

Quality

82%

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

78%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 well-structured, actionable editing policy with a strong classification table and thorough validation stage. Its only weaknesses are mild redundancy in the preservation rules and the absence of an explicit fix-and-retry loop and concrete commands, which keep conciseness, actionability, and workflow clarity at 4.

DimensionReasoningScore

Conciseness

The body is dense policy guidance with no padding or explanations of concepts Claude already knows, and every section carries decision content. Minor tightening is possible: the preserve/revert rule recurs across the intro, the classification table, step 4.4, and step 5.5, which is slightly redundant. This matches anchor 4 (efficient, minor instances that could be trimmed) better than 3, since the repetition appears in distinct functional contexts rather than being unnecessary explanation.

4 / 5

Actionability

Gives concrete, executable guidance for an instruction-only skill: exact search targets ('the release's version numbers and status terms', 'ms.custom: updateeachrelease'), a six-row classification decision table keyed to specific reference types, and explicit edit rules ('use a specific version rather than replacing it with a placeholder'). It falls short of anchor 5 because no concrete search/lint commands are given ('Run the narrowest existing lint... command' is directive but not copy-paste ready).

4 / 5

Workflow Clarity

A clear five-stage sequence (confirm status/scope, inventory, classify, edit, validate) with a dedicated validation stage containing five explicit checks and a completion-report checklist, plus uncertainty handling ('leave it unchanged and ask for clarification rather than guessing'). It matches anchor 4 rather than 5 because there is no explicit error-recovery feedback loop (e.g., 'if lint fails, fix and re-run') after validation — a minor gap for a batch-editing operation.

4 / 5

Progressive Disclosure

The skill is a self-contained ~78-line body with no bundle files, organized under clear headers (Required Inputs, Workflow steps 1-5, Completion Report). Nothing belongs in separate files — the policy is cohesive and splitting it would hurt navigation — and there are no buried or nested references, matching the anchor for clear, easy-to-navigate structure.

5 / 5

Total

17

/

20

Passed

Description

78%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 that clearly states what the skill does, includes explicit trigger guidance, and carves out a distinct niche with domain-specific terms like 'updateeachrelease'. It falls just short of top marks on trigger-term breadth and situational 'when' phrasing.

DimensionReasoningScore

Specificity

Names the domain ('Reviews .NET documentation for a new major release that has reached general availability') and lists three concrete actions: 'remove stale release-stage labels', 'preserving valid preview references', and 'review updateeachrelease articles'. This matches anchor 4 (several specific actions, minor gaps) rather than 5, since coverage of the full workflow (e.g., GA status verification, validation) is not present.

4 / 5

Completeness

The 'what' is explicit (reviews .NET documentation for a GA release, remove stale labels, preserve valid previews, review updateeachrelease articles) and an explicit trigger clause is present ('Use to remove stale release-stage labels...'), so the completeness cap of 3 for missing trigger guidance does not apply. The 'when' identifies tasks rather than user situations, so it is not as concrete as anchor 5's 'when the user mentions...' phrasing.

4 / 5

Trigger Term Quality

Includes natural domain terms users would say: '.NET', 'documentation', 'release', 'general availability', 'preview', and the distinctive 'updateeachrelease'. A few common variants are missing ('GA', 'prerelease', 'RC', version-specific phrasing like '.NET 10'), which fits anchor 4 (good coverage, a few natural terms missing) rather than 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The description occupies a clear niche: .NET documentation GA-release passes with the repo-specific 'updateeachrelease' tag. Triggers ('general availability', 'updateeachrelease', 'release-stage labels') are unlike any generic skill's, so conflict risk is minimal, matching anchor 5.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

dotnet/docs

Path

.github/skills/dotnet-release-ga/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.