agui-dotnet-cross-language-tests

Author cross-language interop tests that verify the AG-UI .NET SDK is wire-compatible with the TypeScript SDK — a Vitest TS client driving a C# CrossLanguage.TestServer over HTTP, both directions, including protobuf byte-parity against @ag-ui/proto. USE FOR: adding or modifying cross-language interop coverage, CrossLanguage.TestServer routes, the CrossLanguage.Vitest suite, protobuf wire parity tests, TS-client-to-C#-server or C#-client-to-TS-server scenarios. DO NOT USE FOR: .NET-only unit tests (use agui-dotnet-unit-tests), ASP.NET Core hosting integration tests (use agui-dotnet-integration-tests).

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%

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 body with clear sequenced workflows and concrete code/commands, assuming Claude's competence throughout. Its one weakness is progressive disclosure: a sizeable amount of parity/transport detail is inline with no bundle reference files to offload it into.

Suggestions

Move the protobuf wire-parity table and the transport-parity deep-dive into reference files under references/ (e.g. PROTOBUF-PARITY.md, TRANSPORT-PARITY.md), leaving SKILL.md as a concise overview that links one level deep.

Add a short 'When to read the full doc' pointer at the top so Claude knows which inline sections are summary vs which to consult cross-language-testing.md for, reinforcing the one-level reference discipline.

If the harness reference section in cross-language-testing.md already covers the route/transport mechanics, trim the inline restatement in SKILL.md to a pointer to avoid duplication.

Dimension	Reasoning	Score
Conciseness	Lean and dense with specifics (exact paths, the `fileParallelism: false` and `Accept`-header-override gotchas) and no padding with concepts Claude already knows; every token earns its place.	3 / 3
Actionability	Provides fully executable guidance — concrete route patterns (`MapPost` → `input.ToChatRequestContext(...)` → ...), exact commands (`pnpm test`, `dotnet test`), and copy-paste-ready TS `describe.each(TRANSPORTS)` and assertion code.	3 / 3
Workflow Clarity	Both phases have numbered, sequenced step lists with explicit registration checkpoints (Program.cs AND CrossLanguageJsonSerializerContext.cs), and the 'Critical anti-patterns' section acts as validation/feedback-loop guardrails.	3 / 3
Progressive Disclosure	Well-organized sections and one clearly-signaled one-level reference (`cross-language-testing.md`), but no bundle files exist and substantial inline detail (protobuf/transport parity tables and deep-dives) reads as content that, at ~185 lines, would benefit from being split into separate reference files.	2 / 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, third-person description that cleanly states what the skill does, when to use it, and when not to. Trigger terms are natural to the domain and the conflict guidance is explicit.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Author cross-language interop tests', 'driving a C# CrossLanguage.TestServer over HTTP, both directions', 'protobuf byte-parity against @ag-ui/proto' — rather than vague language.	3 / 3
Completeness	Explicitly answers what (author wire-compat interop tests in both directions) and when ('USE FOR:' triggers), plus a 'DO NOT USE FOR' disambiguation clause.	3 / 3
Trigger Term Quality	The 'USE FOR' clause surfaces natural trigger terms users would say — 'cross-language interop coverage', 'protobuf wire parity tests', 'TS-client-to-C#-server', 'C#-client-to-TS-server'.	3 / 3
Distinctiveness Conflict Risk	Narrow cross-language niche with distinct triggers and an explicit 'DO NOT USE FOR' pointing at sibling skills (agui-dotnet-unit-tests, agui-dotnet-integration-tests), making conflicts unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ag-ui-protocol/ag-ui
Path: .github/skills/agui-dotnet-cross-language-tests/SKILL.md
Commit: 34c3e0c

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.