CtrlK
BlogDocsLog inGet started
Tessl Logo

system-net-review

Guidance for writing and modifying System.Net networking code in dotnet/runtime. Covers resource lifecycle, connection pooling, cross-platform interop, protocol compliance, async patterns, and security posture. For full code review, delegates to the @system-net-review agent. Trigger words: system.net, networking, http client, sockets, ssl, tls, quic, http2, http3, socketshttphandler, sslstream, connection pool.

72

Quality

88%

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

82%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 dense, competent authoring-and-review guidance document that assumes Claude's expertise and backs every decision framework with concrete executable C# DO/DON'T examples and a clearly bounded review-delegation workflow. Main weaknesses are mild redundancy between decision trees and 'Key rules' lists, and the lack of in-skill validation checkpoints (delegated to the agent and build-and-test skill).

Suggestions

Trim the 'Key rules' bullets that merely restate the adjacent decision tree (e.g. the resource-lifecycle tree already implies single-owner disposal) to recover tokens without losing guidance.

Consider extracting the longer Code Patterns (e.g. SslStream, HTTP/2 flow control) into a references/ file referenced one level deep, keeping SKILL.md as a lean overview per progressive-disclosure best practice.

Add an explicit authoring-side checkpoint (e.g. 'after editing, run the build-and-test skill and confirm tests pass before handing off') so the writing workflow has a validation step mirroring the review path.

DimensionReasoningScore

Conciseness

The body assumes Claude's .NET competence (no explaining what HTTP/2 or a socket is) and uses compact decision trees plus tight DO/DON'T snippets, but the per-framework 'Key rules' blocks partly restate the decision-tree content and some code comments state the obvious, leaving minor trim opportunities.

4 / 5

Actionability

Provides numerous concrete, executable C# patterns (ArrayPool rent/return, SocketAsyncEventArgs reuse, SslClientAuthenticationOptions, linked CancellationTokenSource, HTTP/2 flow-control windowing) with explicit DO/DON'T contrasts covering the common System.Net cases.

5 / 5

Workflow Clarity

The review path is a clear sequenced workflow with explicit role boundaries ('invoke the @system-net-review agent... only collect feedback items and return them... parent reviewer is responsible for collection, deduplication, and posting'), but authoring guidance is reference-style decision trees rather than a sequenced workflow, and validation is delegated out rather than present as checkpoints.

4 / 5

Progressive Disclosure

Well-organized into Decision Frameworks, Code Patterns, Testing Guidance, and Reference Links, with clearly signaled one-level-deep references (repo source paths, the @system-net-review agent, build-and-test/code-review skills, .github/instructions); however it is a substantial single ~270-line file with no bundle files, and some Code Patterns could plausibly live in separate reference files.

4 / 5

Total

17

/

20

Passed

Description

95%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, narrowly-scoped description that clearly communicates both purpose and trigger conditions using third-person voice with concrete domain coverage and natural trigger terms. The only minor weakness is that the action verbs are generic relative to the breadth of domains listed.

DimensionReasoningScore

Specificity

Lists several concrete action areas — 'writing and modifying System.Net networking code' plus 'resource lifecycle, connection pooling, cross-platform interop, protocol compliance, async patterns, and security posture' and 'delegates to the @system-net-review agent' — but the verbs themselves (writing/modifying/delegates) are somewhat generic rather than a comprehensive set of specific actions.

4 / 5

Completeness

Clearly states what ('Guidance for writing and modifying System.Net networking code... Covers [six domains]') and provides explicit when guidance via the concrete 'Trigger words:' list, which is equivalent to a 'Use when...' clause.

5 / 5

Trigger Term Quality

The 'Trigger words:' list — 'system.net, networking, http client, sockets, ssl, tls, quic, http2, http3, socketshttphandler, sslstream, connection pool' — covers natural terms a .NET developer would say, including synonyms (ssl/tls, http2/http3) and concrete API class names (socketshttphandler, sslstream).

5 / 5

Distinctiveness Conflict Risk

Scoped narrowly to System.Net in dotnet/runtime with distinct technical triggers (socketshttphandler, sslstream, quic), giving it a clear niche with minimal overlap risk against other skills.

5 / 5

Total

19

/

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

relative_links

Relative link issues: 7 suspicious

Warning

Total

15

/

16

Passed

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.