[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79FCPS9K4TJYDFK6GDS97Y2":3,"skill-same:01M79FCPS9K4TJYDFK6GDS97Y2":103},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M79FCPS9K4TJYDFK6GDS97Y2","nemo-evaluator-plugin",null,"Use when working on the Evaluator plugin CLI, jobs, SDK-backed specs, metric types, or plugin-owned Evaluator skills.","Elogic360\u002Fsoftware-factory","Elogic360","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F156535519?v=4","01M74NH3F0RB13PWB7JZDE2V80","elogic360","01M74NH3FPC65082MDZVMFHDM3",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fnemo-evaluator-plugin\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: nemo-evaluator-plugin\ndescription: Use when working on the Evaluator plugin CLI, jobs, SDK-backed specs, metric types, or plugin-owned Evaluator skills.\nmetadata:\n  owner: nemo-platform\n  maturity: active\nlicense: Apache-2.0\n---\n\n# Evaluator Plugin\n\nUse this skill for evaluation tasks against a running NeMo Platform server. The plugin-backed CLI interface is `nemo evaluator`; the legacy generated `nemo evaluation` API command group is not the target surface for new guidance.\n\n## CLI Interface\n\n### Prerequisites\n\n- all commands in this file assume that the shell's working dir is at the root of the Nvidia-NeMo\u002Fnemo-platform repo\n- activate the Python virtual environment before invoking the `nemo` CLI: `source .venv\u002Fbin\u002Factivate`\n\nCheck plugin status from the CLI:\n\n```bash\nnemo evaluator info\n```\n\n## Metric Types\n\n### Explore Available Metrics\n\nTo view available metric names, run:\n\n```bash\nnemo evaluator metric-types\n```\n\nTo view a specific metric schema, pass a metric name from the `metric_types` list above:\n\n```bash\nnemo evaluator metric-types \u003Cmetric-name>\n```\n\nInspect all the registered metric schema contracts:\n\n```bash\nnemo evaluator evaluate explain\n```\n\n> Note: use `nemo evaluator evaluate explain` as the source of truth for the current plugin input schema. It will return a large json schema response, so strongly prefer `nemo evaluator metric-types` when you only need metric names and corresponding schemas.\n\n## Evaluation Spec\n\nEvaluation spec is a payload that is provided to CLI as an input to execute evaluation.\n\nAt a high level, a spec describes:\n\n- `metrics`: bundled Evaluator SDK metric configurations\n- `dataset`: inline rows to evaluate or platform FilesetRef that contains the dataset\n- `params`: optional Evaluator SDK execution parameters\n- `target`: optional model or agent target for online evaluation\n\nSee the LLM-judge spec example at [assets\u002Fspecs\u002Fllm_as_judge.json](.\u002Fassets\u002Fspecs\u002Fllm_as_judge.json).\n\n### Metric Bundle Payloads\n\nThe checked-in [spec examples](.\u002Fassets\u002Fspecs) use bundled SDK metrics. The fields under `metrics[*].payload` are generated by `bundle_metric(metric, CloudpickleMetricBundlePackager())`.\n\nTo see the pattern for configuring a pre-defined SDK metric, for example `ExactMatchMetric`, and converting it into bundled metric JSON, inspect `build_metric_bundle_example()` in [generate_example_specs.py](.\u002Fscripts\u002Fgenerate_example_specs.py) and run:\n\n```bash\nuv run --frozen python skills\u002Fnemo-evaluator-plugin\u002Fscripts\u002Fgenerate_example_specs.py\n```\n\n## Run Evaluations\n\n### Run Using File Spec Reference\n\nWhen using the `nemo evaluator evaluate run` command, results are saved into local temporary directories and the link is printed to stdout.\nPrefer the `--spec-file` named argument over inline shell JSON because metric bundles include serialized payloads.\nExamples of various specs are provided in the [assets\u002Fspecs](.\u002Fassets\u002Fspecs\u002F) directory.\n\n#### Evaluate using `exact-match` metric\n\nSee the spec example at [assets\u002Fspecs\u002Fexact_match_metric.json](.\u002Fassets\u002Fspecs\u002Fexact_match_metric.json).\n\n```bash\nnemo evaluator evaluate run --spec-file skills\u002Fnemo-evaluator-plugin\u002Fassets\u002Fspecs\u002Fexact_match_metric.json\n```\n\n#### Evaluate using a benchmark metric set\n\n```bash\nnemo evaluator evaluate run --spec-file skills\u002Fnemo-evaluator-plugin\u002Fassets\u002Fspecs\u002Fexact_match_benchmark.json\n```\n\n#### Evaluate using `LLM-Judge` metric\n\nUses an LLM to score responses. See the spec example at [assets\u002Fspecs\u002Fllm_as_judge.json](.\u002Fassets\u002Fspecs\u002Fllm_as_judge.json).\n\n```bash\nnemo evaluator evaluate run --spec-file skills\u002Fnemo-evaluator-plugin\u002Fassets\u002Fspecs\u002Fllm_as_judge.json\n```\n\n### Run Evaluation As A Durable Job\n\nUse the `nemo evaluator evaluate submit` command to create a durable evaluation job. The response of this command returns a job handler object instead of the evaluation result.\n\n```bash\nnemo evaluator evaluate submit \\\n  --spec-file skills\u002Fnemo-evaluator-plugin\u002Fassets\u002Fspecs\u002Fexact_match_metric.json\n```\n\nThe submit response includes the generated job's `name` field, for example `nemo-evaluator-zlhn1ecd`. Wait for the job to complete, then list and download the job results.\n\n```bash\nnemo jobs get-status \u003Cjob-name>\nnemo jobs get \u003Cjob-name>\nnemo jobs results list \u003Cjob-name>\nnemo jobs results download aggregate-scores --job \u003Cjob-name> --output-file aggregate-scores.json\nnemo jobs results download row-scores --job \u003Cjob-name> --output-file row-scores.jsonl\n```\n\n## Python SDK Interface\n\nEvaluator Python SDK client is exposed as `evaluator` variable on `NeMoPlatform` instance:\n\n```python\nfrom nemo_platform import NeMoPlatform\n\nplatform_client = NeMoPlatform(base_url=\"http:\u002F\u002Flocalhost:8080\")\nstatus = platform_client.evaluator.plugin_status()\n```\n\nSee examples of using the plugin SDK interface in [plugin_sdk_examples.py](.\u002Fassets\u002Fexamples\u002Fplugin_sdk_examples.py).\n\n## Security\nMake sure not to print any secrets to stdout since this can be collected as logs\n\n## Additional Resources\n\nFor LLM-judge setup notes, see [LLM Judge Notes](references\u002Fllm-judge.md).\n\nFor evaluator API key auth, see [Evaluator API Auth](references\u002Fapi-auth.md).\n\nFor local and cluster troubleshooting, see [Evaluation Troubleshooting](references\u002Ftroubleshooting.md).\n","# Evaluator Plugin\n\nUse this skill for evaluation tasks against a running NeMo Platform server. The plugin-backed CLI interface is `nemo evaluator`; the legacy generated `nemo evaluation` API command group is not the target surface for new guidance.\n\n## CLI Interface\n\n### Prerequisites\n\n- all commands in this file assume that the shell's working dir is at the root of the Nvidia-NeMo\u002Fnemo-platform repo\n- activate the Python virtual environment before invoking the `nemo` CLI: `source .venv\u002Fbin\u002Factivate`\n\nCheck plugin status from the CLI:\n\n```bash\nnemo evaluator info\n```\n\n## Metric Types\n\n### Explore Available Metrics\n\nTo view available metric names, run:\n\n```bash\nnemo evaluator metric-types\n```\n\nTo view a specific metric schema, pass a metric name from the `metric_types` list above:\n\n```bash\nnemo evaluator metric-types \u003Cmetric-name>\n```\n\nInspect all the registered metric schema contracts:\n\n```bash\nnemo evaluator evaluate explain\n```\n\n> Note: use `nemo evaluator evaluate explain` as the source of truth for the current plugin input schema. It will return a large json schema response, so strongly prefer `nemo evaluator metric-types` when you only need metric names and corresponding schemas.\n\n## Evaluation Spec\n\nEvaluation spec is a payload that is provided to CLI as an input to execute evaluation.\n\nAt a high level, a spec describes:\n\n- `metrics`: bundled Evaluator SDK metric configurations\n- `dataset`: inline rows to evaluate or platform FilesetRef that contains the dataset\n- `params`: optional Evaluator SDK execution parameters\n- `target`: optional model or agent target for online evaluation\n\nSee the LLM-judge spec example at [assets\u002Fspecs\u002Fllm_as_judge.json](.\u002Fassets\u002Fspecs\u002Fllm_as_judge.json).\n\n### Metric Bundle Payloads\n\nThe checked-in [spec examples](.\u002Fassets\u002Fspecs) use bundled SDK metrics. The fields under `metrics[*].payload` are generated by `bundle_metric(metric, CloudpickleMetricBundlePackager())`.\n\nTo see the pattern for configuring a pre-defined SDK metric, for example `ExactMatchMetric`, and converting it into bundled metric JSON, inspect `build_metric_bundle_example()` in [generate_example_specs.py](.\u002Fscripts\u002Fgenerate_example_specs.py) and run:\n\n```bash\nuv run --frozen python skills\u002Fnemo-evaluator-plugin\u002Fscripts\u002Fgenerate_example_specs.py\n```\n\n## Run Evaluations\n\n### Run Using File Spec Reference\n\nWhen using the `nemo evaluator evaluate run` command, results are saved into local temporary directories and the link is printed to stdout.\nPrefer the `--spec-file` named argument over inline shell JSON because metric bundles include serialized payloads.\nExamples of various specs are provided in the [assets\u002Fspecs](.\u002Fassets\u002Fspecs\u002F) directory.\n\n#### Evaluate using `exact-match` metric\n\nSee the spec example at [assets\u002Fspecs\u002Fexact_match_metric.json](.\u002Fassets\u002Fspecs\u002Fexact_match_metric.json).\n\n```bash\nnemo evaluator evaluate run --spec-file skills\u002Fnemo-evaluator-plugin\u002Fassets\u002Fspecs\u002Fexact_match_metric.json\n```\n\n#### Evaluate using a benchmark metric set\n\n```bash\nnemo evaluator evaluate run --spec-file skills\u002Fnemo-evaluator-plugin\u002Fassets\u002Fspecs\u002Fexact_match_benchmark.json\n```\n\n#### Evaluate using `LLM-Judge` metric\n\nUses an LLM to score responses. See the spec example at [assets\u002Fspecs\u002Fllm_as_judge.json](.\u002Fassets\u002Fspecs\u002Fllm_as_judge.json).\n\n```bash\nnemo evaluator evaluate run --spec-file skills\u002Fnemo-evaluator-plugin\u002Fassets\u002Fspecs\u002Fllm_as_judge.json\n```\n\n### Run Evaluation As A Durable Job\n\nUse the `nemo evaluator evaluate submit` command to create a durable evaluation job. The response of this command returns a job handler object instead of the evaluation result.\n\n```bash\nnemo evaluator evaluate submit \\\n  --spec-file skills\u002Fnemo-evaluator-plugin\u002Fassets\u002Fspecs\u002Fexact_match_metric.json\n```\n\nThe submit response includes the generated job's `name` field, for example `nemo-evaluator-zlhn1ecd`. Wait for the job to complete, then list and download the job results.\n\n```bash\nnemo jobs get-status \u003Cjob-name>\nnemo jobs get \u003Cjob-name>\nnemo jobs results list \u003Cjob-name>\nnemo jobs results download aggregate-scores --job \u003Cjob-name> --output-file aggregate-scores.json\nnemo jobs results download row-scores --job \u003Cjob-name> --output-file row-scores.jsonl\n```\n\n## Python SDK Interface\n\nEvaluator Python SDK client is exposed as `evaluator` variable on `NeMoPlatform` instance:\n\n```python\nfrom nemo_platform import NeMoPlatform\n\nplatform_client = NeMoPlatform(base_url=\"http:\u002F\u002Flocalhost:8080\")\nstatus = platform_client.evaluator.plugin_status()\n```\n\nSee examples of using the plugin SDK interface in [plugin_sdk_examples.py](.\u002Fassets\u002Fexamples\u002Fplugin_sdk_examples.py).\n\n## Security\nMake sure not to print any secrets to stdout since this can be collected as logs\n\n## Additional Resources\n\nFor LLM-judge setup notes, see [LLM Judge Notes](references\u002Fllm-judge.md).\n\nFor evaluator API key auth, see [Evaluator API Auth](references\u002Fapi-auth.md).\n\nFor local and cluster troubleshooting, see [Evaluation Troubleshooting](references\u002Ftroubleshooting.md).\n",{"name":5,"license":15,"metadata":24,"description":7},{"owner":25,"maturity":26},"nemo-platform","active","main","c475fc64e94e803b50d14a791dfee8853fbb2c5c","skills\u002Fnvidia\u002Fnemo-evaluator-plugin","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory","https:\u002F\u002Fgithub.com\u002FElogic360","2026-11-08 22:21:22",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Elogic360\u002Fsoftware-factory --skill nemo-evaluator-plugin",{"tool":39,"command":40},"bunx","bunx skills add Elogic360\u002Fsoftware-factory --skill nemo-evaluator-plugin",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Elogic360\u002Fsoftware-factory --skill nemo-evaluator-plugin","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fnemo-evaluator-plugin\u002FSKILL.md",true,[47,53,59,63,67,73,77,81,85,89,93,97],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"assets\u002Fexamples\u002Fplugin_sdk_examples.py","SCRIPT","脚本",3849,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fnemo-evaluator-plugin\u002Fassets\u002Fexamples\u002Fplugin_sdk_examples.py",{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"assets\u002Fspecs\u002Fexact_match_benchmark.json","ASSET","资产文件",4355,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fnemo-evaluator-plugin\u002Fassets\u002Fspecs\u002Fexact_match_benchmark.json",{"path":60,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":61,"sourceHtmlUrl":62},"assets\u002Fspecs\u002Fexact_match_metric.json",1889,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fnemo-evaluator-plugin\u002Fassets\u002Fspecs\u002Fexact_match_metric.json",{"path":64,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":65,"sourceHtmlUrl":66},"assets\u002Fspecs\u002Fllm_as_judge.json",4987,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fnemo-evaluator-plugin\u002Fassets\u002Fspecs\u002Fllm_as_judge.json",{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"BENCHMARK.md","REFERENCE","参考文档",4244,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fnemo-evaluator-plugin\u002FBENCHMARK.md",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"evals\u002Fevals.json",1171,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fnemo-evaluator-plugin\u002Fevals\u002Fevals.json",{"path":78,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fapi-auth.md",895,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fnemo-evaluator-plugin\u002Freferences\u002Fapi-auth.md",{"path":82,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fllm-judge.md",1259,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fnemo-evaluator-plugin\u002Freferences\u002Fllm-judge.md",{"path":86,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Ftroubleshooting.md",1545,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fnemo-evaluator-plugin\u002Freferences\u002Ftroubleshooting.md",{"path":90,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":91,"sourceHtmlUrl":92},"scripts\u002Fgenerate_example_specs.py",1641,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fnemo-evaluator-plugin\u002Fscripts\u002Fgenerate_example_specs.py",{"path":94,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":95,"sourceHtmlUrl":96},"skill-card.md",3973,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fnemo-evaluator-plugin\u002Fskill-card.md",{"path":98,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":101,"sourceHtmlUrl":102},"skill.oms.sig","OTHER","其他",6561,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fnemo-evaluator-plugin\u002Fskill.oms.sig",[104,111,118,125,132,139],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M79G206MT3J6S0GY3C45P2KV","vss-summarize-video","Use to summarize a recorded video via the LVS summarization microservice (HITL-gated) with a VLM fallback. Not for report generation or live RTSP captioning.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-summarize-video\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":19},"01M79G1WN63PGRE8CKD47WEBQ5","vss-setup-video-analytics-api","Use to deploy the vss-video-analytics-api REST service standalone (config-source, data-log bind, Elasticsearch, optional Kafka). Not for full warehouse deploy.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-setup-video-analytics-api\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":19},"01M79G1S9F7VY3EF6H53PRP5AN","vss-setup-behavior-analytics","Use to deploy the vss-behavior-analytics service standalone (entrypoint, config-source, optional calibration). Not for the full warehouse deploy.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-setup-behavior-analytics\u002FSKILL.md",[],[],{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":19},"01M79G1N1S1Y27PFZPYMNK1MTQ","vss-search-archive","Use this skill to run top-level VSS fusion search on archived video, or to ingest video files \u002F RTSP streams for search. Do NOT use for ad-hoc visual Q&A (use vss-ask-video), live captioning (use vss-deploy-dense-captioning), or video summarization and reports (use vss-summarize-video).","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-search-archive\u002FSKILL.md",[],[],{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":19},"01M79G1H6WN0Q6C0VCAXCZX6B7","vss-query-analytics","Use this skill when reading video-analytics metrics, incidents, alerts, and sensor data via the VA-MCP server (port 9901). Not for live VLM or incident-range narrative reports.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-query-analytics\u002FSKILL.md",[],[],{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":19},"01M79G1DYPNXQS7QHZ0AAF5FX5","vss-manage-video-io-storage","Use to call the VIOS REST API (sensor list, timelines, clip extraction, snapshots, add\u002Fdelete sensors and streams). Not for VLM inference or search.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-manage-video-io-storage\u002FSKILL.md",[],[]]