CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

64

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/integration-tests/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 highly actionable, well-structured reference: real commands for every flag, explicit semantics for each filter mode, and a compilation prerequisite. Its main weakness is token efficiency — the Examples section largely repeats the inline option examples — and the absence of any post-run validation guidance keeps workflow clarity one notch below the top.

Suggestions

Remove the standalone '## Examples' section (or cut it to only combinations not already shown, such as combining --run with --grep), since most of its commands duplicate the inline examples in the Options section.

Consolidate the repeated --suite examples ('--suite git', "--suite 'api*'") into the single Options-section code block instead of showing them in both places.

Add a brief verification step after running tests (e.g., how to interpret exit codes or re-run a failing suite with --grep) to close the workflow-clarity validation gap.

DimensionReasoningScore

Conciseness

The "## Examples" section duplicates commands already shown in the Options section ("--run src/vs/workbench/services/search/test/browser/search.integrationTest.ts", "--grep \"TextSearchProvider\"", "--suite git", and "--suite 'api*'" each appear twice). There is no padding with concepts Claude already knows, but a whole redundant section means the body could be tightened by roughly a third, which is more than the minor trimming of the anchor-4 example.

3 / 5

Actionability

Every option is paired with a copy-paste-ready executable command (e.g. "./scripts/test-integration.sh --runGlob \"**/search/**/*.integrationTest.js\""), edge behavior is explicit ("Extension host tests are skipped since these filters are node.js-specific"), and the examples cover the common cases including combined flags ("--run ... --grep \"should search\"").

5 / 5

Workflow Clarity

Each invocation mode's behavior is unambiguously enumerated (no filters, "--run or --runGlob", "--grep alone", "--suite"), and a pre-flight checkpoint exists ("Ensure the `VS Code - Build` watch task is running or that compilation has completed"). It falls short of anchor 5 because there are no validation or failure-recovery steps after a run, and the body is too long for the simple-skill exception.

4 / 5

Progressive Disclosure

A self-contained, well-sectioned SKILL.md with no nested references and no bundle files to mis-navigate; the content is compact enough to belong inline. Minor organization gaps remain: the duplicated Examples section and the long inline suite list could be consolidated or split out.

4 / 5

Total

16

/

20

Passed

Description

78%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 with an explicit 'Use when...' trigger, concrete script and platform names, and a clear niche within the VS Code repo. It could reach the top anchor by enumerating more concrete actions or adding trigger variations, but as written it is specific, complete, and highly distinct.

DimensionReasoningScore

Specificity

Names concrete scripts and platforms ("scripts/test-integration.sh (macOS/Linux) and scripts/test-integration.bat (Windows)") plus concrete coverage areas ("supported arguments for filtering", "the difference between node.js integration tests and extension host tests"). It lists several specifics but describes coverage areas rather than comprehensively enumerating concrete actions, so it does not reach the anchor-5 example's breadth.

4 / 5

Completeness

Explicitly answers when ("Use when running integration tests in the VS Code repo") and what ("Covers ... their supported arguments for filtering, and the difference between node.js integration tests and extension host tests"). The when clause offers a single trigger phrase rather than the multiple concrete trigger variations ("or when the user mentions...") shown in the anchor-5 example.

4 / 5

Trigger Term Quality

Includes the natural phrase users would say ("running integration tests", "VS Code repo") plus exact script names ("test-integration.sh", "test-integration.bat") and category terms ("extension host tests", "node.js integration tests"). A few natural variations users might say (e.g. "e2e tests", "run the tests in the extension") are missing, so it falls just short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

Pinned to a specific repository ("the VS Code repo") with an explicit distinction "between node.js integration tests and extension host tests", giving it a clear niche with script-name triggers and minimal conflict risk against adjacent skills (e.g., unit-test skills).

5 / 5

Total

17

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 6 missing

Warning

Total

15

/

16

Passed

Repository

microsoft/vscode

Path

.github/skills/integration-tests/SKILL.md

Reviewed

Table of Contents

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.