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%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 well-structured review skill with a crisp phased workflow, concrete citations to real repo files, explicit validation/self-check steps, and a single one-level reference file. It respects the token budget while remaining highly actionable.

DimensionReasoningScore

Conciseness

Lean and efficient: rule IDs carry one-line descriptions and real-file citations with no basic C#/.NET concept explanations; assumes Claude's competence and every line earns its place.

5 / 5

Actionability

Fully executable guidance — exact grep commands ('git grep "Microsoft.AspNetCore" -- sdks/dotnet/src'), concrete file paths for citations, severity-tagged rules, and a copy-paste review-summary template covering the common cases.

5 / 5

Workflow Clarity

Clear Step 0–4 sequence with an explicit self-validation checklist (dedupe, verify rule ID + line, confirm file-class gating, drop unverifiable findings) providing validation checkpoints and a feedback loop before emitting the summary.

5 / 5

Progressive Disclosure

SKILL.md is an overview of phases and discipline pointing to one-level-deep references/rules.md (verified to exist), with a clearly signaled inline link and no nested-reference chains.

5 / 5

Total

20

/

20

Passed

Description

100%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 highly specific, well-scoped description that names concrete actions, provides natural USE FOR / DO NOT USE FOR triggers, and cleanly separates the .NET SDK from sibling SDKs. It uses third person throughout and avoids fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete review actions — AOT serialization, the no-ASP.NET-in-src boundary, the PublicAPI analyzer workflow, wire compatibility with TS, and the house style (sealed/no-records/ConfigureAwait) — giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both 'what' (reviews .NET SDK changes against its conventions, runs a phased rule-by-rule review) and 'when' (USE FOR / DO NOT USE FOR clauses with concrete trigger phrases).

5 / 5

Trigger Term Quality

Natural user phrasing is well covered: 'reviewing a PR, diff, or branch that touches sdks/dotnet/', 'checking a new event/message type', 'verifying serialization, package placement, or public-API changes', plus a DO NOT USE FOR set.

5 / 5

Distinctiveness Conflict Risk

Scoped to sdks/dotnet/ with explicit exclusions for the TypeScript/Python SDKs and for generic analyzer-enforced C# style, giving a clear niche with minimal conflict risk.

5 / 5

Total

20

/

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