CtrlK
BlogDocsLog inGet started
Tessl Logo

code-modernization

Instructions for modernizing and refactoring existing C# / VB.NET code files. Use when asked to refactor, modernize, clean up, review, or improve existing source files in this repository. Covers upgrading to C# 14 / .NET 10 idioms, comment quality, spelling and grammar fixes, XML documentation, and readability improvements.

67

Quality

81%

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

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 highly actionable, well-organized refactoring reference with strong before/after examples and a safety-first golden rule. The main weakness is progressive disclosure: a large monolithic file that could benefit from splitting stable detail into reference bundles.

Suggestions

Move large stable sections (e.g., the full var policy, XML documentation examples, WinForms-specific modernization) into reference files under references/ and link to them from SKILL.md to improve progressive disclosure.

Add an explicit validate->fix->retry feedback loop (e.g., build/test after modernization, revert on failure) to lift workflow clarity for risky transformations.

Trim minor justificatory prose where the before/after example already makes the rule self-evident.

DimensionReasoningScore

Conciseness

The body is a dense, reference-style ruleset that assumes Claude knows C# and avoids explaining basic concepts, with only minor justificatory prose (e.g., the rationale for `is null`) that could be trimmed.

4 / 5

Actionability

It provides extensive copy-paste-ready before/after C# examples covering the common modernization cases, plus a concrete final checklist, giving fully executable guidance.

5 / 5

Workflow Clarity

A clear sequence exists (scope/safety gate, transformation rules, final Refactoring Checklist) with the golden rule acting as a confidence checkpoint, but there is no explicit validate->fix->retry feedback loop for risky transformations.

4 / 5

Progressive Disclosure

The file is well-sectioned with clear headers, but at ~530 lines it is a single monolithic document with no bundle files; distinct sub-domains (WinForms-specific, XML docs, the var policy) could be split into one-level-deep reference files for better progressive disclosure.

3 / 5

Total

16

/

20

Passed

Description

83%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, specific description that clearly states both purpose and trigger conditions with natural user vocabulary. Minor room for improvement in adding synonyms and file extensions to lock in trigger matching and reduce overlap.

Suggestions

Add file extensions and synonyms (e.g., ".cs, .vb files") to the trigger clause to reach comprehensive keyword coverage.

Narrow the "review" trigger (e.g., "review for modernization opportunities") to reduce overlap with general code-review skills.

DimensionReasoningScore

Specificity

Lists several specific coverage areas ("upgrading to C# 14 / .NET 10 idioms, comment quality, spelling and grammar fixes, XML documentation, and readability improvements") rather than vague actions, though these are topical areas rather than discrete concrete actions, leaving minor gaps versus the comprehensive anchor.

4 / 5

Completeness

It explicitly answers both what ("Instructions for modernizing and refactoring existing C# / VB.NET code files... Covers...") and when ("Use when asked to refactor, modernize, clean up, review, or improve existing source files") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural user-facing verbs are well covered ("refactor, modernize, clean up, review, or improve"), but synonyms and file extensions (.cs, .vb) are missing, so it does not reach comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

The C# / VB.NET modernization niche is clearly distinct, but the trigger term "review" and general refactoring overlap slightly with code-review or coding-standards skills, so it is mostly distinct rather than minimal-conflict.

4 / 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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

Total

15

/

16

Passed

Repository
dotnet/winforms
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.