BF rtvi-vlm-customize-model
How to swap the VLM in the VSS Alerts Blueprint — covers RTVI-VLM microservice deployment methods, all three VLM consumers (rtvi-vlm, vlm-as-verifier, vss-agent), and health checks.
How to swap the VLM in the VSS Alerts Blueprint — covers RTVI-VLM microservice deployment methods, all three VLM consumers (rtvi-vlm, vlm-as-verifier…
As a process F 39/100 · Will not run — References files that are not bundled: references/vss-source-layout.md, references/port-and-url-wiring.md, references/health-checks.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: references/vss-source-layout.md - warning
missing-refreference to a missing file: references/port-and-url-wiring.md - warning
missing-refreference to a missing file: references/health-checks.md
Process rating: all ten parameters 39/100
- 0Tools and files. 3 referenced file(s) missing: references/vss-source-layout.md, references/port-and-url-wiring.md, references/health-checks.md
- 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. 15 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 70Execution cost. Instruction body is 4875 tokens
- 100Steps. 20 steps
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- low 11 top-level sections: this looks like several domains in one skill
- high The skill tells the model to perform an irreversible action with no human approval
- 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
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +3Description length 181: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 20 items
- +4Has examples (12 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.