Official agent skill

Deepstream Dev

by NVIDIA in NVIDIA/skills

NVIDIA DeepStream SDK development with Python pyservicemaker API.

OfficialApache-2.0Auto-check passedBackend & APIs

Install Deepstream Dev

skills CLI
$ npx skills add NVIDIA/skills --skill deepstream-dev -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install NVIDIA/skills deepstream-dev --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/deepstream-dev .claude/skills/deepstream-dev && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
deepstream-dev
GitHub stars
3.5k
Token cost
~3.3k tokens
SKILL.md length
1,328 words
Files
21 (incl. references)
Skills in repo
380
Repo updated
First seen
Licence
Apache-2.0

At a glance

NVIDIA DeepStream SDK development with Python pyservicemaker API.

  • Works in 12 steps: Only Add Requested Components: Do NOT… → Default to nvurisrcbin for Sources: When… → Metadata Iteration: Use .frame_items and… → …
  • Building video analytics pipelines
  • SKILL.md covers SDK and Architecture Quick…, Critical Rules, Key Paths and Reference Documents, plus 1 more section
  • Calls pip

What it does

Deepstream Dev is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. NVIDIA DeepStream SDK development with Python pyservicemaker API. Use when building video analytics pipelines, GStreamer-based video processing, TensorRT inference integration, object detection/tracking, or Kafka/message broker integration.

Its SKILL.md is about 3.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 22 other files, including reference files (for example `BENCHMARK.md`, `evals/evals.json` and `references/best_practices.md`).

It sits in Backend & APIs, covering Event-driven systems, LLM inference and serving and Computer vision. It works with NVIDIA AI Platform, Apache Kafka, CUDA and Python. The repository describes itself as: Agent Skills for NVIDIA products — install into Claude Code, Codex, and other coding agents to run Physical AI, robotics, simulation, CUDA, and RAG workflows end to end. The licence is Apache-2.0.

When your agent uses it

  • Building video analytics pipelines
  • GStreamer-based video processing
  • TensorRT inference integration
  • Object detection/tracking

Example prompts

  • “/deepstream-dev”

Requirements

  • Python 3
  • Docker

Workflow steps

12 steps, taken from the first numbered list in SKILL.md.

  1. Only Add Requested Components: Do NOT add pipeline elements the user did not ask for.
  2. Default to nvurisrcbin for Sources: When the user says "camera", "stream", "video", or provides a file path
  3. Metadata Iteration: Use .frame_items and .object_items (returns iterators, NOT lists)
  4. Request Pad Syntax: Use "sink_%u" template, NEVER literal pad names
  5. Platform Detection for Sinks
  6. Buffer Cloning: Always clone buffers for async processing
  7. Queue Types
  8. nvinfer Config Format
  9. nvmsgbroker is a SINK: Cannot have downstream elements - use tee to split pipeline
  10. ALL Sinks Need async=0 for Tee Splits or Dynamic Sources: CRITICAL for state transitions
  11. Built-in Probe Attachment: measure_fps_probe can only be attached to processing elements (e.g., nvinfer, nvosdbin), NOT to sink elements…
  12. Dynamic ONNX Models Require infer-dims: When the ONNX model has dynamic input shapes (e.g., exported with dynamic=True in Ultralytics…

What it can do on your machine

Read from SKILL.md and the folder at commit 0e0d506. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • pip

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use pip, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Deepstream Dev loads about 3.3k tokens when it runs, and up to ~136k if it reads all its reference files. Until then it costs about 64 tokens; SKILL.md has 1,328 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~64
When it runs · the whole SKILL.md, loaded when a task matches
~3.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~136k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from NVIDIA/skills at commit 0e0d506, republished under its Apache-2.0 licence (© NVIDIA). 1,328 words, ~3,328 tokens.

Download SKILL.mdSave it as .claude/skills/deepstream-dev/SKILL.md (or your agent's skills folder). This skill also uses 20 other files; get the full folder from GitHub.
name
deepstream-dev
description
NVIDIA DeepStream SDK development with Python pyservicemaker API. Use when building video analytics pipelines, GStreamer-based video processing, TensorRT inference integration, object detection/tracking, or Kafka/message broker integration.
owner
NVIDIA CORPORATION
metadata.author
NVIDIA CORPORATION <info@nvidia.com>
service
deepstream
version
1.1.1
reviewed
2026-04-24
license
CC-BY-4.0 AND Apache-2.0

DeepStream Development Skill

This skill requires access to all of the reference documents listed in the references/ directory below. Ensure they are available before executing the workflow.

When this skill is active, ALWAYS read the relevant reference documents before generating code. Do NOT rely on memory - the reference documents contain critical details about exact property names, correct API usage, and common pitfalls.

SDK and Architecture Quick Reference

DeepStream SDK Version Requirements
  • GStreamer: 1.24.2
  • NVIDIA Driver: 590+
  • CUDA: 13.1
  • TensorRT: 10.14.1.48
  • Platforms: Ubuntu 24.04 (x86_64 and ARM64/Jetson)
Typical Pipeline Flow
text
Source → Stream Muxer → Inference → [Tracker] → OSD → Renderer

Components in [brackets] are optional -- only add them when the user explicitly requests them.

StageRoleKey Element(s)Required?
SourceInput from files, RTSP, camerasnvurisrcbin (preferred), nvmultiurisrcbin, filesrcYes
Stream MuxerBatches streams for inferencenvstreammuxYes
InferenceTensorRT model executionnvinfer, nvinferserverYes
TrackerMulti-object tracking across framesnvtrackerOnly if requested
OSDDraws bounding boxes, labels, overlaysnvosdbinYes (for visualization)
RendererDisplay or save outputnveglglessink, nv3dsink, filesinkYes
Memory Model

DeepStream uses NVIDIA Video Memory Manager (NVMM) for zero-copy GPU buffer transfers. Caps strings use memory:NVMM to indicate GPU memory (e.g., video/x-raw(memory:NVMM), format=NV12).

Critical Rules

  1. Only Add Requested Components: Do NOT add pipeline elements the user did not ask for.

    • Tracker (nvtracker): Only add when the user explicitly requests tracking or object IDs across frames
    • Secondary GIEs: Only add when the user requests classification or attribute extraction
    • Analytics (nvdsanalytics): Only add when the user requests line crossing, ROI counting, etc.
    • Message broker (nvmsgbroker/nvmsgconv): Only add when the user requests Kafka/cloud messaging
    • When in doubt, build the minimal working pipeline and let the user ask for additions
  2. Default to nvurisrcbin for Sources: When the user says "camera", "stream", "video", or provides a file path:

    • Always use nvurisrcbin -- it handles RTSP, HTTP, and local files (file://) transparently
    • Only use filesrc + qtdemux + parser when the user explicitly needs raw file source control
    • For RTSP/live sources, also set live-source=1 on nvstreammux and sync=0 on the sink
    • Convert local paths to URI: "file://" + os.path.abspath(path)
  3. Metadata Iteration: Use .frame_items and .object_items (returns iterators, NOT lists)

    • NEVER use len() on these - iterate to count
    • Iterator can only be consumed once
  4. Request Pad Syntax: Use "sink_%u" template, NEVER literal pad names

    python
    pipeline.link(("decoder", "mux"), ("", "sink_%u"))  # CORRECT
    # pipeline.link(("decoder", "mux"), ("", "sink_0"))  # WRONG - will fail
  5. Platform Detection for Sinks:

    python
    import platform
    sink_type = "nv3dsink" if platform.processor() == "aarch64" else "nveglglessink"
    • For WSL2 Ubuntu 24 Docker, this default selection must be overridden.
    • WSL2 + Ubuntu 24 Docker: If /proc/version contains microsoft or wsl and /etc/os-release has VERSION_ID="24.04", the generated app must never create a display branch or display sink (nveglglessink, nv3dsink, etc.), even if the prompt asks for display. Do not rely on a --no-display flag for this case. Generate encoded MP4 output only (nvv4l2h264enc -> h264parse -> mp4mux/qtmux -> filesink) and make the default run path write the annotated video file. In the generated README.md, explicitly explain that WSL2 Ubuntu 24 Docker is MP4-output-only because display sinks are disabled by a known issue. If the user explicitly requested display, add an inline code comment and README note explaining: Display requested but disabled due to WSL2 Ubuntu 24 Docker limitation — MP4 output generated instead.
    • Non-WSL targets: Do not add WSL-specific behavior or WSL limitation text to generated apps or READMEs. Use the normal platform display sink selection above.
  6. Buffer Cloning: Always clone buffers for async processing

    python
    tensor = buffer.extract(0).clone()  # CRITICAL
  7. Queue Types:

    • queue.Queue → Use with threading.Thread
    • multiprocessing.Queue → Use with multiprocessing.Process
    • Using wrong type causes silent data loss!
  8. nvinfer Config Format:

    • YAML: Use property: section (NOT model:), key: value with space after colon
    • INI: Use [property] section, key=value with equals sign
    • Section MUST be named property
  9. nvmsgbroker is a SINK: Cannot have downstream elements - use tee to split pipeline

  10. ALL Sinks Need async=0 for Tee Splits or Dynamic Sources: CRITICAL for state transitions

    python
    # When using tee splits OR dynamic sources, ALL sinks MUST have async=0
    pipeline.add("nveglglessink", "sink", {
        "sync": 0, "qos": 0,
        "async": 0  # CRITICAL - prevents state transition deadlock
    })

    Symptom if missing: Pipeline stays in PAUSED state, no video displays.

  11. Built-in Probe Attachment: measure_fps_probe can only be attached to processing elements (e.g., nvinfer, nvosdbin), NOT to sink elements. Attaching to a sink raises RuntimeError: Probe failure.

  12. Dynamic ONNX Models Require infer-dims: When the ONNX model has dynamic input shapes (e.g., exported with dynamic=True in Ultralytics YOLO, or with dynamic batch/height/width axes), you MUST add infer-dims=C;H;W to the nvinfer config. Without it, TensorRT sees -1 for dynamic dimensions and fails with setDimensions: Error Code 3. Common values:

    • YOLO models (640 input): infer-dims=3;640;640
    • Models with 416 input: infer-dims=3;416;416
    • Models with 1280 input: infer-dims=3;1280;1280
  13. Ultralytics YOLO Output Format Depends on Model Generation — newer models (v10+/v26+) output post-NMS results; older models (v8/v11) output raw pre-NMS tensors. The custom parser and cluster-mode must match the actual output:

Model generationOutput tensor shapeFieldscluster-mode
v8 / v11[batch, 84, 8400][features(4+80), anchors] — raw cx/cy/w/h + class scores, no NMS2 (NMS)
v10 / v26+[batch, 300, 6][max_det, (x1,y1,x2,y2,conf,cls)] — already post-NMS, pixel coords4 (none)
Show full SKILL.md (520 more words)Show less

How to identify at runtime: log inferDims.d[0] and inferDims.d[1] inside the custom parser.

  • d={84, 8400} → pre-NMS (v8/v11 style)
  • d={300, 6} → post-NMS (v10/v26+ style)

Symptom of mismatch: If cluster-mode: 2 is used with a post-NMS [N, 6] output, bounding boxes appear shifted by 45° or 135° from the actual objects (DeepStream's NMS incorrectly re-processes already-final coordinates). If you see tilted or rotated boxes, also check the OBB / rotation_angle note in references/nvinfer_config.md: for non-OBB models, value-initialize NvDsInferObjectDetectionInfo with obj{} and keep rotation_angle = 0; plain NvDsInferObjectDetectionInfo obj; leaves fields uninitialized.

  1. Virtual Environment Must Include pyservicemaker: pyservicemaker is installed system-wide but is NOT accessible from a standard Python virtual environment. When a task requires a venv (e.g., for model download/conversion pip dependencies), always install pyservicemaker and pyyaml inside the venv; do not rewrite pyservicemaker pipeline code into non-pyservicemaker code to work around a missing import. The venv setup in generated code and README must always include:
    bash
    python3 -m venv venv
    source venv/bin/activate
    pip install /opt/nvidia/deepstream/deepstream/service-maker/python/pyservicemaker*.whl pyyaml
    pip install -r requirements.txt  # other dependencies
    Symptom if missing: ModuleNotFoundError: No module named 'pyservicemaker' when running the app inside the venv.

Key Paths

  • Models: /opt/nvidia/deepstream/deepstream/samples/models/
  • Primary Detector: /opt/nvidia/deepstream/deepstream/samples/models/Primary_Detector/resnet18_trafficcamnet_pruned.onnx
  • Tracker lib: /opt/nvidia/deepstream/deepstream/lib/libnvds_nvmultiobjecttracker.so
  • Kafka lib: /opt/nvidia/deepstream/deepstream/lib/libnvds_kafka_proto.so
  • Sample configs: /opt/nvidia/deepstream/deepstream/samples/configs/deepstream-app/

Reference Documents

IMPORTANT: Always read these documents for complete details. Do NOT generate code from memory.

DocumentUse When
references/gstreamer_plugins.mdLooking up plugin properties, ALL properties listed
references/service_maker_api.mdUsing Pipeline/Flow API, metadata access, probes, EventMessageUserMetadata
references/use_cases_pipelines.mdBuilding pipelines: simple playback, multi-inference, cascaded GIE
references/streaming_sources.mdIngesting local files, HTTP MP4, HLS, MPEG-DASH, or RTSP sources with nvurisrcbin
references/kafka_messaging.mdKafka/message broker setup, nvmsgconv/nvmsgbroker config, msg2p-newapi
references/best_practices.mdDesign patterns, common pitfalls, anti-patterns
references/buffer_apis.mdBufferProvider/Feeder (injection), BufferRetriever/Receiver (extraction)
references/media_extractor_advanced.mdMediaExtractor, MediaChunk, FrameSampler
references/utilities_config.mdPerfMonitor, EngineFileMonitor, SourceConfig, SensorInfo, SmartRecordConfig
references/nvinfer_config.mdnvinfer config file format, ALL parameters
references/tracker_config.mdnvtracker config, NvDCF/IOU/DeepSORT/NvSORT
references/troubleshooting.mdError messages and solutions
references/rest_api_dynamic.mdREST API, dynamic source add/remove, nvmultiurisrcbin
references/metamux_config.mdnvdsmetamux config, parallel multi-model inference, metadata merging, source ID filtering
references/docker_containers.mdDocker images, Dockerfile examples, pyservicemaker install, container run commands
references/nvds_msgapi_adapter.mdBuilding custom protocol adapters: nvds_msgapi

Quick Error Reference

ErrorSolution
iterator has no len()Iterate to count, don't use len()
pad template not foundUse "sink_%u" not "sink_0"
Queue data lossUse multiprocessing.Queue with Process
Config parse failedUse property: not model: in YAML
is-classifier deprecation warningUse network-type: 1 instead of is-classifier: 1 for classifiers; omit both for detectors
min-boxes unknown key warningUse minBoxes (camelCase) in class-attrs-* sections, not min-boxes
Secondary GIE inactiveSet process-mode: 2, check operate-on-gie-id
Tee/dynamic source stuck PAUSEDSet async: 0 on ALL sink elements
WSL2 Ubuntu 24 display sink requestedDo not use display sinks due to a known bug; write MP4 with filesink and document the WSL limitation in README
RTSP no data/reconnectingTest URL with ffplay, check credentials
RuntimeError: Probe failuremeasure_fps_probe cannot attach to sink elements; use nvinfer or nvosdbin instead
setDimensions negative dims / engine build failedAdd infer-dims=C;H;W for dynamic ONNX models (e.g., infer-dims=3;640;640)
No module named 'pyservicemaker' in venvpip install /opt/nvidia/deepstream/deepstream/service-maker/python/pyservicemaker*.whl pyyaml inside the venv
AttributeError: object has no attribute 'obj_label'Use obj_meta.label not obj_meta.obj_label in pyservicemaker (C API name differs from Python binding)
<!-- Signing refresh marker. -->

© NVIDIA, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 20 other files (references) in skills/deepstream-dev of NVIDIA/skills.

  • SKILL.md
  • BENCHMARK.md
  • evals/evals.json
  • references/best_practices.md
  • references/buffer_apis.md
  • references/docker_containers.md
  • references/gstreamer_plugins.md
  • references/kafka_messaging.md
  • references/media_extractor_advanced.md
  • references/metamux_config.md
  • references/nvds_msgapi_adapter.md
  • references/nvinfer_config.md
  • references/rest_api_dynamic.md
  • references/service_maker_api.md
  • references/streaming_sources.md
  • references/tracker_config.md
  • references/troubleshooting.md
  • references/use_cases_pipelines.md
  • references/utilities_config.md
  • … and 2 more

Open the folder on GitHubat commit 0e0d506

Compare with similar skills

Deepstream Dev next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Deepstream Dev compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Deepstream Dev this skillNVIDIA/skills3.5k—~3.3kAutomated safety check: PassApache-2.0
Vllm Deploy Simplevllm-project/vllm-skills103—~1.6kAutomated safety check: PassApache-2.0
Quark Env Preflightamd/Quark181—~1.4kAutomated safety check: PassMIT
Opensource Guide Coachcalf-ai/calfkit-sdk1491 repos~2.1kAutomated safety check: PassApache-2.0
Vss Deploy Detection Tracking 3DNVIDIA-AI-Blueprints/video-search-and-summarization1.9k—~5.1kAutomated safety check: NotesApache-2.0
Using Message Queuesancoleman/ai-design-components526—~2.9kAutomated safety check: PassMIT

Similar skills

  • Vllm Deploy Simple

    vllm-project/vllm-skills

    Quick install and deploy vLLM, start serving with a simple LLM, and test OpenAI API.

    103 GitHub stars~1.6k tokensUpdated 6 mo ago
    AI & LLM EngineeringAuto-check passed
  • Collect and normalize environment facts (OS, Python, GPU, CUDA/ROCm, container state) before Quark installation or PTQ planning.

    181 GitHub stars~1.4k tokensUpdated 9 days ago
    AI & LLM EngineeringAuto-check passed
  • Opensource Guide Coach

    calf-ai/calfkit-sdk

    A skill your agent uses when a user wants guidance on starting, contributing to, growing, governing, funding, securing, or sustaining an open source project, or asks about contributor onboarding…

    149 GitHub starsUsed in 1 repo~2.1k tokens
    Backend & APIsAuto-check passed
  • Vss Deploy Detection Tracking 3D

    NVIDIA-AI-Blueprints/video-search-and-summarization

    A skill your agent uses when deploying or operating standalone RTVI-CV-3D / MV3DT multi-camera 3D tracking for calibrated MP4/file inputs and live RTSP streams: missing-calibration handoff to AMC…

    1.9k GitHub stars~5.1k tokensUpdated today
    AI & LLM EngineeringAuto-check: notes
  • Using Message Queues

    ancoleman/ai-design-components

    Async communication patterns using message brokers and task queues.

    526 GitHub stars~2.9k tokensUpdated 10 mo ago
    Backend & APIsAuto-check passed
  • Streaming Data

    ancoleman/ai-design-components

    Build event streaming and real-time data pipelines with Kafka, Pulsar, Redpanda, Flink, and Spark.

    526 GitHub stars~2.9k tokensUpdated 10 mo ago
    Backend & APIsAuto-check passed

More from NVIDIA/skills

All 380 skills in this repo
  • Official

    A skill your agent uses when the user wants to deploy, run, debug, tear down, or call the REST API of the RTVI-CV 2D detection / tracking microservice.

    3.5k GitHub starsUsed in 1 repo~4.5k tokens
    Auto-check passed
  • Official

    Generates, validates, compares and explains HOLOLINK_def.svh macro files for the HSB IP, using bundled Python scripts and asking before it writes anything.

    3.5k GitHub stars~2.9k tokensUpdated today
    Auto-check passed
  • Official

    Runs and validates an end-to-end Mission Control demo in a locally installed Isaac Sim, with a Nova Carter robot driven through a Python server.

    3.5k GitHub stars~4.8k tokensUpdated today
    Auto-check passed
  • Orchestrates defect image generation for PCBA, metal surface and glass inspection with NVIDIA Cosmos AnomalyGen on OSMO, from cold-start Day 0 to real-photo Day 1 labeling.

    3.5k GitHub stars~5k tokensUpdated today
    Auto-check: notes
  • Orchestrates video data augmentation and auto-labeling workflows on OSMO, from flow selection and preflight checks to submission, monitoring and output download.

    3.5k GitHub stars~4.7k tokensUpdated today
    Auto-check: notes
  • Official

    Runs NVIDIA TAO Data Services KPI analysis on object detection results, comparing predictions to ground truth and writing per-class precision, recall and AP to a CSV.

    3.5k GitHub stars~2.7k tokensUpdated today
    Auto-check: notes

Questions about Deepstream Dev

What does Deepstream Dev do?

NVIDIA DeepStream SDK development with Python pyservicemaker API. Deepstream Dev is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. NVIDIA DeepStream SDK development with Python pyservicemaker API.

When should I use Deepstream Dev?

Deepstream Dev fits situations like: building video analytics pipelines; GStreamer-based video processing; tensorRT inference integration; object detection/tracking.

How do I install Deepstream Dev in Claude Code?

Run `npx skills add NVIDIA/skills --skill deepstream-dev -a claude-code`. Or copy the skill folder (skills/deepstream-dev in NVIDIA/skills) into .claude/skills/deepstream-dev in your project. Claude Code loads it when a task matches its description.

How do I install Deepstream Dev in Codex?

Run `npx skills add NVIDIA/skills --skill deepstream-dev -a codex`. Or copy the skill folder (skills/deepstream-dev in NVIDIA/skills) into .agents/skills/deepstream-dev in your project. Codex loads it when a task matches its description.

Can I use Deepstream Dev in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NVIDIA/skills --skill deepstream-dev -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/deepstream-dev, .gemini/skills/deepstream-dev, .github/skills/deepstream-dev and .opencode/skills/deepstream-dev in your project.

What does Deepstream Dev need to run?

Going by SKILL.md and its folder, Deepstream Dev needs the command-line tools its instructions call (pip). Our summary lists: Python 3; Docker.

Does Deepstream Dev access the network?

SKILL.md contains no URLs. Its commands use pip, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Deepstream Dev safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Deepstream Dev use?

Deepstream Dev is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Deepstream Dev use?

About 3.3k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 133k tokens, read only when the agent opens those files.

What are the alternatives to Deepstream Dev?

Skills that share tags, products or a category with Deepstream Dev: Vllm Deploy Simple (vllm-project/vllm-skills, 103 stars), Quark Env Preflight (amd/Quark, 181 stars), Opensource Guide Coach (calf-ai/calfkit-sdk, 149 stars) and Vss Deploy Detection Tracking 3D (NVIDIA-AI-Blueprints/video-search-and-summarization, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Deepstream Dev?

NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/skills, which has 3,534 GitHub stars. The repository holds 380 skills in this directory. The repository was last updated on October 7, 2026.

Source: NVIDIA/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.