Content
67%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured, operationally rich investigation skill that delegates MAUI facts to a canonical doc and gives concrete parameterized commands for the nightly-build path. Its main weakness is the long inlined historical root-cause narrative, which costs conciseness and would sit better in a separate reference.
Suggestions
Move the Jun 2026 inflight/current outage root-cause narrative (PR #32203, commit 543b1ebeb7, #36089) into a dated reference file or the canonical doc, keeping only the recurring MSB4019 signature and the short triage lesson ('confirm IsPackable evaluates true in pack.binlog and that _GenerateVSWorkloadProps ran') inline.
Add a fallback for the nightly path when internal AzDO access is unavailable (e.g., who to page or what anonymous signal can substitute), since definition 1095 requires dnceng/internal.
Tighten the MAUI CI facts bullet list — it previews the canonical doc's contents at length; a shorter pointer would preserve navigation while cutting tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly lean — MAUI facts are delegated to the canonical doc ('Do not restate those facts from memory') and the nightly section is dense with operational specifics. However, the ~250-word 'Root cause of the Jun 2026 inflight/current outage' paragraph inlines time-sensitive historical narrative (PR numbers, commit hash 543b1ebeb7, dates) that is not placed in an 'old patterns'/'deprecated' section and could be tightened or split out. | 3 / 5 |
Actionability | Concrete parameterized tool calls ('azdo_builds with definitionId: 1095, branch: refs/heads/inflight/current', 'azdo_search_timeline (filter failed)'), exact pipeline IDs, an exact recurring error signature (MSB4019 vs-workload.props), and file paths make the nightly path near copy-paste ready. Minor gap: the most common case (PR investigation) delegates execution to the ci-analysis skill and the canonical doc rather than showing runnable commands itself. | 4 / 5 |
Workflow Clarity | 'Using this skill' gives a numbered 1–4 sequence with escalation, and the nightly section is an explicit three-step chain (azdo_builds → azdo_search_timeline → azdo_search_log) plus 'confirm whether it's a one-off or a multi-day streak'. Validation cross-checks exist (baseline comparison, XHarness exit-0, binlog IsPackable check), but there are minor gaps — e.g., no guidance when internal AzDO access is unavailable for definition 1095. | 4 / 5 |
Progressive Disclosure | No bundle files exist; the single external reference ('.github/docs/maui-ci-facts.md — read it') is clearly signaled, one level deep, with an itemized coverage list, and sections are well organized. The inlined Jun 2026 outage root-cause narrative is content that arguably belongs in a separate reference file, keeping this a 4 rather than a 5. | 4 / 5 |
Total | 15 / 20 Passed |