CtrlK
BlogDocsLog inGet started
Tessl Logo

agui-dotnet-sample-step

Add a GettingStarted sample Step (a Server/Client pair) to the AG-UI .NET SDK that demonstrates one protocol feature the way we want users to write it. USE FOR: adding a new samples/GettingStarted/StepNN_<Name> Server+Client pair, wiring it into AGUI.slnx and the integration-test project, giving it a deterministic FakeChatClient for replay, and registering it in the Step tables in AGENTS.md / docs/architecture.md. DO NOT USE FOR: the replay/Verify integration-test mechanics (use agui-dotnet-integration-tests), the dojo scenarios under samples/AGUIClientServer (use agui-dojo), or protocol/wire changes the sample exercises (use agui-dotnet-wire-types / agui-dotnet-transport).

70

Quality

85%

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

78%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 strong, lean instruction set with concrete code, exact paths, an explicit verify step, and clear routing to sibling skills. The main gaps are a few trimmable rationale sentences and a Server skeleton left to prose/mirroring rather than inline code.

Suggestions

Tighten rationale sentences (e.g. 'The IChatClient is the whole point...') to directives, or drop them, to push conciseness toward a 5.

Add a minimal copy-paste Server Program.cs skeleton (AddAGUI/IChatClient/MapAGUI) alongside the Client block so the Server side is as executable as the Client.

Add a short validate-then-fix retry note in Verify (e.g. 'if build/test fails, fix and re-run') to make the feedback loop explicit.

DimensionReasoningScore

Conciseness

The body is dense and project-specific, assuming competence (no ASP.NET/MEAI primers), but a few rationale sentences like 'The IChatClient is the whole point...' and 'Replayable determinism is what lets the integration test record once and replay forever' could be trimmed.

4 / 5

Actionability

Provides a copy-paste Client code block, concrete dotnet build/test commands, and exact file paths/csproj refs, but the Server Program.cs is described in prose rather than a full executable skeleton (mitigated by 'mirror the closest existing Step').

4 / 5

Workflow Clarity

The Wiring section is a clearly numbered 1-4 sequence with an explicit Verify block (build + test + end-to-end run) and a 'list Step* first — never assume the range' checkpoint, though error-recovery feedback loops are only lightly sketched.

4 / 5

Progressive Disclosure

Well-organized into Anatomy / Wiring / Verify / Anti-patterns / References with one-level-deep, clearly signaled routing to sibling skills; content is appropriately self-contained with no nested or buried references.

5 / 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.

The description is exemplary: concrete actions, explicit USE FOR / DO NOT USE FOR trigger guidance, and clear boundary routing to sibling skills. Its only mild weakness is the heavily technical vocabulary, which lacks the synonyms/extensions a broader-audience skill would include.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Add a GettingStarted sample Step (a Server/Client pair)', 'wiring it into AGUI.slnx and the integration-test project', 'giving it a deterministic FakeChatClient for replay', 'registering it in the Step tables' — covering the task comprehensively with no vague filler.

5 / 5

Completeness

Explicitly states both what it does ('Add a GettingStarted sample Step... that demonstrates one protocol feature') and when to use it via concrete 'USE FOR:' trigger phrases plus boundary guidance, satisfying the top anchor.

5 / 5

Trigger Term Quality

Strong, domain-natural trigger phrases ('GettingStarted sample Step', 'Server/Client pair', 'AGUI.slnx', 'FakeChatClient', 'Step tables') with explicit 'USE FOR' / 'DO NOT USE FOR' triggers, but the terms are highly technical with few synonyms or extensions for broader coverage.

4 / 5

Distinctiveness Conflict Risk

A clear narrow niche with explicit 'DO NOT USE FOR' routing to sibling skills (agui-dotnet-integration-tests, agui-dojo, agui-dotnet-wire-types, agui-dotnet-transport), minimizing 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.