Content
71%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 highly actionable, project-specific troubleshooting skill with copy-paste commands, explicit user-confirmation checkpoints for the destructive retry path, and a real error-recovery section. Its main weaknesses are redundancy between the Task and Implementation Steps sections and a progressive-disclosure structure whose two most-referenced files are missing from the bundle.
Suggestions
Delete the "## Task" section (or collapse it into a two-line phase overview) — its Phase 1/Phase 2 bullet lists are fully restated under "## Implementation Steps".
Add failure-patterns.md and scripts-reference.md to the bundle or fix the links (they are cited ~9 times but only references/cli-reference.md ships); consider also moving the Timeline Record Structure and snapshot-mismatch fine print into a reference file.
Add a verification step after the UpdateSnapshotsFromBuild command (e.g., re-run the affected test or show the resulting diff) to close the loop on the snapshot-update workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly dense, non-obvious project knowledge (API quirks, field names, exact commands) that earns its tokens, but the "## Task" section re-lists both phases that "## Implementation Steps" then details in full, "## Additional Resources" repeats links already given inline, and a few over-hedged multi-clause sentences (e.g., "Missing spans can result from instrumentation defects, startup/transport failures, or timing; the count alone does not prove a deterministic regression or rule out flakiness") could be tightened. This fits "mostly efficient but includes some unnecessary explanation or could be trimmed" better than the minor-trim level 4. | 3 / 5 |
Actionability | Commands are copy-paste ready for every invocation pattern ("pwsh -NoProfile -Command \".\\tracer\\tools\\Get-AzureDevOpsBuildAnalysis.ps1 -BuildId $BUILD_ID -Verbose\"", "./tracer/build.ps1 UpdateSnapshotsFromBuild --BuildId <BUILD_ID>", "gh pr checks <PR> --repo DataDog/dd-trace-dotnet") and include concrete failure-specific workarounds ("The az devops invoke --resource logs API returns HTTP 500, so avoid it"). Example 1 shows a full realistic output block, so the common cases are covered. | 5 / 5 |
Workflow Clarity | The two-phase sequence is clearly gated ("DO NOT perform these steps automatically", "ONLY IF USER REQUESTS") and the state-mutating retry path has explicit checkpoints ("Run with -WhatIf first to preview", "Confirm with user — Show the list of stages that would be retried and ask for confirmation") plus a re-check feedback loop ("After retrying, offer to re-run the analysis script later"). It falls short of a 5 because Phase 1 steps 1-4 are bundled into one "Step 1-4: Run Quick Analysis Script" block, the workflow is spread across four sections with Task/Implementation-Steps duplication, and there is no verification step after updating snapshots. | 4 / 5 |
Progressive Disclosure | The load-condition signaling is good where it exists ("Load ONLY during Phase 2 categorization", "Load ONLY if the PowerShell script fails"), but scored against the actual bundle: "failure-patterns.md" and "scripts-reference.md" are referenced throughout yet are not present (only references/cli-reference.md exists), making those navigation paths dead ends. Detail-heavy sections (Timeline Record Structure, snapshot-mismatch fine print, full Example 1 output) are inlined where reference files would be appropriate, matching "some structure but could be better organized" better than level 4's "references mostly clear". | 3 / 5 |
Total | 15 / 20 Passed |