agui-dotnet-protobuf

Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then SseEventStreamFormatter as fallback) into the HttpClient; enabling a server to answer protobuf by registering ProtobufEventStreamFormatter and negotiating the response format from the request Accept header; understanding the protobuf-or-SSE fallback. DO NOT USE FOR: the default SSE transport or first-time setup (use agui-dotnet-streaming-chat); JSON event serialization questions; tools, state, interrupts, multimodal, or generative UI.

Quality

96%

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

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.

The body is a model of an action-oriented skill: complete executable code for both ends of the transport, a brief negotiation model, anti-patterns targeting the real silent-failure mode, and a concrete three-step verification including the fallback path. Nothing is padded, misplaced, or missing for its scope.

Dimension	Reasoning	Score
Conciseness	Lean throughout: no explanation of what protobuf or SSE are, no library evangelism, no padded prose. Every sentence either states a constraint that prevents a mistake ('Nothing above the transport changes') or instructs. Fits the 'every token earns its place' anchor.	5 / 5
Actionability	Fully executable: the exact package install ('dotnet add package AGUI.Protobuf') with the additional package names per app type, plus two complete, copy-paste-ready C# blocks covering both the client and server cases. The Anti-patterns section adds concrete failure modes to avoid.	5 / 5
Workflow Clarity	Clear sequence (Install → Client config → Server config) with an explicit 'Verify' section of three numbered checks, including a fallback test ('Point the same client at an SSE-only server... confirming fallback'). Validation checkpoints and error-recovery guidance (verify Content-Type, don't assume) are present.	5 / 5
Progressive Disclosure	Single-file skill (~90 lines, mostly code) with no bundle files; sections are well-organized (Install, Client, Server, Anti-patterns, Verify) and nothing here clearly belongs in a separate reference file. Per the simple-skill guidance, well-organized sections with no needed external references warrant 5.	5 / 5
	Total	20 / 20 Passed

Description

92%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-bounded description that names concrete SDK types and actions, provides explicit positive and negative triggers, and cleanly separates itself from the SSE streaming skill. Only minor gap: a few natural keyword variations are missing, which alone keeps trigger term quality at 4.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete, class-level actions: 'wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then SseEventStreamFormatter as fallback) into the HttpClient' and 'registering ProtobufEventStreamFormatter and negotiating the response format from the request Accept header'. Names the domain, the mechanism, and the exact SDK types — comprehensive with no vague language.	5 / 5
Completeness	Explicitly answers what ('Use the protobuf wire transport... a compact binary event stream negotiated via the Accept header') and when ('USE FOR:' three concrete scenarios) plus a 'DO NOT USE FOR:' boundary. Exceeds the 5 anchor by including negative triggers; not 4 because both what and when are concrete and explicit.	5 / 5
Trigger Term Quality	Good natural-keyword coverage with synonyms ('protobuf', 'Server-Sent Events'/'SSE', 'compact binary event stream', 'Accept header', 'transport', 'fallback'). A few phrasings a user might naturally say (e.g. 'wire format', 'message encoding', 'binary protocol') are absent, so it fits the 4 anchor rather than 5.	4 / 5
Distinctiveness Conflict Risk	Clear niche (protobuf binary transport for AG-UI .NET) with distinct triggers, and the 'DO NOT USE FOR: the default SSE transport or first-time setup (use agui-dotnet-streaming-chat)' clause explicitly disambiguates from the closest sibling skill. Minimal conflict risk.	5 / 5
	Total	19 / 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: sdks/dotnet/plugins/ag-ui-dotnet/skills/agui-dotnet-protobuf/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.