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

84%

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

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.

Highly actionable reference content with copy-paste-ready commands, accurate flag semantics, and a stated compilation precondition. The main weakness is redundancy — the Examples section repeats most of the commands already demonstrated in Options — which costs tokens without adding guidance.

Suggestions

Cut the Examples section down to only combinations not already shown inline (e.g., combining --run with --grep, and multi-suite globs), removing the ~6 entries that duplicate the Options section verbatim.

Consolidate the duplicated script invocations so each canonical usage appears exactly once, letting the Options sections serve as the single source of examples.

If the skill grows, move the suite-name catalog (the 15 suite names under --suite) into a references file and link to it, keeping SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

The body is mostly efficient — it documents only repo-specific facts (scripts, flags, suite names, compilation requirement) with no explanation of concepts Claude already knows. However, the "Examples" section duplicates roughly six commands already shown verbatim in the Options section (e.g. "--run src/vs/workbench/services/search/test/browser/search.integrationTest.ts", "--grep \"TextSearchProvider\"", "--suite git", "--suite 'api*'"), which is more than minor trimming.

3 / 5

Actionability

Every command is fully executable and copy-paste ready: exact script invocations, real source paths, glob patterns ("**/search/**/*.integrationTest.js"), the full list of suite names, and flag combinations covering the common cases. No gaps between the guidance and what can actually be run.

5 / 5

Workflow Clarity

The decision logic is clearly sequenced — behavior "without filters", "with --run or --runGlob", "with --grep alone", "with --suite" — and the compilation precondition ("Ensure the VS Code - Build watch task is running or that compilation has completed before running tests") is an explicit checkpoint. It falls short of 5 because there is no explicit sequence framing or error-recovery guidance (e.g., what to check when tests fail to launch), though no destructive/batch validation cap applies.

4 / 5

Progressive Disclosure

The body is well organized into clearly signaled sections (Scripts, Options, Examples, Compilation requirement, Distinction from unit tests) with no bundle files and no nested references, so navigation is easy. It is not a 5 because at ~118 lines it exceeds the self-contained simple-skill threshold and keeps everything inline — the suite catalog and duplicated examples could live in a reference file to slim the SKILL.md.

4 / 5

Total

16

/

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 with an explicit and concrete "Use when…" trigger, named scripts and platforms, and clear differentiation of test categories. It is specific and highly distinct; only minor gains available from more action-oriented phrasing or a few extra synonyms.

DimensionReasoningScore

Specificity

The description names concrete artifacts — "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" — which goes well beyond naming the domain with 1-2 actions. It falls short of a 5 because the catalog-style "Covers…" phrasing describes what the skill includes rather than enumerating multiple discrete actions.

4 / 5

Completeness

It explicitly answers both parts: the trigger "Use when running integration tests in the VS Code repo" is concrete and explicit, and the what is concretely described (the two scripts, their filtering arguments, and the test-type distinction). A 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

"Use when running integration tests in the VS Code repo" is exactly the natural phrase a user would say, and the description includes script names and synonyms like "node.js integration tests" and "extension host tests". It is not a 5 because a few natural variations (e.g., "integration testing", "run the tests") are absent.

4 / 5

Distinctiveness Conflict Risk

The description is scoped to a clear niche — integration test scripts in the VS Code repo — and even distinguishes "node.js integration tests" from "extension host tests", so it would not fire for unit-test or unrelated skills. Minimal conflict risk.

5 / 5

Total

18

/

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

posit-dev/positron

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.