BD vx-best-practices
Best practices for using vx effectively. Use when following recommended patterns for tool management, project setup, and team workflows with vx.
Best practices for using vx effectively.
As a process D 43/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
For the model run — optional
- 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
- note
edit-residuethe text marks something as outdated (lines 561): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 43/100
- 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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 6 mutating operations with no state check
- 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
- 100Steps. 25 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3468 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 16 top-level sections: this looks like several domains in one skill
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
- -4Absolute local paths (C:\Users, /home/…): not portable
- +1No license
- +2Single-language instructions
- +3Description length 144: enough signal without eating the budget
- +4Structure: 57 headings
- +3Step-by-step instructions: 25 items
- +4Has examples (37 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.
External checks
ClawHub: clean
This is a Markdown-only vx best-practices skill with coherent instructions; the main caution is unguarded migration examples that delete old nvm and pyenv directories.
LLM: benign (high) · VirusTotal: · 10 Oct 2026