CtrlK
BlogDocsLog inGet started
Tessl Logo

extensions-review

Guidance for writing and modifying Microsoft.Extensions.* and System.IO.Compression code in dotnet/runtime. Covers DI lifetime management, configuration binding, options validation, logging provider patterns, caching semantics, compression format compliance, and host lifecycle. For full code review, delegates to the @extensions-reviewer agent. Trigger words: Microsoft.Extensions, IServiceCollection, IConfiguration, ILogger, IHost, IMemoryCache, IOptions, ZipArchive, HttpClientFactory, IFileProvider, IChangeToken.

69

Quality

84%

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

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

An efficient, highly actionable reference with concrete code and decision trees that assume Claude's competence. Its main limitations are the absence of explicit validate-then-retry feedback loops for destructive/batch operations and the lack of reference files to offload the denser per-topic detail.

Suggestions

Add an explicit ordered workflow with validation checkpoints for destructive or batch operations (e.g., a step-by-step register -> validate-on-start -> AOT-publish -> run parity tests sequence) to push workflow_clarity to the top anchor.

Move the larger per-topic code galleries (e.g., full compression and host-lifecycle examples) into references/ files and link to them one level deep to keep SKILL.md a lean overview and improve progressive_disclosure.

DimensionReasoningScore

Conciseness

The body is dense and efficient: tight decision trees plus minimal WRONG/CORRECT code examples, terse reminder bullets, and no padding or explanations of concepts Claude already knows, so every section earns its tokens.

5 / 5

Actionability

Guidance is fully executable with copy-paste-ready C# (TryAddSingleton, IServiceScopeFactory scopes, AddOptions().Bind().ValidateDataAnnotations().ValidateOnStart(), [LoggerMessage], HybridCache, BrotliStream, File.SetUnixFileMode) and concrete decision trees covering the common cases for each topic.

5 / 5

Workflow Clarity

Decision trees give clear sequencing for lifetime/binding/logging choices and the Testing, Trim & AOT, and dispose-behavior guidance function as validation checklists, but the skill is pattern guidance rather than an explicit ordered destructive workflow with validate->fix->retry feedback loops, leaving minor checkpoint gaps versus the top anchor.

4 / 5

Progressive Disclosure

The single SKILL.md is well-organized with clear section headers and appropriately delegates full review to the @extensions-reviewer agent as a one-level reference; however several multi-block per-topic sections (DI tree, compression details) are inlined rather than split into reference files, and no bundle files are provided.

4 / 5

Total

18

/

20

Passed

Description

78%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, highly specific description that clearly delineates a narrow .NET niche and supplies explicit trigger terms. Its only weakness is presenting the "when to use" guidance as a raw keyword list rather than a natural use-when scenario sentence.

Suggestions

Convert the "Trigger words:" enumeration into a natural "Use when writing or modifying Microsoft.Extensions.* or System.IO.Compression code, or when the user mentions DI registration, options, logging providers, caching, ZipArchive, or HttpClientFactory." sentence.

Lead with concrete action verbs (e.g., "Register services with correct DI lifetimes, bind and validate options, implement logging providers") rather than "Covers ..." domain labels to strengthen specificity.

DimensionReasoningScore

Specificity

Lists several concrete capability areas ("DI lifetime management, configuration binding, options validation, logging provider patterns, caching semantics, compression format compliance, and host lifecycle") plus the actions "writing and modifying", but these are domain labels rather than discrete action verbs, leaving minor coverage gaps versus the comprehensive anchor.

4 / 5

Completeness

It clearly states both what (writing/modifying these libraries and the covered areas) and when (the Trigger words line plus "delegates to the @extensions-reviewer agent for full code review"), but the "when" is a keyword enumeration rather than a flowing "Use when..." scenario sentence, so it fits the anchor where when could be more explicit rather than the fully concrete phrase anchor.

4 / 5

Trigger Term Quality

The explicit "Trigger words:" list provides many natural identifiers users say (IServiceCollection, IConfiguration, ILogger, ZipArchive, HttpClientFactory, IOptions, etc.) with good coverage, though it lacks common synonyms or file extensions that would push it to the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

The niche is sharply scoped to "Microsoft.Extensions.* and System.IO.Compression code in dotnet/runtime" with distinct type-name triggers, giving it a clear niche with minimal conflict risk against unrelated skills.

5 / 5

Total

17

/

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/runtime
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.