integration-tests

Use when running integration tests in the VS Code repo. Covers scripts/test-integration.sh (macOS/Linux) and scripts/test-integration.bat (Windows), their supported arguments for filtering, and the difference between node.js integration tests and extension host tests.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable and unambiguous — exact commands, exhaustive filter semantics, and a clear unit-vs-integration distinction. Its main weakness is redundancy: the Examples section repeats the Options section's examples nearly line-for-line, costing tokens without adding coverage.

Suggestions

Remove the '## Examples' section or reduce it to only combinations not already shown under Options (e.g., just the 'Combine file and grep' case), eliminating the duplicated --run/--grep/--runGlob/--suite examples.

Move the catalog of suite names and per-option detail into a references/ file (e.g., suites.md), keeping SKILL.md as a lean overview with one example per flag.

Clarify the opaque sentence about 'deterministic Agent Host E2E entrypoints' — either state which tests it affects and why it matters, or drop it.

Dimension	Reasoning	Score
Conciseness	The body is dense and free of concept over-explanation, but the '## Examples' section duplicates the per-option examples from '## Options' almost verbatim (--run, --runGlob, --grep, and --suite examples all appear twice), which is a full redundant section rather than a minor trim.	3 / 5
Actionability	Every option is shown as a copy-paste-ready shell command with realistic arguments (source paths, glob patterns, grep strings), plus the full list of valid suite names ('api-folder', 'git', 'typescript', ...) — common cases are fully covered.	5 / 5
Workflow Clarity	A simple single-purpose skill where the action is unambiguous: invocation, behavior under every filter combination (no filters / --run / --grep alone / --suite), and a prerequisite checkpoint ('Ensure the VS Code - Build watch task is running') plus unit-vs-integration disambiguation are all explicit. Not a destructive or batch operation, so no validation cap applies.	5 / 5
Progressive Disclosure	Well-sectioned and self-contained with no nested references, but at ~118 lines content such as the suite-name catalog and per-option detail could be split into a reference file. Good structure with minor organization gaps rather than the fully optimal split of the 5 anchor.	4 / 5
	Total	17 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it explicitly pairs a concrete 'what' with a specific 'Use when' trigger, names exact scripts and platforms, and stakes out a distinct niche. Only minor gaps — a few natural trigger synonyms and capabilities (suites, compile prerequisite) are not surfaced.

Dimension	Reasoning	Score
Specificity	Names concrete coverage — exact script paths per platform ('scripts/test-integration.sh (macOS/Linux) and scripts/test-integration.bat (Windows)'), filtering arguments, and the node.js vs extension host test distinction. Not fully comprehensive (suite names, compile prerequisite unmentioned), so below the 5 anchor but above the 1-2-action level of 3.	4 / 5
Completeness	Explicitly answers both: 'Use when running integration tests in the VS Code repo' (when) and 'Covers scripts... arguments... difference between node.js integration tests and extension host tests' (what), with concrete trigger phrases. The 'when' is already explicit and specific, so not the 4 anchor.	5 / 5
Trigger Term Quality	'Use when running integration tests in the VS Code repo' supplies natural phrases users would say ('integration tests', 'VS Code'). Minor natural terms missing (e.g., 'extension tests', 'run the tests on Windows'), matching good-but-not-comprehensive keyword coverage.	4 / 5
Distinctiveness Conflict Risk	Scoped tightly to integration tests in the VS Code repo and explicitly distinguishes the two test categories, giving it a clear niche with minimal overlap against generic test-running skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 6 missing	Warning

	Total	15 / 16 Passed

Repository: posit-dev/positron
Path: .github/skills/integration-tests/SKILL.md
Commit: b0258bc

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.