CtrlK
BlogDocsLog inGet started
Tessl Logo

agui-dotnet-transport

Add or modify a wire transport / event-stream encoding in the AG-UI .NET SDK — the protobuf codec, the SSE format, content negotiation, the JsonElement-to-protobuf Value bridge, or a brand new encoding — while preserving Native AOT compatibility and byte-level wire compatibility with @ag-ui/proto. USE FOR: working on AGUI.Formatting / AGUI.Protobuf, IAGUIEventStreamFormatter, transport content negotiation, the JsonElement-to-google.protobuf.Value bridge, SSE or protobuf framing, server formatter registration / AGUIResults.Events negotiation. DO NOT USE FOR: adding a new wire event TYPE (use agui-dotnet-wire-types), writing tests (use agui-dotnet-integration-tests).

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.

The body encodes genuinely non-obvious transport constraints concisely, with concrete identifiers, a real deep-dive reference, sequenced extension steps, and explicit verification checkpoints. It is a well-structured, high-actionability skill file.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious wire-format facts (media type, big-endian uint32 framing, AOT caveats) and never explains basics Claude already knows, so it earns the lean/efficient score-3 anchor rather than the padded score-2 case.

3 / 3

Actionability

Provides concrete, copy-paste-ready guidance — the DI registration 'services.AddSingleton<IAGUIEventStreamFormatter, ProtobufEventStreamFormatter>()', exact media-type string, framing byte layout, and 'dotnet build' from 'sdks/dotnet/' — meeting the fully-executable score-3 anchor rather than the pseudocode score-2 anchor.

3 / 3

Workflow Clarity

The schema-first extension is a clearly sequenced two-step process and the 'How to verify' section supplies explicit validation checkpoints (byte-parity cross-language tests, PublicAPI.Unshipped.txt, warnings-as-errors), matching the score-3 anchor over the checkpoint-missing score-2 case.

3 / 3

Progressive Disclosure

The body is an overview that signals one level of depth via 'references/wire-format.md' (a real, verified 161-line file) both inline and in a References section, fitting the well-signaled one-level-deep score-3 anchor rather than inline-bloat score-2.

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 tight, high-signal description that names concrete capabilities, gives explicit use/do-not-use triggers, and is cleanly distinguished from sibling skills. It earns top marks across all dimensions with no padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'the protobuf codec, the SSE format, content negotiation, the JsonElement-to-protobuf Value bridge, or a brand new encoding' — matching the score-3 anchor rather than the single-domain score-2 anchor.

3 / 3

Completeness

It states both what ('Add or modify a wire transport / event-stream encoding...') and when via explicit 'USE FOR' / 'DO NOT USE FOR' triggers, clearing the explicit-trigger bar that would otherwise cap at 2.

3 / 3

Trigger Term Quality

The 'USE FOR' clause covers the API surface a developer on this SDK would naturally name (AGUI.Formatting, AGUI.Protobuf, IAGUIEventStreamFormatter, SSE/protobuf framing, AGUIResults.Events), giving good natural-term coverage rather than the sparse score-2 case.

3 / 3

Distinctiveness Conflict Risk

A narrow AG-UI .NET transport/encoding niche plus 'DO NOT USE FOR' routing to sibling skills (agui-dotnet-wire-types, agui-dotnet-integration-tests) makes wrong-skill conflict very 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.