BD smoke-tests
Use when running VS Code smoke tests or working on smoke-test CI steps. Covers npm run smoketest / smoketest-no-compile, grep filtering tests, and a temporary repeat-loop technique for tracking down flaky smoke tests in CI.
A skill for running VS Code smoke tests—instructions for CI setup and debugging flaky tests. Promises to cover npm run smoketest commands, grep filtering, and a repeat-loop technique to catch unstable tests in CI.
The file contains 2170 tokens of text, but broken_references flag indicates missing links. Code quality scores 75, process score 40. No critical issues found, but the process clearly needs work. Not tested on models, no sandbox run. Supports many platforms from Claude to OpenClaw.
Install if you're already working with VS Code CI and need a quick reference for smoke tests. If you're looking for a ready-made automation solution—you'll be disappointed.
Covers npm run smoketest / smoketest-no-compile, grep filtering tests, and a temporary repeat-loop technique for tracking down flaky smoke tests in CI.
As a process D 40/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 40/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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 5 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 20 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2170 tokens
- 100Progress reporting. Reports progress
- high The skill tells the model to perform an irreversible action with no human approval
- low The response is described with custom markup (14 tags): a typed call is more reliable
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 223: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 20 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.