CD ci-artifact-testing
Use when validating an upstream pull request or dependency fix against VS Code tests using GitHub Actions CI build artifacts instead of building locally. Covers finding compatible binaries, verifying PR and merge-commit provenance, selecting a candidate runtime or build, comparing unchanged regression tests, and restoring the baseline.
This skill promises to streamline VS Code PR validation using CI build artifacts instead of local rebuilds. The folder contains a single file with instructions for finding compatible binaries, verifying commit provenance, and comparing test results.
Quality scores 72 out of 100, but the process score drops to 38—the documentation is clearly incomplete. No critical issues found, yet broken references and missing files signal unfinished work. Never tested on models, never run in sandbox. For VS Code contributors willing to hunt through gaps in the docs, it might work as a reference. Everyone else should just build locally.
Covers finding compatible binaries, verifying PR and merge-commit provenance, selecting a candidate runtime or build, comparing unchanged regression tests…
As a process D 38/100 · Unfinished process — References files that are not bundled: ../integration-tests/SKILL.md, ../unit-tests/SKILL.md, ../smoke-tests/SKILL.md
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: ../integration-tests/SKILL.md - warning
missing-refreference to a missing file: ../unit-tests/SKILL.md - warning
missing-refreference to a missing file: ../smoke-tests/SKILL.md - warning
missing-refreference to a missing file: ../azure-pipelines/SKILL.md - warning
missing-refreference to a missing file: ../agent-host-e2e-tests/SKILL.md - note
edit-residuethe text marks something as outdated (lines 89): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 38/100
- 0Tools and files. 5 referenced file(s) missing: ../integration-tests/SKILL.md, ../unit-tests/SKILL.md, ../smoke-tests/SKILL.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 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. 21 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1928 tokens
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 337: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 21 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.