CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

roll-forward-csharp-whats-new

Rolls the three-release C# What's new window forward. Use after a confirmed annual C# GA release to preserve release history, move the older What's new article into history, repair links and redirects, and remove stale introductory version framing without erasing compatibility requirements. Older C# language features remain supported; only their new framing changes.

Quality

88%

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

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 well-sequenced, carefully guarded workflow skill: scope control, repository-wide inventory, semantic version-mention classification, and a genuinely thorough validation phase with feedback loops. Its main gaps are minor — no executable command examples, some compressible prose, and all detail inlined in one file rather than split into references.

Suggestions

Add one or two concrete command examples (e.g., a representative grep pattern for the normalized all-C#-mentions sweep, or the exact lint command to run) so the validation phase is copy-paste ready rather than described.

Move the search-phrase catalogue ("new in", "introduced", "added", "available", "starting with", ...) and the version-mention retention categories into a reference file, keeping SKILL.md as a tighter overview.

Tighten the duplicate compatibility statement (body intro restates the description's "Older C# language features remain supported") and compress the longest sentences in the Inventory section.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence — it never explains what C# or redirects are, and lines like "Previews don't count toward the three GA releases" earn their tokens. Minor trimming is possible: the older-features-stay-supported point is stated twice (body intro and description), and sentences like the normalized-search instruction are long enough to compress. Efficient overall, so score 4 rather than the lean 5 or the noticeably padded 3.

4 / 5

Actionability

Guidance is concrete for an instruction-only skill: exact paths (docs/csharp/whats-new/, .openpublishing.redirection.csharp.json, toc.yml), an exact redirect destination format ("/dotnet/csharp/whats-new/csharp-version-history" plus fragment), named search forms (escaped C\#, HTML entities, spelled-out versions), and explicit validation targets. Per the rubric's code-vs-instruction note, absent code is not penalized, but no actual commands are supplied ("Use available repository tooling", no example grep pattern or lint invocation), leaving minor gaps that keep it below copy-paste-ready.

4 / 5

Workflow Clarity

A clear seven-phase sequence (Confirm scope → Locate → Inventory → Move → Review → Validate → Hand off) with a full validation checklist for this destructive/batch operation: parse redirect JSON for uniqueness and sort order, parse owning YAML, repeat caller sweeps, real path-and-fragment link checks, lint, whitespace, full diff review. Feedback loops are explicit ("repair unresolved live callers", re-run the all-C#-mentions sweep, "If evidence doesn't settle the distinction, retain the text and report the uncertainty"). This matches the anchor for explicit validation steps with error-recovery loops; the destructive-operation cap does not apply because validation is thorough.

5 / 5

Progressive Disclosure

Well-organized sections with clearly signaled one-level-deep references to companion skills ("[Redirect article](../redirect-article/SKILL.md) owns article deletion... through its existing script") and explicit repo-relative paths, and it correctly delegates rather than duplicating their scripts. However, it is an ~84-line single file that inlines everything — the search-phrase catalogue and the detailed validation checklist could live in reference files — which sits between the well-placed-4 and the ideal split-5 anchors rather than clearly at either.

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: it names the precise domain operation, enumerates the concrete actions involved, and gives an explicit 'Use after a confirmed annual C# GA release' trigger with a clear compatibility boundary. Keyword coverage is good but could add a few natural synonyms (.NET docs, language version) users might say.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "preserve release history", "move the older What's new article into history", "repair links and redirects", "remove stale introductory version framing" — covering the workflow comprehensively, matching the anchor for multiple specific concrete actions. It does not merely name the domain like the score-3/4 anchors; no action is generic.

5 / 5

Completeness

It explicitly answers both: what ("Rolls the three-release C# What's new window forward... preserve release history, move the older What's new article into history, repair links and redirects, and remove stale introductory version framing") and when ("Use after a confirmed annual C# GA release") with a concrete trigger. This matches the anchor for clearly and explicitly answering both with concrete trigger phrases; the 'Use...' clause avoids the completeness cap.

5 / 5

Trigger Term Quality

Natural phrases a maintainer would say are present ("C# What's new", "GA release", "release history", "redirects", "links"), giving good keyword coverage. A few natural terms are missing (e.g., ".NET docs", "Microsoft Learn", "language version"), so it falls just short of the comprehensive synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

"Rolls the three-release C# What's new window forward... after a confirmed annual C# GA release" carves out a clear niche (annual What's new window maintenance) with distinct triggers that would not fire for general C# documentation or redirect work. Third-person voice ("Rolls") is used correctly, so no specificity penalty applies.

5 / 5

Total

19

/

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

relative_links

Relative link issues: 9 suspicious

Warning

Total

15

/

16

Passed

Repository

dotnet/docs

Path

.github/skills/roll-forward-csharp-whats-new/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.