Tessl • The management layer for AI agent skills

SkillPublic

csharp-nullable-reference-types

Guidelines for introducing and using nullable reference types (NRT) and System.Diagnostics.CodeAnalysis nullable attributes in C# / .NET codebases. Covers the nullability model, flow analysis, the null-forgiving operator, API design rules, the full attribute catalog (AllowNull, DisallowNull, MaybeNull, NotNull, NotNullWhen, MaybeNullWhen, NotNullIfNotNull, MemberNotNull, MemberNotNullWhen, DoesNotReturn, DoesNotReturnIf), the C# 14 field keyword, incremental migration of legacy codebases, and a code-generation checklist.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/csharp-nullable-reference-types/SKILL.md

Quality

Content

61%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.

The body is actionable and well-structured with concrete code and a clear overview-to-reference split, but it is somewhat verbose where it re-teaches NRT basics and its workflow lacks explicit validation checkpoints. The referenced detail files are also missing from the bundle.

Suggestions

Trim or condense the 'Core Nullability Model' basics that Claude already knows, keeping only the skill-specific rules and edge cases.

Turn the Generation Checklist into an explicit workflow with validation checkpoints (e.g. 'after enabling <Nullable>, build and confirm no new CS86xx warnings before proceeding').

Ensure the referenced files nullable-attributes-reference.md and nrt-migration-playbook-reference.md are actually shipped in the bundle so the one-level-deep navigation resolves.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient but re-explains NRT fundamentals Claude already knows (e.g. "string — non-nullable reference. The compiler assumes instances are never null"), which could be trimmed without losing the skill-specific rules.	3 / 5
Actionability	It provides concrete, executable C# throughout (ArgumentNullException.ThrowIfNull, `field ??= GetPropValue()`, the <Nullable>enable</Nullable> property, guard-pattern examples), with only minor gaps where rules are stated without accompanying code.	4 / 5
Workflow Clarity	The Generation Checklist gives a clear ordered sequence, but it lacks explicit validate→fix→retry checkpoints; warnings handling (item 7) is asserted rather than framed as a feedback loop.	3 / 5
Progressive Disclosure	Structure is good with a dedicated, well-signaled 'Reference Files' section pointing one level deep to two files, but those referenced files (nullable-attributes-reference.md, nrt-migration-playbook-reference.md) are not present in the bundle, slightly weakening navigation.	4 / 5
	Total	14 / 20 Passed

Description

75%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.

The description is specific and clearly scoped to a distinct niche with strong keyword coverage, but it omits any explicit "Use when..." trigger guidance, which caps its completeness. Adding a concrete usage-trigger clause would raise the completeness score.

Suggestions

Add an explicit 'Use when ...' clause naming the situations that should activate this skill (e.g. 'Use when introducing or migrating to nullable reference types, annotating APIs with nullable attributes, or reviewing C# null-state analysis').

Include a few more natural user phrasings such as 'null warnings' or 'CS86xx warnings' to broaden trigger-term coverage.

Lead with the trigger context before the long capability list so the 'when' is as prominent as the 'what'.

Dimension	Reasoning	Score
Specificity	The description enumerates many concrete capabilities — "the nullability model, flow analysis, the null-forgiving operator, API design rules, the full attribute catalog (...), the C# 14 field keyword, incremental migration..., and a code-generation checklist" — giving comprehensive coverage rather than vague language.	5 / 5
Completeness	It clearly states what the skill covers but contains no "Use when..." clause or equivalent explicit trigger guidance, so per the rubric guidelines completeness is capped at 3.	3 / 5
Trigger Term Quality	Natural terms a C# developer would say are present ("nullable reference types", "NRT", "nullable attributes", "C# / .NET"), with synonyms, but a few common natural phrasings (e.g. "null warnings", "NullReferenceException prevention") are absent.	4 / 5
Distinctiveness Conflict Risk	The niche is sharply defined — nullable reference types and System.Diagnostics.CodeAnalysis attributes in C#/.NET — giving distinct triggers and minimal overlap with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 5 missing	Warning

	Total	14 / 16 Passed

Repository: Aaronontheweb/dotnet-skills
Path: skills/csharp-nullable-reference-types/SKILL.md
Revision: 5ca5db8

Reviewed: 1 month ago

Discovery Implementation Validation

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.

csharp-nullable-reference-types

Table of Contents

Is this your skill?