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

77

Quality

96%

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

92%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-engineered review skill: a phased, rule-by-rule workflow with explicit self-validation, concrete commands and repo citations throughout, and a clean split between the in-body rule catalog and the one-level-deep references/rules.md. The only weakness is a handful of redundant justificatory sentences that could be trimmed for token efficiency.

Suggestions

Trim duplicate framing in 'Reviewer discipline' and the summary rules — the severity legend and 'the skill only reports / verdict is advisory' rationale each appear twice; stating each once saves tokens without losing information.

Delete justificatory asides that assume the model needs persuading (e.g. 'Automated reviewers have high false-positive rates') and keep only the directive ('Verify before flagging: read the changed code and confirm the rule applies').

DimensionReasoningScore

Conciseness

The body is dense and assumes competence — 50+ rules rendered as single-line IDs with severity and a citation, no basic-concept explanation — but there are minor instances of over-explanation that could be trimmed (e.g. "Automated reviewers have high false-positive rates," the severity legend explained twice, and "The skill never approves or blocks automatically — the verdict is advisory" restating the earlier "Fix nothing — this skill only reports"). This sits between the level-4 'efficient, minor trimmable over-explanation' and level-5 'every token earns its place' anchors, and the redundant severity/verdict prose keeps it at 4 rather than 5.

4 / 5

Actionability

Guidance is fully executable: exact commands ("git merge-base <base> HEAD", "git grep \"Microsoft.AspNetCore\" -- sdks/dotnet/src"), concrete file citations for every key rule, a per-rule severity taxonomy, a common-pitfalls table, and a copy-paste-ready Markdown output template with worked examples — matching the level-5 'copy-paste ready, specific examples cover the common cases' anchor, clearly above the 'minor gaps' level-4 anchor.

5 / 5

Workflow Clarity

A clearly sequenced Step 0–4 process with explicit validation checkpoints: "Verify the code first" before flagging, Step 3 self-validation ("Dedupe; confirm each finding cites a real rule and a real line ... drop anything not verifiable in the actual diff"), a closing checklist, and clean-diff/reporting rules — the level-5 'explicit validation steps; feedback loops; checklists' anchor. The skill is report-only, so the destructive/batch cap does not apply.

5 / 5

Progressive Disclosure

SKILL.md is the overview (rule IDs with one-line summaries, process, output format) and full BAD→GOOD detail and per-rule exceptions live in references/rules.md, which exists (431 lines, with its own TOC), is referenced twice with clear signaling, and is exactly one level deep — matching the level-5 'clear overview with well-signaled one-level-deep references; content appropriately split' anchor rather than the 'minor organization gaps' level-4 anchor.

5 / 5

Total

19

/

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.

An exemplary description: it states concrete capabilities tied to named conventions, gives explicit USE FOR / DO NOT FOR trigger guidance in third person, and scopes itself narrowly to sdks/dotnet/ to avoid conflicts with sibling SDK skills. No vague fluff, over-claims, or padding is present.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete, domain-specific capabilities: "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)" plus "Runs a phased, rule-by-rule review" — comprehensive and fully concrete, matching the level-5 anchor rather than the 'several specific actions, minor gaps' level-4 anchor.

5 / 5

Completeness

Both questions are answered explicitly with concrete trigger phrases: the "what" (review C#/.NET code changes against named conventions) and an explicit "USE FOR:" clause with multiple triggers, additionally reinforced by a "DO NOT USE FOR:" clause — clearly the level-5 anchor, not the level-4 anchor where "when" could be more explicit.

5 / 5

Trigger Term Quality

Natural user phrases and synonyms are comprehensively 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" — includes path/extension-like identifiers (sdks/dotnet/, sdks/typescript/) and colloquial variations, exceeding the 'good coverage, a few missing' level-4 anchor.

5 / 5

Distinctiveness Conflict Risk

A clear niche (the AG-UI .NET SDK at sdks/dotnet/) with path-scoped triggers and an explicit "DO NOT USE FOR: ... reviewing the TypeScript SDK (sdks/typescript/) or Python SDK (sdks/python/); generic C# style nits" boundary, giving minimal conflict risk with sibling skills — the level-5 'clear niche with distinct triggers' anchor.

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.

Validation — 16 / 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.