CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

68

Quality

82%

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

65%

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-organized integration-test runbook with concrete commands and examples, weakened mainly by redundancy across the intro, Options, and Examples sections and the absence of an explicit result-validation step for a batch test operation.

Suggestions

Consolidate the per-filter behavior descriptions so each flag's semantics appear once (in Options) and the intro only summarizes, removing repeated commands from Examples.

Add an explicit verification step after running tests (e.g. check the script's exit code / read the Mocha summary) to close the feedback loop for this batch operation.

Consider moving the long Options reference and/or Examples into a references/ file linked from the body, to apply progressive disclosure and slim the main SKILL.md.

DimensionReasoningScore

Conciseness

The content is mostly efficient and free of basic-concept padding, but the filter behaviors (--run/--runGlob/--grep/--suite) are described in the intro paragraphs, restated in the Options section, and several commands reappear in Examples — redundancy that could be tightened.

2 / 3

Actionability

Fully executable commands with real file paths (e.g. src/vs/workbench/services/search/test/browser/search.integrationTest.ts), concrete suite names, and copy-paste-ready bash examples — no pseudocode.

3 / 3

Workflow Clarity

Filter combinations are clearly sequenced and the compilation prerequisite is stated, but running a full integration suite is a batch operation with no explicit validation/verification checkpoint (e.g. inspecting exit code or report), which caps this dimension at 2 per the rubric guideline.

2 / 3

Progressive Disclosure

The skill is well-organized into clear sections but is a monolithic single file over 50 lines with no bundle files and no one-level-deep references; the long Options reference and Examples could be split out, fitting the 'content that should be separate is inline' anchor.

2 / 3

Total

9

/

12

Passed

Description

100%

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, third-person description with an explicit 'Use when' trigger, concrete script and platform details, and clear scoping that distinguishes it from generic test-running skills. All four dimensions hit the top anchor.

DimensionReasoningScore

Specificity

Names concrete scripts (test-integration.sh, test-integration.bat), platforms, supported filtering arguments, and the node.js vs extension host distinction — multiple specific concrete items rather than vague language.

3 / 3

Completeness

Explicitly answers both what (covers the scripts, their filtering arguments, and the test-category distinction) and when ('Use when running integration tests in the VS Code repo').

3 / 3

Trigger Term Quality

'Use when running integration tests in the VS Code repo' provides natural terms ('integration tests', 'VS Code repo') a user would actually say when needing this skill.

3 / 3

Distinctiveness Conflict Risk

Scoped to integration tests in the VS Code repo with specific named scripts, giving it a clear niche unlikely to trigger for unrelated skills.

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 6 missing

Warning

Total

15

/

16

Passed

Repository
posit-dev/positron
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.