CtrlK
BlogDocsLog inGet started
Tessl Logo

coding-standards

C# and .NET coding standards for generating new code files. Use when creating new classes, methods, controls, tests, or any new C# / VB source files in this repository. Covers C# 14 / .NET 10 patterns, naming, formatting, XML docs, WinForms conventions, and performance idioms.

72

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

77%

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

A dense, executable coding-standards reference with strong actionability and clear priority-ordered rules. Its weaknesses are length/verbosity and a monolithic structure with no progressive disclosure.

Suggestions

Split large topical blocks (e.g. the `var` policy and WinForms-specifics) into one-level-deep reference files referenced from SKILL.md to improve progressive disclosure.

Tighten the `var` policy by collapsing the seven numbered rules and redundant before/after code blocks into a compact decision table.

Trim illustrative code blocks to the minimal example that demonstrates each rule, reducing token load without losing actionability.

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows and is mostly lean rules-plus-examples, but at ~415 lines it is verbose — the seven-rule `var` policy and extensive code blocks could be trimmed without losing clarity.

2 / 3

Actionability

Highly actionable: nearly every rule is paired with concrete, copy-paste-ready C# examples (e.g. throw-helpers, expression-bodied wrapping, collection expressions, designer Dispose pattern).

3 / 3

Workflow Clarity

As a single-purpose reference skill the action is unambiguous, and the `var` policy is explicitly sequenced 'in priority order'; the simple-skills note permits a 3 here since no multi-step destructive workflow requires validation checkpoints.

3 / 3

Progressive Disclosure

Content is well sectioned with headers, but it is a single monolithic ~415-line file with no bundle files or one-level-deep references; material such as the detailed `var` policy or WinForms specifics that could live in separate reference files is all inline.

2 / 3

Total

10

/

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.

A tight, third-person description that states concrete capabilities and gives an explicit 'Use when' trigger scoped to the repository. It is clearly distinguishable from sibling skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and topics — 'generating new code files', 'creating new classes, methods, controls, tests', plus 'C# 14 / .NET 10 patterns, naming, formatting, XML docs, WinForms conventions, and performance idioms'.

3 / 3

Completeness

Explicitly answers both 'what' (C#/.NET coding standards covering named topics) and 'when' via a clear 'Use when creating new classes, methods, controls, tests, or any new C# / VB source files in this repository' clause.

3 / 3

Trigger Term Quality

Natural terms a user would say are well covered: 'creating new classes, methods, controls, tests', 'new C# / VB source files'. Not merely technical jargon — these are phrasings users actually use.

3 / 3

Distinctiveness Conflict Risk

Niche is sharply bounded — C#/.NET new-code-generation standards scoped to this repository, even disambiguating from a 'code-modernization' skill. Unlikely to trigger for unrelated work.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.