Conciseness

Each section is 1–2 sentences of genuinely non-obvious SDK behavior ('the server is stateless and keeps nothing between turns', 'a non-null ConversationId would make wrappers send only deltas') followed by a concrete Fix — no padding and no explanation of concepts Claude already knows. Matches the lean 'every token earns its place' anchor.

Actionability

Every fix names the exact executable API (history.AddMessages(updates.ToChatResponse()), AIFunctionFactory.Create(method, serializerOptions: ctx.Options), .UseFunctionInvocation(fic => fic.TerminateOnUnknownCalls = true)), plus a copy-paste curl command and a runnable C# pattern for RawEvent inspection. Fully executable guidance covering the common cases.

Workflow Clarity

A clear symptom→cause→fix structure with an explicit final validation step ('reproduce the original prompt and confirm the symptom is gone against the wire stream'), giving the diagnostic loop a feedback checkpoint. No destructive/batch operation applies, so the cap at 3 is not triggered.

Progressive Disclosure

The skill is self-contained with no bundle files; each per-symptom section is only a few lines and well-signaled with headers, so nothing that belongs in a separate file is inlined and navigation is trivial.

Specificity

Lists multiple concrete capabilities (diagnose/fix streaming chat, tools, state, interrupts, transport problems) plus a comprehensive itemized symptom list ('update.ConversationId always null', '406 Not Acceptable', 'AOT/trim warnings'), matching the comprehensive-coverage anchor rather than the minor-gaps anchor at 4. No vague fluff, no first/second-person voice.

Completeness

Explicitly answers 'what' ('Diagnose and fix problems in an AG-UI .NET app built on the AG-UI SDK') and 'when' with a concrete 'USE FOR:' trigger list plus a 'DO NOT USE FOR:' clause. Both are explicit and concrete, matching the top anchor rather than the less-explicit 'when' of 4.

Trigger Term Quality

The symptom phrases are exactly what a user would naturally say ('history truncated', 'always null', '406 Not Acceptable', 'interrupt or approval that won't resume', 'AOT/trim warnings'), including synonyms and wire-level terms (curl SSE frames, RawEvent) — comprehensive natural-term coverage, above the 'a few natural terms missing' anchor at 4.

Distinctiveness Conflict Risk

Clear troubleshooting niche with distinct symptom triggers, and explicit disambiguation against sibling skills ('use agui-dotnet-streaming-chat' for the happy path, 'use the matching agui-dotnet-* skill' for clean feature work) minimizes conflict risk.