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.

69

Quality

85%

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 thorough, highly actionable coding-standards skill with executable examples and clear section organization. Its main weakness is mild verbosity in the var and style sections that could be tightened or externalized.

Suggestions

Trim or externalize the multi-page `var` policy into a reference file, keeping only the priority-ordered rules and one example per rule inline.

Fix the unclosed code fence in the 'Magic Numbers' section (line ~348) where the ```csharp block is opened but never closed before the XML Documentation header.

DimensionReasoningScore

Conciseness

Mostly lean and assumes Claude's competence with rule-and-example pairs, though the extensive `var` policy and repeated code examples add some length that could be trimmed without losing clarity.

4 / 5

Actionability

Provides fully executable, copy-paste-ready code examples throughout (var policy, target-typed new, switch expressions, throw helpers, using declarations) covering common cases with explicit GOOD/REQUIRED/DON'T contrasts.

5 / 5

Workflow Clarity

Rules are organized into clear prioritized sections (the 7-step var policy in priority order, distinct topic sections); no destructive/batch workflow requires validation checkpoints, and the single-action guidance is unambiguous with a minor gap in sequencing the file-generation workflow.

4 / 5

Progressive Disclosure

Well-organized topical sections with clear headers and no bundle files needed; content is appropriately self-contained, with only minor opportunity to split the lengthy var/style guidance into a reference file.

4 / 5

Total

17

/

20

Passed

Description

88%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 what it covers and when to use it, with concrete trigger terms tied to new file creation. Minor room for improvement in adding file-extension synonyms and tightening the distinctiveness from sibling skills.

Suggestions

Add file-extension triggers (e.g. '.cs', '.vb') so users searching by extension match this skill.

Name the sibling skills it differentiates from (e.g. 'not for refactoring existing files — use code-modernization') directly in the description to sharpen distinctiveness.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and coverage areas (creating new classes, methods, controls, tests, naming, formatting, XML docs, WinForms, performance idioms) — comprehensive coverage matching the score-5 anchor.

5 / 5

Completeness

Explicitly answers both 'what' (coding standards for generating new code files) and 'when' ('Use when creating new classes, methods, controls, tests, or any new C# / VB source files') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural trigger phrases like 'creating new classes, methods, controls, tests' and 'new C# / VB source files', but lacks some common synonyms or file extensions (e.g. '.cs', '.vb') users might say.

4 / 5

Distinctiveness Conflict Risk

Clearly niched to new C#/.NET code generation in this repository with distinct triggers, with minor overlap risk against the related code-modernization skill it explicitly differentiates from.

4 / 5

Total

18

/

20

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.