Content
77%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.
Highly actionable and clearly sequenced reference content with excellent troubleshooting feedback loops, undermined by token inefficiency: a verbatim-duplicated cheat sheet and long inline scripts pad the file. It is also entirely monolithic — no reference files exist to move the attribute guide, TRX parsing, and VS details into.
Suggestions
Delete or radically shrink the Quick-Reference Command Cheat Sheet — it repeats the exact commands from sections 1, 3, and 4 (~30 duplicated lines) in a single-file skill where the numbered sections already serve as the quick reference.
Move the TRX-parsing PowerShell script and the test-attribute/category table into a references/ file (e.g. references/parsing-results.md, references/test-attributes.md) with one-line pointers from the main body, keeping SKILL.md as a lean overview.
Either vendor the VS-specific content (docs\testing-in-vs.md) into the bundle as references/visual-studio.md or drop the dangling pointer, so every 'see X' reference resolves inside the skill itself.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly dense, useful commands and tables, but the "Quick-Reference Command Cheat Sheet" restates ~30 lines of commands verbatim from sections 1, 3, and 4 (the same filter-method, filter-class, wildcard, --list-tests, and DOTNET_ROOT examples), and the 12-line TRX-parsing PowerShell script is more than the core workflow needs inline. It could be meaningfully tightened, matching 'mostly efficient but includes some unnecessary content'. | 3 / 5 |
Actionability | Every workflow ships copy-paste-ready commands with concrete paths (e.g. `& "artifacts\bin\System.Windows.Forms.Tests\Debug\net11.0-windows7.0\System.Windows.Forms.Tests.exe" --filter-method "..."`), executable option tables, a project-path table, and a working PowerShell script. The TFM drift risk is even handled explicitly ("Check artifacts\bin\... for the actual TFM directory name"), and common failure modes get exact fixes — fully executable coverage of the common cases. | 5 / 5 |
Workflow Clarity | Sequences are clear and ordered (full build → project directory → executable invocation), prerequisites are explicit ("After a full build", DOTNET_ROOT setup), and error recovery is thorough: expected failure "Zero tests ran" with exit code 5 maps to a named alternative, "framework not found" maps to the DOTNET_ROOT fix, and the TRX-parsing script provides a verify-results feedback loop. This is a command-reference skill rather than a destructive batch workflow, so no validation cap applies. | 5 / 5 |
Progressive Disclosure | The single ~330-line SKILL.md is well sectioned, but there are no bundle reference files at all (references/, scripts/, assets/ are absent), so peripheral material — the test-attribute/category guide, the TRX XML-parsing script, VS-specific workflows (deferred only to a repo doc, docs\testing-in-vs.md, which is not part of the bundle), and the duplicated cheat sheet — is all inlined rather than split into one-level-deep references. That matches 'some structure, but content that should be separate is inline'. | 3 / 5 |
Total | 16 / 20 Passed |