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

89%

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

86%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.

A tightly written, fully actionable reference for running VS Code integration tests with executable commands and a clear flag-decision matrix. The main improvement opportunity is trimming command duplication between Options and Examples and adding a brief note on interpreting run results.

Suggestions

Trim or cross-reference the Examples section so commands already demonstrated under each option are not repeated verbatim, reclaiming token budget.

Add a short note after the Compilation requirement on how to interpret failures (e.g. checking the Mocha reporter output, where logs land) to round out the workflow.

Clarify Windows parity for --suite glob patterns, since the body notes shell glob support is macOS/Linux only but leaves Windows behavior unstated.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — no padding about what integration tests are — but the Examples section repeats several commands already shown under Options, which is mild redundancy that could be trimmed.	4 / 5
Actionability	Every option is paired with copy-paste-ready bash commands and the Examples section covers the common cases (run all, single file, grep, glob, single suite, multi-suite, combinations), making the guidance fully executable.	5 / 5
Workflow Clarity	The flag-combination matrix ('without filters', '--run/--runGlob', '--grep alone', '--suite') provides clear decision logic and the Compilation requirement is an explicit precondition, but there is no guidance on verifying or interpreting test outcomes after the run.	4 / 5
Progressive Disclosure	No bundle files exist and the self-contained ~120-line body is organized into clearly signaled sections (Scripts, Options, Examples, Compilation requirement, Distinction from unit tests), satisfying the simple-skill bar for well-organized single-file content.	5 / 5
	Total	18 / 20 Passed

Description

92%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 precise, well-triggered description that concretely enumerates the skill's scope and opens with an explicit 'Use when' clause. The only soft spot is trigger-term breadth, which favors technical identifiers over additional natural-language synonyms.

Dimension	Reasoning	Score
Specificity	The description names multiple concrete capabilities — the two platform-specific scripts (test-integration.sh, test-integration.bat), their filtering arguments, and the distinction between node.js integration tests and extension host tests — giving comprehensive coverage of the skill's scope.	5 / 5
Completeness	It explicitly answers both 'what' (covers the scripts, their filtering arguments, and the test-type distinction) and 'when' via the explicit 'Use when running integration tests in the VS Code repo' trigger clause.	5 / 5
Trigger Term Quality	Natural phrases like 'running integration tests' and 'VS Code repo' appear and would be said by users, but coverage leans on technical script identifiers rather than a fuller set of synonyms a user might verbalize.	4 / 5
Distinctiveness Conflict Risk	The niche is sharply defined — VS Code integration tests executed via named scripts — and it is clearly separable from unit-test tooling, leaving minimal overlap risk with other skills.	5 / 5
	Total	19 / 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: 75a1182

Reviewed: 3 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.