CtrlK
BlogDocsLog inGet started
Tessl Logo

agui-dotnet-code-review

Review C#/.NET code changes to the AG-UI .NET SDK (sdks/dotnet/) against its specific conventions and architectural rules — AOT serialization, the "no ASP.NET in src/" boundary, the PublicAPI analyzer workflow, wire compatibility with the TypeScript reference, and the house style (sealed/no-records/ConfigureAwait). Runs a phased, rule-by-rule review. USE FOR: reviewing a PR, diff, or branch that touches sdks/dotnet/; checking a new event/message type; verifying serialization, package placement, or public-API changes in the .NET SDK. DO NOT USE FOR: generic C# style nits already enforced by analyzers/EditorConfig; reviewing the TypeScript SDK (sdks/typescript/) or Python SDK (sdks/python/); writing new features (only flag violations, never rewrite code).

80

Quality

100%

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

100%

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

A well-structured instruction-only review skill: lean rule catalog with concrete citations and executable checks, an explicitly sequenced process with a self-validation checkpoint, and a single well-signaled one-level-deep reference. It scores at the top anchor on all four dimensions.

DimensionReasoningScore

Conciseness

The body is a dense rule catalog plus a phased process with no concept explanations Claude already knows (no "what is AOT" padding); each rule line carries an ID, severity, and citation, so every token earns its place. Not level 2 because there is no unnecessary explanation to tighten away.

3 / 3

Actionability

Guidance is concrete and executable: rule IDs, severities, real repo citations, a verifiable command ("git grep \"Microsoft.AspNetCore\" -- sdks/dotnet/src must be empty"), and a copy-paste-ready review-summary template. Not level 2 because it is specific and copy-paste ready rather than pseudocode or abstract direction.

3 / 3

Workflow Clarity

Steps 0–4 are explicitly sequenced with a dedicated Step 3 self-validation (dedupe, confirm real rule + real line, confirm correct file class, drop unverifiable) and a closing checklist. Not level 2 because validation checkpoints are explicit, not implicit.

3 / 3

Progressive Disclosure

The body is an overview that defers full BAD→GOOD examples and per-rule exceptions to a single clearly signaled one-level-deep reference, references/rules.md, which exists in the bundle. Not level 2 because the reference is well signaled and only one level deep.

3 / 3

Total

12

/

12

Passed

Description

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.

A tightly scoped, third-person description that states concrete capabilities, gives explicit USE FOR / DO NOT FOR triggers, and draws a clear boundary against sibling SDK and generic-C# skills. It hits the top anchor on every dimension.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Review C#/.NET code changes", "checking a new event/message type", "verifying serialization, package placement, or public-API changes" — and enumerates specific conventions (AOT serialization, the no-ASP.NET-in-src boundary, ConfigureAwait). It is not a level-2 "names domain and some actions" case because the action set is comprehensive and concrete.

3 / 3

Completeness

Explicitly answers both what ("Review C#/.NET code changes… Runs a phased, rule-by-rule review") and when (explicit "USE FOR:" and "DO NOT USE FOR:" clauses). Not level 2 because the when is explicit, not merely implied.

3 / 3

Trigger Term Quality

The USE FOR clause uses natural terms a user would actually say — "reviewing a PR, diff, or branch", "serialization", "public-API changes" — with good coverage of common variations. Not level 2 because it covers the natural phrasings rather than just one keyword.

3 / 3

Distinctiveness Conflict Risk

Niche is sharply scoped to sdks/dotnet/ and the DO NOT USE clause actively excludes the TypeScript/Python SDKs and generic analyzer-enforced nits, making wrong-skill conflicts unlikely. Not level 2 because the boundary against sibling SDK skills is explicit.

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
ag-ui-protocol/ag-ui
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.