vss-manage-video-io-storage

Manage VIOS REST API operations for sensors, streams, clips, snapshots, and video storage.

2|Updated Aug 20, 2026
One-click install
npx skills add https://github.com/atomicrajat/industry_safety_monitoring_system --skill vss-manage-video-io-storage-atomicrajat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vss-manage-video-io-storage
Source: https://github.com/atomicrajat/industry_safety_monitoring_system/tree/main/.claude/skills/vss-manage-video-io-storage
Command: npx skills add https://github.com/atomicrajat/industry_safety_monitoring_system --skill vss-manage-video-io-storage-atomicrajat

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Operating the NVIDIA VSS Video Input/Output and Storage (VIOS) service requires knowing dozens of REST endpoints, ID resolution rules, timestamp handling, and known platform defects. This Skill gives an agent the exact curl-based workflows to manage cameras, streams, recordings, clips, and snapshots without navigating the VIOS UI or guessing API contracts. ## Core Features & Use Cases - Sensor and stream management: List, add (ONVIF or RTSP), inspect, and delete sensors and streams, with automatic sensorId/streamId resolution. - Clip extraction and snapshots: Download MP4/TS clips and capture live or historical snapshots using timeline-validated timestamps. - File upload and storage: Upload local MP4 files as file-backed sensors via the VIOS PUT API, and route synthetic RTSP feeds through NvStreamer when needed. - Use Case: An operator asks to "download a two-second clip from the warehouse camera at 10:30 UTC" — the Skill probes VIOS health, resolves the sensor and stream IDs, checks recording timelines, and downloads the clip via the binary direct endpoint. ## Quick Start Ask the agent to list the active VIOS sensors and show their stream status using the VIOS REST API.

Frequently Asked Questions about vss-manage-video-io-storage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a camera or RTSP stream to VIOS?

Add a sensor by calling POST /vst/api/v1/sensor/add with either sensorIp plus credentials for ONVIF cameras, or sensorUrl with credentials embedded for RTSP streams. The response returns a sensorId used for all subsequent operations.

How do I download a video clip from a VIOS recording?

First fetch the stream's timelines via GET /storage/<streamId>/timelines to find a valid recorded range, then call GET /storage/file/<streamId>?startTime=...&endTime=...&container=mp4 with -o clip.mp4. Prefer the binary direct endpoint over the /url variant, which has a known double-http:// defect.

When should I use NvStreamer instead of the VIOS upload API?

Use the direct VIOS PUT /storage/file/{filename} API for storing a local video as a file-backed sensor. Use NvStreamer only when you explicitly need a live or synthetic RTSP camera feed, or need to retrieve a generated RTSP URL to register with VIOS.

Why do VIOS uploads fail with 'Failed to get media information'?

This error means the VIOS streamprocessing container was deployed without libav libraries. Set VST_INSTALL_ADDITIONAL_PACKAGES=true in the environment and redeploy so the container installs libavcodec, libavformat, and libavutil at startup.

What tasks should NOT use this VIOS management skill?

Do not use it for VLM inference or visual Q&A (use vss-ask-video), semantic archive search (vss-search-archive), clip summarization (vss-summarize-video), incident reports (vss-generate-video-report), or analytics queries (vss-query-analytics). It only covers VIOS and NvStreamer API operations.

What happens if the VIOS backend is not reachable?

The skill probes GET /vst/api/v1/sensor/version before any operation. If the probe fails, it offers to deploy VIOS standalone via its bundled deployment runbook or hand off to the vss-deploy-profile skill, and stops if the user declines both.