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.

68

Quality

82%

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

65%Weight 40%Scale 1-3

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

A highly actionable, concept-free reference packed with executable C# and decision trees, but it is a monolithic single-file skill that would benefit from offloading detailed examples into reference files and adding explicit validation feedback loops.

Suggestions

Move full code examples (e.g. the captive-dependency and archive-extraction blocks) into files under references/ and keep SKILL.md as a concise overview with one-level-deep links, improving progressive_disclosure and conciseness.

Add an explicit validate→fix→retry feedback loop for the riskier operations (e.g. a checklist around compression format compliance or background-service disposal) to raise workflow_clarity.

Trim the body by replacing some inline WRONG/CORRECT pairs with compact rules, retaining only one representative example per pattern.

DimensionReasoningScore

Conciseness

The body is dense and free of concept padding Claude already knows, but at ~250 lines it is substantial and several full code examples could be offloaded to reference files to tighten the overview.

2 / 3

Actionability

Every section ships executable, copy-paste-ready C# with explicit WRONG/CORRECT contrasts and concrete APIs (TryAddSingleton, HybridCache.GetOrCreateAsync, BrotliStream), fully matching the executable-code anchor.

3 / 3

Workflow Clarity

Decision trees sequence choices clearly and the testing section adds validation/disposal checkpoints, but the body reads as a reference catalog rather than a workflow and lacks an explicit validate→fix→retry feedback loop for risky operations.

2 / 3

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent) and all guidance is inline in SKILL.md; sections are well-organized but content that should be split into separate files is kept inline, matching the mid-tier anchor.

2 / 3

Total

9

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 precise, third-person description that cleanly answers both what the skill covers and when to use it, with concrete symbol-level triggers tied to a well-scoped niche. Only minor nit is the mechanical "Trigger words:" framing.

DimensionReasoningScore

Specificity

Lists multiple concrete capability areas — "DI lifetime management, configuration binding, options validation, logging provider patterns, caching semantics, compression format compliance, and host lifecycle" — matching the anchor for naming several specific actions.

3 / 3

Completeness

It states both what the skill does ("Guidance for writing and modifying Microsoft.Extensions.* and System.IO.Compression code") and when to use it via an explicit "Trigger words:" list and a delegation note, satisfying the explicit-trigger requirement.

3 / 3

Trigger Term Quality

The trigger words (IServiceCollection, IConfiguration, ILogger, IHost, IMemoryCache, IOptions, ZipArchive, HttpClientFactory) are precisely the symbols a developer names when touching this domain; coverage of natural domain terms is good, though the "Trigger words:" label is slightly mechanical.

3 / 3

Distinctiveness Conflict Risk

The niche is sharply bounded to Microsoft.Extensions.* and System.IO.Compression in dotnet/runtime with distinct symbol triggers, making it unlikely to fire for an unrelated skill.

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.

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.