BD 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.
This skill covers running integration tests in the VS Code repository through shell scripts on macOS/Linux and batch files on Windows. It promises to clarify filter arguments and the distinction between Node.js tests and extension host tests.
One file with 1541 tokens inside. Security checks found no critical issues (safety score 100), but quality landed at 75 and process score dropped to 37—a sign the instructions are incomplete. Broken reference links to missing files will make navigation through actual scripts harder.
Install if you regularly run integration tests in VS Code. Otherwise it's too narrow—won't help outside this specific repository.
Covers scripts/test-integration.sh (macOS/Linux) and scripts/test-integration.bat (Windows), their supported arguments for filtering, and the difference…
As a process D 37/100 · Unfinished process — References files that are not bundled: scripts/test.sh, scripts/test-integration.sh
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: scripts/test.sh - warning
missing-refreference to a missing file: scripts/test-integration.sh
Process rating: all ten parameters 37/100
- 0Tools and files. 2 referenced file(s) missing: scripts/test.sh, scripts/test-integration.sh
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 50When it triggers. No condition that starts the skill
- 85Steps. 6 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1541 tokens
- 100Running it twice. No mutating operations
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 268: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 6 items
- +4Has examples (7 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.