CtrlK
BlogDocsLog inGet started
Tessl Logo

agui-dotnet-integration-tests

Write integration tests for the AG-UI .NET SDK. USE FOR: adding a new AG-UI event type and covering it end-to-end, testing SSE or protobuf streaming through the hosting pipeline, verifying AGUIChatClient maps events to ChatResponseUpdate, multi-turn conversation tests, parameterizing a test over Json/Protobuf transports, adding or updating a GettingStarted sample replay/Verify snapshot. Covers: WebApplicationFactory + DelegatingStreamingChatClient setup, IChatClient-based assertions with Assert.Collection, TransportFormat [Theory] (Json/Protobuf), recording/replay capture infrastructure, and the 8-capture-point Verify baselines. DO NOT USE FOR: unit tests of event serialization (use tests/AGUI.Abstractions.UnitTests) or stream-conversion unit tests (use tests/AGUI.Server.UnitTests).

75

Quality

92%

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

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, highly actionable reference for a complex integration-test codebase, with a clear numbered procedure, validation feedback loops for baselines, and appropriate deferral to external docs; the main weakness is mild redundancy between the Procedure, Transport, and Key rules sections.

Suggestions

Collapse the redundancy between "Transport parameterization", the "Procedure" steps, and "Key rules" — state the parametrize-over-TransportFormat rule once and reference it, rather than repeating it three times.

Consider moving the 8-capture-point baseline table and full project-layout tree into a bundled reference file so SKILL.md stays a leaner overview that points to the detail.

Tighten the Orientation/Architecture prose where it re-describes pipeline mechanics already implied by the code examples, to recover token budget.

DimensionReasoningScore

Conciseness

It assumes Claude's competence (no explainer text on SSE, protobuf, WebApplicationFactory, or xUnit Theories) and the dense reference material mostly earns its place, but the "Key rules" section restates guidance already given in "Transport parameterization" and the "Procedure" (e.g. parametrizing over TransportFormat appears three times), so it could be tightened.

2 / 3

Actionability

It provides executable, copy-paste-ready code throughout — the CreateClient(handler, format) pattern, a full [Theory]/[InlineData] test with Assert.Collection assertions, Emit-helper signatures, the sample CreateCapturingClient pattern, and the dotnet test build command.

3 / 3

Workflow Clarity

The "Procedure: writing a new integration test" is a clear 6-step numbered sequence, and "Updating baselines" adds an explicit review→accept feedback loop (VERIFY_ACCEPT, "review them before committing") for the risky batch snapshot operation.

3 / 3

Progressive Disclosure

It is well-organized into clear sections and defers orientation to one-level-deep external references (sdks/dotnet/AGENTS.md and docs/architecture.md) with no multi-level nesting; no bundle files are provided to evaluate against.

3 / 3

Total

11

/

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, well-scoped description that answers both what and when with explicit USE FOR / DO NOT USE FOR triggers and natural domain keywords, in correct third-person voice.

DimensionReasoningScore

Specificity

Enumerates many concrete actions — "adding a new AG-UI event type and covering it end-to-end", "testing SSE or protobuf streaming through the hosting pipeline", "verifying AGUIChatClient maps events to ChatResponseUpdate", "multi-turn conversation tests", "parameterizing a test over Json/Protobuf transports" — rather than vague language.

3 / 3

Completeness

It states what the skill does ("Write integration tests for the AG-UI .NET SDK") and gives explicit when-triggers via both "USE FOR:" and "DO NOT USE FOR:", answering both what and when.

3 / 3

Trigger Term Quality

The "USE FOR:" clause covers the natural terms a developer in this SDK would say ("integration tests", "SSE or protobuf streaming", "multi-turn conversation", "Json/Protobuf transports", "Verify snapshot") with good variation rather than generic jargon.

3 / 3

Distinctiveness Conflict Risk

It carves a clear niche (AG-UI .NET SDK integration tests) and the "DO NOT USE FOR:" clause explicitly routes serialization and stream-conversion unit tests to other projects, making conflict 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.