CtrlK
BlogDocsLog inGet started
Tessl Logo

agui-dotnet-sdk-docs

Author, update, and validate the AG-UI .NET SDK documentation pages on the docs.ag-ui.com Mintlify site (under docs/). USE FOR: adding or editing a ".NET SDK" docs page (sdk/dotnet/**/*.mdx), wiring it into the docs.json ".NET" nav group and global anchor, running the docs site locally with mintlify dev, previewing/validating rendered .NET pages, checking the .NET sidebar anchor/icon. DO NOT USE FOR: in-repo dotnet markdown such as sdks/dotnet/AGENTS.md or docs/architecture.md (use agui-dotnet-agents-sync); TypeScript/Python docs pages; product code, tests, or wire types.

69

Quality

83%

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

75%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, actionable docs-authoring skill with concrete commands, a clear workflow, explicit validation, and useful operational gotchas. The main improvement room is in tightening the repeated restart-on-docs.json guidance and making the Playwright validation loop more self-contained.

Suggestions

Consolidate the 'restart mintlify dev for docs.json changes' guidance into one place (step 4, the quirks list, and anti-pattern #2 all restate it) to recover conciseness.

Inline a minimal Playwright-MCP validation snippet instead of only referencing the agui-playwright-validate skill, so the validate-fix-retry loop is self-contained and workflow_clarity can reach 5.

Add a one-line explicit 'after fixing, re-run the page assertions until all pass' retry instruction to close the feedback loop in the validation section.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's competence with no basic-concept padding; the 'Known quirks' and 'Critical anti-patterns' sections earn their tokens. Minor restatement of the restart-on-docs.json point across three sections keeps it just under 5.

4 / 5

Actionability

Provides concrete, copy-paste-ready commands ('node_modules/.bin/mintlify dev --port=4000', 'dotnet add package AGUI.*') and exact nav-string format, with minor gaps where validation leans on an external skill.

4 / 5

Workflow Clarity

Clear sequenced steps with an explicit restart checkpoint and a validation loop with concrete assertions (HTTP 200, H1 match, zero console errors); falls just short of 5 because the validate-fix-retry loop is prose-asserted and delegates technique to another skill.

4 / 5

Progressive Disclosure

Self-contained, well-sectioned file with a clearly signaled 'Files to mine' pointer list to repo paths; no bundle files exist so there is nothing to mis-split, and nothing monolithic is inlined.

4 / 5

Total

16

/

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 strong, concrete description with explicit what/when guidance and clear boundary disambiguation against sibling skills. The only soft spot is keyword phrasing that leans technical rather than covering broad natural synonyms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across the full task surface ('Author, update, and validate', 'wiring it into the docs.json .NET nav group and global anchor', 'running the docs site locally with mintlify dev', 'checking the .NET sidebar anchor/icon'), matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly answers both 'what' (author/update/validate .NET docs pages on Mintlify) and 'when' via concrete 'USE FOR:' and 'DO NOT USE FOR:' trigger clauses, exceeding the anchor-5 example.

5 / 5

Trigger Term Quality

Strong, natural keyword coverage ('.NET SDK docs page', 'docs.json', 'mintlify dev', 'sidebar anchor/icon') but the terms lean technical-jargon rather than the broad synonym-plus-extension spread the anchor-5 example shows.

4 / 5

Distinctiveness Conflict Risk

The 'DO NOT USE FOR' clause explicitly separates it from sibling skills (agui-dotnet-agents-sync, TypeScript/Python docs, product code), giving a clear niche with minimal 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.