CF chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
The skill runs VS Code chat performance benchmarks and memory leak checks. Promises to catch rendering regressions and pipeline issues.
Broken references to missing files found—the skill is incomplete. Quality score 72 out of 100, process coverage 34 percent. No critical findings, but the model never ran it. Sandbox didn't execute. No scripts, just one config file.
Don't install it. Half the docs are broken, and nobody tested whether it actually works. For memory leak diagnostics, you need something more solid.
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version.
As a process F 34/100 · No process to follow — References files that are not bundled: scripts/chat-simulation/test-chat-perf-regression.js, scripts/chat-simulation/common/perf-scenarios.js, scripts/chat-simulation/test-chat-mem-leaks.js
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/chat-simulation/test-chat-perf-regression.js - warning
missing-refreference to a missing file: scripts/chat-simulation/common/perf-scenarios.js - warning
missing-refreference to a missing file: scripts/chat-simulation/test-chat-mem-leaks.js
Process rating: all ten parameters 34/100
- 0Tools and files. 3 referenced file(s) missing: scripts/chat-simulation/test-chat-perf-regression.js, scripts/chat-simulation/common/perf-scenarios.js, scripts/chat-simulation/test-chat-mem-leaks.js
- 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
- 30Running it twice. 10 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 70Execution cost. Instruction body is 4759 tokens
- 85Steps. 45 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- low The response is described with custom markup (8 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 266: enough signal without eating the budget
- +4Structure: 28 headings
- +3Step-by-step instructions: 45 items
- +4Has examples (9 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.