CtrlK
BlogDocsLog inGet started
Tessl Logo

agui-dotnet-streaming-chat

Get started with the AG-UI .NET SDK: bootstrap and run your first streaming-chat app (client + server) with the AG-UI .NET NuGet packages (AGUI.Client, AGUI.Server, AGUI.Formatting, AGUI.Abstractions). USE FOR: which packages to install and how to wire them; constructing an AGUIChatClient against an endpoint and streaming the reply as Microsoft.Extensions.AI IChatClient / ChatResponseUpdate; hosting an AG-UI POST endpoint yourself over any IChatClient; running a single- or multi-turn conversation; STATELESS agents (client owns history, resends it every turn) vs HOSTED / conversation-holding agents (server keeps the session, client pins a thread id). DO NOT USE FOR: changing the AG-UI .NET SDK itself (use the agui-dotnet-* contributor skills); server tools (agui-dotnet-server-tools); client tools (agui-dotnet-client-tools); interrupts / human-in-the-loop; shared state; generative UI; multimodal; or protobuf transport.

72

Quality

87%

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

82%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 highly actionable getting-started guide with executable client and server code, a clear run-it section, and useful anti-patterns. It is concise and well-structured; the only minor gaps are a missing error-recovery loop and no external reference split.

DimensionReasoningScore

Conciseness

The body is code-dense and mostly earns its tokens on non-obvious SDK behavior (thread-id pinning, ConversationId null by design, full-history resend); a few prose passages like the issue-#4869 aside could be trimmed but overall it assumes Claude's competence.

4 / 5

Actionability

Provides copy-paste-ready, complete code for client construction, server hosting via MapPost, multi-turn history carrying, a curl smoke test, and hosted-agent patterns — fully executable across the common cases.

5 / 5

Workflow Clarity

A clear 'Run it (definition of done)' sequence with numbered steps and a smoke-test checkpoint, plus an explicit done condition; lacks a full validate-fix-retry feedback loop but the task is non-destructive so this is a minor gap.

4 / 5

Progressive Disclosure

Well-organized single-file structure with clear section headers and an appropriate 'read this first' framing; no external bundle files exist, so everything is inline, which is reasonable for a getting-started skill though the hosted-agent section could arguably be split out.

4 / 5

Total

17

/

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 strong, highly specific description with explicit use/avoid triggers and concrete package names. It is comprehensive and clearly distinguishable from sibling skills; only trigger-term naturalness is mildly reduced by jargon.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'bootstrap and run your first streaming-chat app', 'constructing an AGUIChatClient', 'hosting an AG-UI POST endpoint', 'running a single- or multi-turn conversation', and the stateless vs hosted distinction — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Clearly answers 'what' (bootstrap and run a streaming-chat app with named packages) and 'when' via explicit 'USE FOR' and 'DO NOT USE FOR' clauses with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ('streaming-chat app', 'hosting an AG-UI POST endpoint', 'multi-turn conversation') plus explicit 'USE FOR'/'DO NOT USE FOR' triggers, but the language leans heavily on technical identifiers (NuGet, IChatClient, ChatResponseUpdate) and lacks some plain synonyms.

4 / 5

Distinctiveness Conflict Risk

A clear niche (AG-UI .NET streaming chat) with explicit 'DO NOT USE FOR' routing to sibling skills (server tools, client tools, interrupts, generative UI), giving minimal conflict risk.

5 / 5

Total

19

/

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.

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.