dotnet-patterns

Idiomatic C# and .NET patterns, conventions, dependency injection, async/await, and best practices for building robust, maintainable .NET applications.

Quality

68%

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/dotnet-patterns/SKILL.md

The canonical home for this skill is tdg-personal/dotnet-patterns

Quality

Content

80%

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

The content is exceptionally actionable and token-efficient, with executable, copy-paste-ready C# throughout and no concept-explaining fluff. Its weaknesses are structural: it is a monolithic single-file reference with no progressive disclosure or validation/feedback workflow for risky operations.

Suggestions

Split detailed pattern catalogs (e.g. repository, middleware, minimal APIs) into reference files and keep SKILL.md as an overview with one-level-deep links.

Add validation/verification guidance for operations that mutate state or persist data (e.g. SaveChangesAsync, repository AddAsync) to support feedback loops.

If kept as a single reference file, add a brief table of contents or cross-links so the reader can navigate the 12+ sections.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: each section is a brief framing line followed directly by executable code, with no padding or explanation of basic programming concepts.	3 / 3
Actionability	Every section provides fully executable, copy-paste-ready C# with good/bad contrasts and concrete DI registration calls, leaving no ambiguity about what to do.	3 / 3
Workflow Clarity	Sections are well organized, but this is a patterns reference rather than a sequenced workflow; there are no validation checkpoints or feedback loops, and batch/risky operations like AddAsync lack verification guidance, capping clarity at 2.	2 / 3
Progressive Disclosure	All content sits in a single ~320-line monolithic SKILL.md with no bundle files or references to split it out; sections are clearly labeled, but the monolithic structure and absence of navigation keep it at 2.	2 / 3
	Total	10 / 12 Passed

Description

57%

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 clear and well-targeted to the .NET/C# niche with good keyword coverage, but it omits any explicit "when to use" trigger guidance and frames capabilities as topics rather than concrete actions.

Suggestions

Add an explicit "Use when..." clause, e.g. "Use when writing, reviewing, or refactoring C#/.NET code, or designing ASP.NET Core services."

Reframe topic labels as concrete actions (e.g. "configure dependency injection", "apply async/await patterns") to strengthen specificity.

Expand trigger terms with natural variations users might say ("C#", ".NET", "ASP.NET Core", "EF Core", "DI").

Dimension	Reasoning	Score
Specificity	Names the .NET/C# domain and several concrete topics ("conventions, dependency injection, async/await"), but these are topic labels rather than concrete actions, so it stops short of listing multiple specific actions.	2 / 3
Completeness	Clearly answers "what" with a strong capability list, but there is no explicit "when to use it" clause; per guidelines a missing "Use when..." caps completeness at 2.	2 / 3
Trigger Term Quality	Includes relevant natural terms users would say ("C#", ".NET", "dependency injection", "async/await") but lacks common variation coverage and an explicit use-when framing.	2 / 3
Distinctiveness Conflict Risk	The .NET/C# niche with DI and async-specific framing is clearly distinguishable from other skills and unlikely to trigger for the wrong skill.	3 / 3
	Total	9 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/dotnet-patterns/SKILL.md
Commit: 754b8dd

Reviewed: 2 days ago

Table of Contents

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.