BF vscode-node
Operate on code through a VS Code/Cursor IDE connected as an OpenClaw Node. Provides 40+ commands for file operations, language intelligence, git, testing, debugging, and Cursor Agent CLI integration. Use when you need to read/write/edit code, navigate definitions/references, run tests, debug, or delegate coding tasks to Cursor Agent.
As a process F 47/100 · Will not run — References files that are not bundled: references/commands/file.md, references/commands/language.md, references/commands/editor.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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/commands/file.md - warning
missing-refreference to a missing file: references/commands/language.md - warning
missing-refreference to a missing file: references/commands/editor.md - warning
missing-refreference to a missing file: references/commands/git.md - warning
missing-refreference to a missing file: references/commands/test-debug.md - warning
missing-refreference to a missing file: references/commands/terminal.md - warning
missing-refreference to a missing file: references/commands/agent.md - warning
missing-refreference to a missing file: references/workflows.md
Process rating: all ten parameters 47/100
- 0Tools and files. 8 referenced file(s) missing: references/commands/file.md, references/commands/language.md, references/commands/editor.md
- 0Result and completion. Does not say what the result is
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 3 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 13 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1189 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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 336: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 13 items
- +4Has examples (5 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.