SKILLEMALL.ai
GitHub ↗ RU Sign in

BF rtvi-cv-customize-model

How to swap the DeepStream CV detection model in the VSS Alerts Blueprint verification (2d_cv) mode - covers ONNX export, custom bbox parsers, compose mount gotchas, nvinfer config, runtime TRT engine build, deployment, and a segmentation-capable model addendum handoff.

ClawHub Agent Skills author: NVIDIA 1 file body ≈ 4 344 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

How to swap the DeepStream CV detection model in the VSS Alerts Blueprint verification (2dcv) mode - covers ONNX export, custom bbox parsers, compose mount…

As a process F 51/100 · Will not run — References files that are not bundled: references/segmentation-model-contract.md, references/vss-source-layout.md, ../deepstream-dev/

ProcedureDockerPeople and hiringInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
84/100
safety, quality, tests
Safety 60%
90
Quality 40%
75
Run on models
none yet
Process rating
F
51/100
Will not run
References files that are not bundled: references/segmentation-model-contract.md, references/vss-source-layout.md, ../deepstream-dev/
Tools and files w 18
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Dangerous commands medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

How to improve

  1. The text references files that are not there: add them or drop the references.
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 · 2

✓ No critical or high findings

Medium and low: 2
  • medium Dangerous commands cmd-privilege SKILL.md:100
    Privilege escalation / world-writable permissions
    sudo chown -R $(id -u):$(id -g) "${VSS_DATA_DIR}/models/yolo"
  • medium Dangerous commands cmd-privilege SKILL.md:313
    Privilege escalation / world-writable permissions
    sudo chown -R $(id -u):$(id -g) "${VSS_DATA_DIR}/models/yolo"

Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: references/segmentation-model-contract.md
  • warning missing-ref reference to a missing file: references/vss-source-layout.md
  • warning missing-ref reference to a missing file: ../deepstream-dev/
  • warning missing-ref reference to a missing file: references/yolov11-onnx-export.md
  • warning missing-ref reference to a missing file: references/yolov11-parser.md
  • warning missing-ref reference to a missing file: references/ds-start-entrypoint.md
  • warning missing-ref reference to a missing file: references/common-gotchas.md
  • warning missing-ref reference to a missing file: references/nvinfer_config.md

Process rating: all ten parameters 51/100

Will not run. References files that are not bundled: references/segmentation-model-contract.md, references/vss-source-layout.md, ../deepstream-dev/
  • 0Tools and files. 8 referenced file(s) missing: references/segmentation-model-contract.md, references/vss-source-layout.md, ../deepstream-dev/
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 7 mutating operations with no state check
  • 60Result and completion. Output format stated, no completion criterion
  • 60Failures and branches. 2 branches
  • 70When it triggers. States when to use, but not when not to
  • 70Execution cost. Instruction body is 4344 tokens
  • 100Steps. 20 steps
  • 100Consistency. Name and required fields are in place
  • low 13 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)
  • +1No license
  • +2Single-language instructions
  • +3Description length 270: enough signal without eating the budget
  • +4Structure: 14 headings
  • +3Step-by-step instructions: 20 items
  • +3Output format is stated explicitly
  • +4Has examples (10 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.