CtrlK
BlogDocsLog inGet started
Tessl Logo

agui-dotnet-agents-sync

Keep the AG-UI .NET SDK docs (sdks/dotnet/AGENTS.md and docs/architecture.md) in sync with the real code tree after structural changes. USE FOR: "update AGENTS.md / docs/architecture.md", "check the dotnet docs are current", verifying docs after a .NET SDK refactor (package rename, added/removed project, changed endpoint pattern, new/renamed test project, sample step added, new convention). DO NOT USE FOR: writing product code or tests (follow AGENTS.md itself), Python/TypeScript SDK docs, or generic markdown editing unrelated to the dotnet SDK structure.

74

Quality

91%

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

88%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 well-organized, highly actionable body with executable PowerShell commands, an explicit verification feedback loop, and a useful drift checklist. The main improvement opportunity is reducing the repeated 'derive from the tree' emphasis that recurs across several sections.

Suggestions

Consolidate the 'derive ground truth from the tree, not from prose' guidance so it is stated once authoritatively and referenced, rather than repeated in the intro blockquote, Process steps, anti-patterns, and Deriving ground truth section.

The Drift checklist table and the Deriving ground truth command block overlap in the commands they prescribe; consider merging the command snippets into the table to avoid stating the same Select-String/Get-ChildItem invocations twice.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes Claude's competence, but the 'derive from the tree, don't trust prose' message is reinforced across the intro blockquote, Process steps 1-2, anti-pattern 1, and the 'Deriving ground truth' intro, which could be tightened without losing the point.

4 / 5

Actionability

Copy-paste-ready PowerShell commands (Select-String, Get-ChildItem with specific patterns/filters) and a drift-checklist table mapping each doc claim to a concrete reconciliation command fully cover the common cases.

5 / 5

Workflow Clarity

A clear four-step Process sequence includes an explicit 'Verify' step (re-grep every symbol written) forming a validate-fix-retry feedback loop, plus a drift checklist for complex reconciliation.

5 / 5

Progressive Disclosure

The skill is self-contained with well-organized sections (Process, Drift checklist, Deriving ground truth, Anti-patterns, Files to mine) and no nested references; it sits slightly above the ~50-line simple-skill threshold, so it is well-structured rather than optimally split.

4 / 5

Total

18

/

20

Passed

Description

95%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, tightly-scoped description that answers both what and when with concrete, natural trigger phrases and an explicit boundary clause. The only minor weakness is that the underlying capability is a single action family, so the specificity of distinct actions is good rather than comprehensive.

DimensionReasoningScore

Specificity

Names the domain and concrete actions ('Keep ... docs in sync with the real code tree', 'verifying docs after a .NET SDK refactor') with several specific trigger scenarios; the action set itself is narrow (reconcile docs against tree), leaving minor coverage gaps rather than a comprehensive multi-action list.

4 / 5

Completeness

It explicitly states what the skill does ('Keep the AG-UI .NET SDK docs ... in sync with the real code tree') and when to use it via an explicit USE FOR clause with concrete trigger phrases, plus a DO NOT USE FOR boundary.

5 / 5

Trigger Term Quality

Quoted USE FOR phrases ('update AGENTS.md / docs/architecture.md', 'check the dotnet docs are current') plus a concrete refactor-scenario list and a DO NOT USE FOR boundary give comprehensive coverage of the natural terms a user would say for this niche.

5 / 5

Distinctiveness Conflict Risk

The niche is sharply defined (AG-UI .NET SDK docs sync) and the DO NOT USE FOR clause excludes Python/TypeScript SDK docs and generic markdown editing, giving clear distinct triggers 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.