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.

68

Quality

82%

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

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is highly actionable and well organized, with excellent concrete examples and a verification checklist. Its main weaknesses are length/conciseness and the lack of progressive disclosure via separate reference files or a validation feedback loop.

Suggestions

Move the detailed var policy and XML documentation guidance into reference files (e.g. references/var-policy.md, references/xml-docs.md) and keep SKILL.md as a leaner overview with one-level-deep links, improving both conciseness and progressive disclosure.

Add an explicit validate-fix-retry loop for batch modernization (e.g. run dotnet build/format after changes, fix reported issues, re-run) to lift workflow clarity past 2.

Trim redundant before/after examples where a single representative example already conveys the rule, to reduce token cost without losing actionability.

DimensionReasoningScore

Conciseness

The body is a dense, mostly fluff-free rules catalogue, but at ~520 lines with many repeated before/after examples it is longer than necessary and several sections could be tightened without losing clarity.

2 / 3

Actionability

Provides concrete, executable before/after code, rules in explicit priority order, named throw helpers, and exact thresholds (e.g. '60 characters'), all copy-paste ready.

3 / 3

Workflow Clarity

A strong 'Refactoring Checklist' with verification checkboxes plus a 'Golden rule' safety checkpoint gives a clear sequence, but there is no validate-fix-retry feedback loop for what is effectively batch/destructive file editing, capping this dimension.

2 / 3

Progressive Disclosure

No bundle files exist and the content is a single ~520-line monolith; it is well sectioned but substantial material (var policy, XML doc guide) that could be split into references remains inline.

2 / 3

Total

9

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise, third-person, and fully covers both capabilities and explicit 'Use when' triggers. It is specific to its domain and unlikely to conflict with other skills. No improvements needed.

DimensionReasoningScore

Specificity

Names multiple concrete actions ('modernizing and refactoring', 'comment quality', 'spelling and grammar fixes', 'XML documentation', 'readability improvements'), matching the multi-specific-action anchor.

3 / 3

Completeness

Explicitly answers both what (modernizing/refactoring C#/VB.NET files) and when ('Use when asked to refactor, modernize, clean up, review, or improve existing source files'), with an explicit trigger clause.

3 / 3

Trigger Term Quality

Uses natural verbs a user would say ('refactor, modernize, clean up, review, or improve') with good coverage of common phrasings rather than jargon.

3 / 3

Distinctiveness Conflict Risk

Scoped narrowly to C#/VB.NET existing-file modernization and explicitly distinguished from new-file generation, giving it a clear niche unlikely to fire for the wrong skill.

3 / 3

Total

12

/

12

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.