BF deepstream-generate-pipeline
Build DeepStream GStreamer pipelines interactively. Use when the user asks about pipelines for video/image inference, detection, tracking, or streaming — including natural phrases like 'pipeline to infer on image', 'run inference on video', 'detect objects in stream', 'save inference output', 'deepstream pipeline', 'gst-launch pipeline', 'process video with detection', 'build a pipeline', or any request involving GStreamer/DeepStream elements (nvinfer, nvstreammux, nvtracker, etc.).
Build DeepStream GStreamer pipelines interactively.
As a process F 61/100 · Will not run — References files that are not bundled: references/assembly-rules.md, scripts/generate_pipeline.py, scripts/validate_pipeline.py
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/assembly-rules.md - warning
missing-refreference to a missing file: scripts/generate_pipeline.py - warning
missing-refreference to a missing file: scripts/validate_pipeline.py - warning
missing-refreference to a missing file: scripts/lint_data.py - warning
missing-refreference to a missing file: references/requirement-extraction.md - warning
missing-refreference to a missing file: references/output-format.md - warning
missing-refreference to a missing file: scripts/demo.sh - warning
missing-refreference to a missing file: references/security-and-limitations.md - note
frontmatter-keyunknown frontmatter key "owner" - note
frontmatter-keyunknown frontmatter key "service" - note
frontmatter-keyunknown frontmatter key "reviewed"
Process rating: all ten parameters 61/100
- 0Tools and files. 8 referenced file(s) missing: references/assembly-rules.md, scripts/generate_pipeline.py, scripts/validate_pipeline.py
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 4005 tokens
- 85Steps. 23 steps, 3 vague phrases
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (3 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)
- +2Single-language instructions
- +3Description length 487: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 23 items
- +3Output format is stated explicitly
- +4Has examples (12 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.