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.

Quality

83%

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

SKILL.md
Quality
Evals
Security

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.

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.

DimensionReasoningScore

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

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 names, and clear domain scoping that keeps conflict risk low. Its main limitation is that the 'what' is expressed as coverage scope rather than enumerated concrete capabilities, which keeps specificity and completeness just below top marks.

Suggestions

Replace the 'Covers...' scope phrasing with enumerated concrete actions, e.g. 'Run integration tests via scripts/test-integration.sh or .bat, filter by file, glob, grep pattern, or extension host suite'.

Add a few natural trigger synonyms such as 'integration test suites' or 'extension host tests failing' to broaden the natural-phrases users might say.

DimensionReasoningScore

Specificity

Names concrete artifacts — 'scripts/test-integration.sh (macOS/Linux) and scripts/test-integration.bat (Windows)', 'supported arguments for filtering', and the 'difference between node.js integration tests and extension host tests' — but capabilities are framed as scope ('Covers...') rather than an enumerated action list, matching the 'several specific actions; minor gaps' anchor rather than comprehensive coverage.

4 / 5

Completeness

Both parts are present: an explicit 'Use when running integration tests in the VS Code repo' trigger and a clear what (the two scripts, their arguments, the test-type distinction). The 'when' is concrete, but the 'what' is a coverage description rather than explicit capability statements, matching anchor 4 ('when' or 'what' could be more explicit) better than anchor 5.

4 / 5

Trigger Term Quality

'running integration tests', 'VS Code repo', 'node.js integration tests', and 'extension host tests' are phrases users would naturally say, giving good keyword coverage; common variations like 'integration test suites' or 'extension tests' are missing, so it falls just short of the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

Scoped to a single repo with named scripts and an explicit test-category distinction, it occupies a clear niche ('integration tests in the VS Code repo') with minimal risk of triggering for the wrong skill — matching the 'clear niche with distinct triggers' anchor.

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: 9 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.