CtrlK
BlogDocsLog inGet started
Tessl Logo

agui-dotnet-feature-workflow

Orchestrator/hub for implementing a feature or change in the AG-UI .NET SDK (sdks/dotnet). USE FOR: "what's the workflow", "what order do I do things in", "how do I implement a feature in the .NET SDK", starting any non-trivial AG-UI .NET SDK change, planning the end-to-end steps and definition-of-done (code + AOT serialization + client/server mapping + unit/integration/cross-language tests + docs + PublicAPI + AGENTS.md sync). DO NOT USE FOR: the deep how-to of a single step — this skill ROUTES to focused siblings: adding wire types (agui-dotnet-wire-types), transport/encoding (agui-dotnet-transport), unit tests (agui-dotnet-unit-tests), integration tests (agui-dotnet-integration-tests), cross-language tests (agui-dotnet-cross-language-tests), porting from TS/Python (agui-cross-sdk-parity), adding a GettingStarted sample Step (agui-dotnet-sample-step), SDK docs (agui-dotnet-sdk-docs), AGENTS/Architecture sync (agui-dotnet-agents-sync), the dojo (agui-dojo), review (agui-dotnet-code-review).

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 well-structured hub skill with a clear ordered workflow, concrete build/test commands, and strong progressive disclosure through sibling routing. The main weakness is redundant routing information repeated across the description, the workflow steps, and the routing table.

Suggestions

Remove or compress the standalone 'Routing table (quick reference)' since the ordered workflow already embeds each sibling inline and the description enumerates them too — keeping one authoritative routing surface would save significant tokens.

Consider noting in the body that the description's USE FOR / DO NOT USE FOR list is the authoritative at-a-glance routing, so the body can avoid re-listing every sibling and focus on sequencing.

DimensionReasoningScore

Conciseness

The body is lean and avoids explaining concepts Claude already knows, but routing information is triplicated — the description, the inline sibling references in the ordered workflow, and the standalone routing table all repeat the same skill map — so it could be tightened.

2 / 3

Actionability

Provides concrete, executable commands ('dotnet build sdks/dotnet/AGUI.slnx', 'dotnet test tests/AGUI.Abstractions.UnitTests/') and names specific files and symbols (PublicAPI.Unshipped.txt, AGUIJsonSerializerContext, EventStreamConverter).

3 / 3

Workflow Clarity

A 12-step ordered workflow with a definition-of-done checklist and an explicit validation gate at step 11 (build + test green) and review gate at step 12, plus warnings-as-errors enforcement notes that function as feedback loops.

3 / 3

Progressive Disclosure

As an orchestrator it routes depth to one-level-deep sibling skills and falls back to canonical AGENTS.md / docs/architecture.md, with well-organized sections and no nested-reference chains; no bundle files exist to verify.

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 strong, highly specific description that clearly states what the skill does, when to use it, and when to route to siblings. Its only weakness is verbosity — the sibling enumeration is long — but every part is informative rather than fluffy.

Suggestions

The description is dense; consider trimming the DO NOT USE FOR sibling list to the most conflict-prone cases and letting the body's routing table carry the full enumeration, since that list is already duplicated in the body.

DimensionReasoningScore

Specificity

Lists multiple concrete artifacts and actions — 'code + AOT serialization + client/server mapping + unit/integration/cross-language tests + docs + PublicAPI + AGENTS.md sync' — naming specific deliverables rather than vague capabilities.

3 / 3

Completeness

Explicitly answers both 'what' (orchestrator/hub for implementing a feature or change in the AG-UI .NET SDK) and 'when' (USE FOR / DO NOT USE FOR clauses with concrete triggers).

3 / 3

Trigger Term Quality

Includes natural phrases a user would actually say — 'what's the workflow', 'what order do I do things in', 'how do I implement a feature in the .NET SDK' — giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

A tightly scoped .NET SDK orchestrator with a DO NOT USE FOR clause distinguishing it from 11 named sibling skills, making wrong-skill triggering 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.