CtrlK
BlogDocsLog inGet started
Tessl Logo

dotnet-patterns

Idiomatic C# and .NET patterns, conventions, dependency injection, async/await, and best practices for building robust, maintainable .NET applications. Use when writing or reviewing C# / .NET code — DI, async, or general conventions.

67

Quality

81%

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

76%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 strong, executable patterns reference with excellent code examples and lean prose. Its main weakness is the absence of any multi-step workflow or validation guidance, which limits workflow_clarity, but as a reference catalog it is well-organized and self-contained.

Suggestions

Add a short 'Decision guide' or workflow mapping common situations (e.g., 'expected failure → Result pattern', 'cross-cutting concern → middleware') to give the reference an explicit selection sequence.

Consider moving the longer worked examples (EF Core repository, middleware) into references/ files with one-line pointers from SKILL.md to reduce body length and improve progressive disclosure.

Trim redundant contrast ('Bad:') blocks where the accompanying 'Good' example already makes the point, to tighten conciseness.

DimensionReasoningScore

Conciseness

Mostly lean, code-forward prose that assumes Claude knows C# and .NET ('Return explicit success/failure instead of throwing for expected failures'), with only minor instances that could be trimmed such as redundant 'Bad' contrast blocks and the Anti-Patterns table restating earlier points.

4 / 5

Actionability

Fully executable, copy-paste-ready C# across DI registration, async/await, Options, Result, EF Core repository, middleware, Minimal APIs, and guard clauses, covering the common cases concretely.

5 / 5

Workflow Clarity

This is a patterns reference rather than a multi-step workflow, so it has no sequenced process or validation checkpoints; sections are well-organized but the workflow dimension is only implicitly served by 'When to Activate' plus topical grouping.

3 / 5

Progressive Disclosure

No bundle files exist and the skill is self-contained with clear section headers; structure is good and content is appropriately placed in one file for a quick-reference patterns catalog, though at ~295 lines some extended examples (repository, middleware) could optionally live in reference files.

4 / 5

Total

16

/

20

Passed

Description

87%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 well-crafted description that clearly states both capability and activation triggers in concise third-person voice. It is distinctive and actionable, with only minor room to broaden trigger-term synonyms.

DimensionReasoningScore

Specificity

Lists several concrete areas — 'conventions, dependency injection, async/await, and best practices' — beyond just naming the domain, though these read more as topics than crisp verb-actions like 'extract' or 'merge', leaving minor gaps.

4 / 5

Completeness

Explicitly answers both 'what' ('Idiomatic C# and .NET patterns, conventions, dependency injection, async/await...') and 'when' ('Use when writing or reviewing C# / .NET code — DI, async, or general conventions') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural user-facing terms ('writing or reviewing C# / .NET code', 'DI', 'async', 'general conventions') with the C#/.NET synonym pair, but misses several common variations users might say (ASP.NET, Entity Framework, CancellationToken).

4 / 5

Distinctiveness Conflict Risk

Scoped tightly to C#/.NET with distinct triggers ('writing or reviewing C# / .NET code'), giving it a clear niche and minimal conflict risk with non-.NET skills.

5 / 5

Total

18

/

20

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
affaan-m/ECC
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.