vss-manage-video-io-storage
Use to call the VIOS REST API (sensor list, timelines, clip extraction, snapshots, add/delete sensors and streams). Not for VLM inference or search.
npx skills add NVIDIA-AI-Blueprints/video-search-and-summarization --skill vss-manage-video-io-storage --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Manage VIOS and NvStreamer API operations for VSS video input/output and storage workflows: sensors, streams, uploads, snapshots, clips, timelines, and recording status.
How it works
- It instructs to call the VIOS REST API directly via curl to perform operations such as managing cameras/sensors, RTSP streams, recordings, snapshots, and storage.
- For uploading a video file to VIOS, use the direct VIOS API: PUT /vst/api/v1/storage/file/{filename}; NvStreamer is used only if a live/synthetic RTSP feed is explicitly required.
- It forbids using this skill for VLM inference, ad-hoc visual Q&A, semantic search, or narrative clip summaries; those tasks are assigned to other skills.
- It provides a set of setup prerequisites (VIOS must be reachable, necessary credentials, curl/jq/docker availability) and a deployment-prerequisite flow if VIOS is not reachable.
- It outlines a structured reference suite including API references, NvStreamer references, integration and deployment contracts, and known deployment issues.
- It describes procedural steps for workflow: sensor name/IP to clip or snapshot, including probing VIOS, listing sensors, obtaining streams, checking timelines, and using binary endpoints for downloads when possible.
When to use it
- When you need to call VIOS REST API operations for sensor management, storage, snapshots, clip extraction, and uploading video files to VIOS.
- When a live RTSP feed is required, or when you need to retrieve an RTSP URL via NvStreamer, explicitly using NvStreamer flow.
- When you intend to avoid UI navigation and operate directly through VIOS API endpoints.
- When you need to avoid VLM inference, semantic search, or clip narration tasks (these are delegated to other skills).
What it can touch
- VIOS REST API endpoints under /vst/api/v1 (sensor management, storage, timelines, live and replay endpoints).
- It references files under references/ for API reference, NvStreamer reference, and deployment/integration contracts.
Caveats
- Requires VIOS to be running and reachable at the VST ingress; otherwise deployment steps may be invoked.
- Includes known deployment issues (e.g., libav-missing, leftover containers causing 502) and directs to references/deploy-vios-service.md for remediation.
- Uses direct VIOS endpoints for file uploads and storage operations; if endpoint information is missing, the skill instructs to prompt for the VST endpoint.
- Primarily an API client; does not perform UI navigation or higher-level analytics unless supported by VIOS APIs.
## Purpose Manage VIOS and NvStreamer API operations for VSS video input/output and storage workflows: sensors, streams, uploads, snapshots, clips, timelines, and recording status. ## Prerequisites - Active VSS deployment reachable on `$HOST_IP` (see `vss-deploy-profile` and `references/`). - NGC credentials in `$NGC_CLI_API_KEY` and `$NVIDIA_API_KEY` for any image pulls. - `curl`, `jq`, and Docker available on the caller. ## Instructions # VIOS Operations Call the VIOS REST API to manage cameras/sensors, RTSP streams, recordings, snapshots, and storage. Use when asked to: add a camera, add an RTSP stream, list sensors, show configured sensors/cameras/streams, check stream status, get a snapshot, download a clip, upload a video file, or manage video storage. Query the VIOS API directly using curl — do not navigate the UI. **Upload routing rule:** - If the user asks to "upload `<file>.mp4` to VIOS", "upload a video file", or otherwise means storing a local video as a VIOS file-backed sensor, use the direct VIOS API: `PUT /vst/api/v1/storage/file/{filename}` from [`references/api-reference.md`](references/api-reference.md) Section 8. - Use NvStreamer only when the user explicitly nee
- Purpose
- Prerequisites
- Instructions
- Reference contracts shipped with this skill
- Deployment prerequisite — VIOS MUST be running
- Known limitation — leftover containers from prior deploys
- Setup
- Service Map
- Operations
- Workflow: sensor name/IP -> clip or snapshot
- Responses
- Examples
- Limitations
- Troubleshooting
curl -sf --max-time 5 "http://${HOST_IP}:30888/vst/api/v1/sensor/version" >/dev/null
curl -sf --connect-timeout 5 http://<VST_ENDPOINT>/vst/api/v1/sensor/version
curl -sf --connect-timeout 5 "http://<VST_ENDPOINT>/vst/api/v1/sensor/version"
curl -s "http://<VST_ENDPOINT>/vst/api/v1/sensor/list" | jq .
curl -s "http://<VST_ENDPOINT>/vst/api/v1/sensor/<sensorId>/streams" | jq .
curl -s "http://<VST_ENDPOINT>/vst/api/v1/storage/<streamId>/timelines" | jq .What does the vss-manage-video-io-storage skill do?
Use to call the VIOS REST API (sensor list, timelines, clip extraction, snapshots, add/delete sensors and streams). Not for VLM inference or search.
How do I install it?
Run `npx skills add NVIDIA-AI-Blueprints/video-search-and-summarization --skill vss-manage-video-io-storage --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From NVIDIA-AI-Blueprints/video-search-and-summarization, a repository with 1,773 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.