Content
81%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, well-structured reference: every option comes with executable commands, explicit filter semantics, and documented constraints, and the workflow preconditions are unambiguous. The main weakness is token efficiency — the Examples section duplicates commands already shown and the CI job-name detail runs long.
Suggestions
Trim the Examples section to only combinations not already demonstrated under Options (keep the --run + --grep combination and drop the verbatim repeats).
Condense the CI/ADO paragraph to the essential fact — Agent Host E2E suites are separate and run via ./scripts/test-agent-host-e2e.sh — and leave job/shard names to the referenced README.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient — commands, suite lists, and filter semantics are all load-bearing — but the Examples section repeats commands already shown under Options (e.g. the search --run file and --suite 'api*' appear twice) and the CI paragraph enumerates GitHub/ADO job names in more detail than needed to run tests locally, matching the 'mostly efficient but could be tightened' anchor. | 3 / 5 |
Actionability | Every section gives copy-paste-ready, executable commands ('./scripts/test-integration.sh --run src/vs/workbench/services/search/test/node/search.integrationTest.ts', 'INTEGRATION_TEST_PARALLEL=2 ./scripts/test-integration.sh --only-extension-host-tests') and the examples cover the common cases — single file, grep, suite globs, comma-separated suites — matching the fully-executable anchor. | 5 / 5 |
Workflow Clarity | This is a single-action skill (run the right integration test command) and the action is unambiguous: a stated compilation precondition ('Ensure the VS Code - Build watch task is running'), explicit decision rules for each filter combination ('When run with --suite... Node.js integration tests are skipped'), and documented invalid combinations. It is not a destructive or batch operation, so the validation cap does not apply. | 5 / 5 |
Progressive Disclosure | Good structure with clear headers, a logical Options-to-Examples-to-caveats flow, and a clearly signaled pointer to external material ('See src/vs/platform/agentHost/test/node/e2e/README.md'). No bundle files exist, everything is inline, and at ~150 lines the single-file layout is reasonable, but there is no overview-to-detail split — matching anchor 4 rather than the well-signaled multi-file structure of anchor 5. | 4 / 5 |
Total | 17 / 20 Passed |