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

87%

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

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 tight, highly actionable body with concrete commands, code, and tables, plus clear two-phase workflows and an anti-patterns guardrail section. It assumes Claude's competence and avoids concept padding, with only minor room to tighten version specifics and add an explicit validate-retry loop in the authoring workflows.

Suggestions

Add an explicit validate-checkpoint step (e.g. 'run `pnpm test` for the new route and confirm it passes before moving on') inside the Phase 1/Phase 2 authoring workflows to close the feedback-loop gap.

Move the long protobuf `byteParity` strict-vs-roundtrip rules into a referenced doc or table and keep a one-line summary inline, reducing the inlined detail that could live one level deeper.

Isolate the time-sensitive version requirements (.NET 10 SDK, pnpm 10+, Node version) into a dedicated 'Requirements' note so they don't read as workflow instruction.

Dimension	Reasoning	Score
Conciseness	Dense and assumes Claude's competence (no padding explaining Vitest, xUnit, protobuf, or SSE), with every section earning its place; minor instances of version-specific detail ('.NET 10 SDK', 'pnpm 10+') and slightly long transport section keep it just short of fully lean.	4 / 5
Actionability	Fully executable guidance: copy-paste run commands ('pnpm test', 'dotnet test'), a complete `describe.each(TRANSPORTS)` code block, concrete route tables, and exact file paths covering the common cases.	5 / 5
Workflow Clarity	Clear numbered sequences for both directions (5-step Phase 1, 3-step Phase 2) with explicit registration checkpoints (Program.cs AND CrossLanguageJsonSerializerContext.cs) reinforced by a Critical anti-patterns section; lacks an explicit validate-then-retry feedback loop within the authoring steps.	4 / 5
Progressive Disclosure	Well-organized into distinct sections (philosophy, architecture, scenario types, protobuf, transport, running, anti-patterns) with clearly signaled one-level-deep references to external repo docs (sdks/dotnet/docs/cross-language-testing.md); no bundle files exist, so the score reflects structure plus signaled external references, with minor inlining of detail that could live in reference files.	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 highly specific, well-scoped description that clearly states what the skill does, when to use it, and when not to use it with routing to adjacent skills. Trigger terms are thorough but skew toward project-specific jargon over universally natural phrasing.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Author cross-language interop tests', 'Vitest TS client driving a C# CrossLanguage.TestServer over HTTP, both directions, including protobuf byte-parity against @ag-ui/proto' — with comprehensive coverage of the skill's scope.	5 / 5
Completeness	Explicitly answers both 'what' (author cross-language interop tests verifying wire-compatibility) and 'when' via concrete 'USE FOR'/'DO NOT USE FOR' trigger phrases that also route to sibling skills.	5 / 5
Trigger Term Quality	Good keyword coverage with natural variations ('TS-client-to-C#-server', 'C#-client-to-TS-server', 'both directions', 'protobuf wire parity tests'), though the terms are largely project-specific jargon rather than broadly natural phrasings a user would say verbatim.	4 / 5
Distinctiveness Conflict Risk	Clear niche (cross-language interop) with an explicit 'DO NOT USE FOR' clause redirecting .NET-only unit tests and ASP.NET Core hosting integration tests to sibling skills, minimizing conflict risk.	5 / 5
	Total	19 / 20 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: 821b8c2

Reviewed: 1 day 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.