agui-dotnet-wire-types

Add or modify a wire/protocol type in the AG-UI .NET SDK AGUI.Abstractions package — a new event, message, or content-part type, the AOT source-gen serializer context, or a polymorphic JSON converter, keeping it AOT-safe, JSON-wire-compatible with the TypeScript reference, and PublicAPI-clean. USE FOR: adding an AG-UI event type, adding a message role or input-content type, editing AGUIJsonSerializerContext, editing BaseEventJsonConverter / AGUIMessageJsonConverter / AGUIInputContentJsonConverter, fixing PublicAPI.Unshipped analyzer build failures on protocol types, wire-format round-trip serialization. DO NOT USE FOR: writing integration/SSE tests (use agui-dotnet-integration-tests), server hosting/endpoint code, or non-Abstractions packages.

Quality

98%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

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

The body is a dense, executable recipe: numbered steps, exact code, failure-mode mapping, and a validation section, with no filler. Its only structural weakness is inlining serialization-rule detail that duplicates the canonical AGENTS.md reference instead of splitting it out.

Suggestions

Move the detailed Serialization/AOT rules that duplicate sdks/dotnet/AGENTS.md into a short reference file (e.g. references/serialization-rules.md), keeping only the task-critical non-negotiables inline and pointing to AGENTS.md as canonical.

Add an explicit feedback loop to the Validate section, e.g. "if dotnet build fails on PublicAPI analyzer errors, add the missing members to PublicAPI.Unshipped.txt and rebuild".

Consider moving the PublicAPI.Unshipped.txt line-format block to the same reference file, keeping one representative example inline.

Dimension	Reasoning	Score
Conciseness	No basic-concept explanations; every section is operational recipe material and assumes C#/System.Text.Json competence. The only narrative passage (the NullOmissionTest rationale) justifies a rule that guards a real regression, so it earns its tokens.	5 / 5
Actionability	Gives a numbered 6-step recipe with exact file paths, sealed-class conventions, copy-paste converter switch arms, exact PublicAPI.Unshipped.txt line formats, a round-trip test example, and dotnet build/test commands — covering event, message, and input-content cases.	5 / 5
Workflow Clarity	Clear sequence with an explicit four-spot checklist mapping each miss to its failure mode (build fails vs silent deserialize failure), a mandatory round-trip test, and a Validate section with build and test commands serving as recovery feedback.	5 / 5
Progressive Disclosure	Well-sectioned body with one clearly signaled external reference (sdks/dotnet/AGENTS.md as canonical), but the inline Serialization/AOT rules and PublicAPI block duplicate canonical AGENTS.md material rather than splitting detail into a reference file — a minor organization gap.	4 / 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.

The description is a dense, third-person statement of what the skill does and exactly when to use it, with concrete trigger phrases and an explicit do-not-use boundary. It covers the niche comprehensively with no fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions (new event/message/content-part types, AOT source-gen serializer context, polymorphic JSON converters, PublicAPI fixes, round-trip serialization) with comprehensive coverage of its niche.	5 / 5
Completeness	Explicitly answers both what (add/modify wire/protocol types in AGUI.Abstractions, kept AOT-safe and JSON-wire-compatible) and when (USE FOR list plus a DO NOT USE FOR boundary with a redirect to agui-dotnet-integration-tests).	5 / 5
Trigger Term Quality	USE FOR enumerates the exact natural phrases a developer would say: adding an AG-UI event type, adding a message role or input-content type, editing AGUIJsonSerializerContext, fixing PublicAPI.Unshipped analyzer build failures, wire-format round-trip serialization.	5 / 5
Distinctiveness Conflict Risk	A clear niche (AG-UI .NET Abstractions wire types) with distinct triggers and explicit negative boundaries (integration/SSE tests, server hosting, non-Abstractions packages), minimizing overlap with sibling skills.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

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
Path: .github/skills/agui-dotnet-wire-types/SKILL.md
Commit: ec9f4fa

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.