CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

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 tight, executable skill body: complete C# examples for both client and server sides, an explicit verification checklist covering both success and fallback paths, and clean sectioning with no padding. It assumes Claude's knowledge and adds only SDK-specific wiring and gotchas.

DimensionReasoningScore

Conciseness

Lean throughout — no preamble explaining what protobuf, SSE, or the SDK is; every line is task-relevant instruction (install, wire handler, negotiate server-side, anti-patterns, verify). The prose assumes Claude's competence and earns its tokens.

3 / 3

Actionability

Both client and server sections give complete, copy-paste-ready C# with real using-directives, package install command (`dotnet add package AGUI.Protobuf`), and concrete formatter wiring; the server snippet is a full endpoint including Accept-header selection and response writing.

3 / 3

Workflow Clarity

The Verify section provides an explicit 3-step checklist with validation checkpoints (confirm Content-Type is the protobuf media type and body is binary; drop server protobuf registration to confirm fallback; confirm decoded stream matches SSE), giving a clear feedback loop for a non-trivial two-sided negotiation.

3 / 3

Progressive Disclosure

No bundle files exist in references/scripts/assets, and the body is under ~50 lines of well-organized sections (Install, Client, Server, Anti-patterns, Verify); per the simple-skills scoring note, a self-contained single-purpose skill with clear sections scores 3 without external references.

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 highly specific, trigger-rich description that explicitly states both what it does and when to use it, and distinguishes itself from sibling skills via a concrete DO NOT USE FOR clause that points to the correct alternative. Written in third person with no over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then SseEventStreamFormatter as fallback) into the HttpClient', 'registering ProtobufEventStreamFormatter and negotiating the response format from the request Accept header' — naming specific SDK types and the negotiation mechanism rather than vague abstractions.

3 / 3

Completeness

Explicitly answers both 'what' (use the protobuf wire transport with the AG-UI .NET SDK via Accept-header negotiation) and 'when' via the capitalized 'USE FOR:' and 'DO NOT USE FOR:' clauses, which are explicit trigger guidance beyond mere implication.

3 / 3

Trigger Term Quality

Covers natural terms a user would say — 'protobuf', 'SSE/Server-Sent Events', 'Accept header', 'fallback', '.NET SDK' — alongside the inverse 'DO NOT USE FOR' trigger set (SSE transport, JSON serialization, tools/state/interrupts) giving good coverage of likely phrasing.

3 / 3

Distinctiveness Conflict Risk

Carves a clear niche (protobuf vs SSE transport for the AG-UI .NET SDK) and actively de-conflicts from sibling skills via the 'DO NOT USE FOR: default SSE transport or first-time setup (use agui-dotnet-streaming-chat)' clause, making collision with adjacent skills unlikely.

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.