dotnet-standards-enforcer
Reviews and refactors .NET/C# code: fixes async patterns, validates DI registration, corrects error handling, adds documentation, enforces style conventions. USE FOR: review C# code, audit project, enforce coding standards, apply .NET best practices, clean up code, fix style issues, apply coding standards, tidy up this file, make this idiomatic C#, fix code quality issues, get PR-ready, prepare for code review, add documentation, fix async patterns, check DI registration, check error handling, fix configuration, bring this up to standard, make this code production-ready. DO NOT USE FOR: non-.NET codebases, read-only .NET questions, trivial single-variable edits.
96
100%
Does it follow best practices?
Impact
92%
1.27xAverage score across 6 eval scenarios
Passed
No known issues
Quality
Discovery
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.
This is an excellent skill description that hits all the marks. It provides specific concrete actions, uses natural language trigger terms that users would actually say, explicitly defines both when to use and when not to use the skill, and clearly carves out a distinct niche for .NET/C# code review and refactoring.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'fixes async patterns, validates DI registration, corrects error handling, adds documentation, enforces style conventions' - these are precise, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (reviews/refactors .NET/C# code with specific actions) AND when (explicit 'USE FOR:' clause with extensive triggers), plus includes 'DO NOT USE FOR:' exclusions which adds clarity. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'review C# code', 'clean up code', 'make this idiomatic C#', 'get PR-ready', 'fix async patterns', 'make this code production-ready' - these match real user language patterns. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche targeting .NET/C# specifically with distinct triggers like 'DI registration', 'async patterns', 'idiomatic C#'. The 'DO NOT USE FOR' clause explicitly excludes non-.NET codebases, reducing conflict risk. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill with excellent structure and actionability. It demonstrates strong progressive disclosure by keeping the main file as an orchestration overview while delegating detailed rules to reference files. The workflow is clearly sequenced with explicit checkpoints, validation steps, and a defined output format.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, assuming Claude's competence with .NET/C#. No unnecessary explanations of basic concepts; every section serves a clear purpose with specific, actionable rules. | 3 / 3 |
Actionability | Provides concrete, executable guidance: specific file patterns to exclude, exact table format for findings, clear severity definitions, and explicit instructions for applying fixes with checkmarks. References to sub-skill files contain the detailed rules. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with clear sequencing: pre-flight detection → scope determination → sequential sub-skill execution → summary table → apply findings. Includes explicit validation (checkpoint summary for context limits) and feedback loops (confirm each fix with ✅). | 3 / 3 |
Progressive Disclosure | Exemplary structure with SKILL.md as overview and 8 sub-skill reference files clearly linked in a table. One-level-deep references with clear navigation. Trigger phrases appropriately externalized to a separate reference file. | 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- thoughtboat/copilot-skills-that-work
- Commit
94e070f
- 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.