[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79FBH8EAD5FZQYESAVK3SCJ":3,"skill-same:01M79FBH8EAD5FZQYESAVK3SCJ":68},{"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":29,"commitSha":30,"skillDirectory":31,"forksCount":14,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":47},"01M79FBH8EAD5FZQYESAVK3SCJ","mcore-create-issue",null,"Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.","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\u002Fmcore-create-issue\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: mcore-create-issue\ndescription: Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.\nlicense: Apache-2.0\nwhen_to_use: User shares a GitHub Actions URL and wants to file a bug report; 'create an issue for this failure', 'file a bug for this CI run', 'triage this GitHub Actions failure'.\nuser_invocable: true\nargument: \"GitHub Actions run or job URL\"\nmetadata:\n  author: Philip Petrakian \u003Cppetrakian@nvidia.com>\n---\n\n# Triage CI Failure into a GitHub Issue\n\nInvestigate a failing GitHub Actions job, extract the root cause, and file a\nwell-structured bug issue against `NVIDIA\u002FMegatron-LM`.\n\n## Workflow\n\n### 1. Parse the URL\n\nThe argument is a GitHub Actions URL. It will be one of:\n\n- **Job URL**: `https:\u002F\u002Fgithub.com\u002F\u003Cowner>\u002F\u003Crepo>\u002Factions\u002Fruns\u002F\u003Crun_id>\u002Fjob\u002F\u003Cjob_id>`\n- **Run URL**: `https:\u002F\u002Fgithub.com\u002F\u003Cowner>\u002F\u003Crepo>\u002Factions\u002Fruns\u002F\u003Crun_id>`\n\nExtract `run_id` and, if present, `job_id`.\n\n### 2. Identify failed jobs\n\n- If a `job_id` was provided, use that job directly.\n- If only a `run_id` was provided, list all failed jobs in the run:\n\n  ```bash\n  gh run view \u003Crun_id> --repo NVIDIA\u002FMegatron-LM --json jobs \\\n    --jq '[.jobs[] | select(.conclusion == \"failure\") | {id: .databaseId, name: .name, url: .url}]'\n  ```\n\n  If multiple jobs failed, ask the user which one to triage, or triage all of them if they say so.\n\n### 3. Fetch the failure logs\n\nFor each failed job, retrieve the logs and narrow them down to the failure:\n\n```bash\n# Pull the raw log and keep only error-bearing lines\ngh api repos\u002FNVIDIA\u002FMegatron-LM\u002Factions\u002Fjobs\u002F\u003Cjob_id>\u002Flogs 2>&1 \\\n  | grep -E \"(FAILED|ERROR|\\bError\\b|assert|Traceback|Exception|##\\[error\\])\" \\\n  | head -200\n```\n\nAlso capture the full job name:\n\n```bash\ngh run view --job \u003Cjob_id> --repo NVIDIA\u002FMegatron-LM --json name --jq .name\n```\n\nIf the grep output is sparse, download the full logs and look for the pytest\n`FAILURES` section or the last non-zero exit signal.\n\n### 4. Resolve the triggering PR and test author\n\n**Triggering PR**: the run's head branch follows the pattern `pull-request\u002F\u003Cnumber>`.\nExtract it and resolve the PR:\n\n```bash\ngh run view \u003Crun_id> --repo NVIDIA\u002FMegatron-LM --json headBranch --jq .headBranch\n# → e.g. \"pull-request\u002F4332\"\n# Extract PR number and fetch metadata:\ngh pr view \u003Cpr_number> --repo NVIDIA\u002FMegatron-LM --json number,title,url \\\n  --jq '{number: .number, title: .title, url: .url}'\n```\n\n**Test file author**: find the GitHub login of whoever last touched the failing\ntest file. The file may not exist on `main` — first determine the PR's base\nbranch, then search from there:\n\n```bash\n# 1. Get the PR's base branch (e.g. \"main\", \"dev\", \"release\u002FX.Y\")\ngh pr view \u003Cpr_number> --repo NVIDIA\u002FMegatron-LM --json baseRefName --jq .baseRefName\n\n# 2. Search commits on that base branch\ngh api \"repos\u002FNVIDIA\u002FMegatron-LM\u002Fcommits?path=\u003Ctest-file-path>&sha=\u003Cbase-branch>&per_page=1\" \\\n  --jq '.[0] | {login: .author.login, name: .commit.author.name, sha: .sha}'\n```\n\nIf the result is empty (file was introduced by the PR itself), query the PR's\ncommits instead:\n\n```bash\ngh api \"repos\u002FNVIDIA\u002FMegatron-LM\u002Fpulls\u002F\u003Cpr_number>\u002Fcommits\" \\\n  --jq '[.[] | select(.files? \u002F\u002F [] | any(.filename == \"\u003Ctest-file-path>\"))] | .[0].author.login'\n```\n\nAs a last resort, list the PR commits and pick the author of the commit whose\nmessage most closely relates to the failing test file.\n\n### 5. Extract the root cause\n\nFrom the logs, identify:\n\n- **Failed test(s)**: lines matching `FAILED tests\u002F...::...` give the exact pytest node IDs.\n- **Error message**: the assertion failure, exception type, or first meaningful\n  traceback frame — keep it under ~30 lines.\n- **Job name**: the GitHub Actions job name (e.g. `tests\u002Funit_tests\u002Ftransformer\u002Fmoe\u002F**\u002F*.py - latest`).\n- **Run \u002F job URLs** and **PR URL**: for linking in the issue.\n\n### 6. Check for duplicate issues\n\nSearch for open issues that already cover the same test:\n\n```bash\ngh issue list --repo NVIDIA\u002FMegatron-LM \\\n  --state open \\\n  --search \"\u003Cfailed-test-filename>\" \\\n  --json number,title,url \\\n  --limit 10\n```\n\n- If a matching open issue exists, **do not create a new one**. Report the\n  existing issue to the user and stop.\n- If no match is found, proceed to file a new issue.\n\n### 7. Create the issue\n\nPass `--assignee \u003Ctest-author-login>` to assign the issue to the test file's\nauthor. Include the triggering PR URL in the issue body.\n\n```bash\ngh issue create \\\n  --repo NVIDIA\u002FMegatron-LM \\\n  --title \"🐛 CI failure: \u003Cfailed-test-node-id>\" \\\n  --label \"bug\" \\\n  --assignee \"\u003Ctest-author-login>\" \\\n  --body \"...\"\n```\n\nUse the bug-report template body structure:\n\n```markdown\n**Describe the bug**\n\nCI test `\u003Cfailed-test-node-id>` failed in job [`\u003Cjob-name>`](\u003Cjob-url>).\nTag @NVIDIA\u002Fmcore-oncall to get oncall's attention to this issue.\n\n**Failing run**\n\n| Field | Value |\n|-------|-------|\n| PR    | [#\u003Cpr_number>: \u003Cpr_title>](\u003Cpr_url>) |\n| Run   | [\u003Crun_id>](\u003Crun_url>) |\n| Job   | [\u003Cjob_name>](\u003Cjob_url>) |\n\n**Error**\n\n```\n\u003Ccore error message \u002F traceback — 30 lines max>\n```\n\n**Steps\u002FCode to reproduce bug**\n\nRe-run the failing CI job linked above, or locally inside the dev container:\n\n```bash\npytest \u003Cfailed-test-node-id>\n```\n\n**Additional context**\n\nTriaged automatically via `\u002Ftriage-issue`.\n```\n\nIf multiple tests failed in the same job, list each one as a separate bullet\nunder \"Describe the bug\" and include the combined error snippets. Assign the\nissue to the author of whichever test file appears first in the failure list.\n\n### 8. Report back to the user\n\nPrint the URL of the newly created issue (or the duplicate, if found) so the\nuser can review or share it.\n\n## Important guidelines\n\n- Never create an issue if a duplicate already exists — link the existing one instead.\n- Always include the triggering PR link in the issue body.\n- Always assign the issue to the test file's most recent author. If the author\n  lookup fails (e.g. the commit was made by a bot or the login is unavailable),\n  skip `--assignee` and note it in the \"Additional context\" section.\n- Keep the error snippet concise (≤30 lines). Truncate long tracebacks and note that the full log is available via the job URL.\n- Do not guess the root cause — quote the actual log output verbatim.\n- If the job is still in progress or the logs are unavailable, say so and ask the user to retry once the run completes.\n","# Triage CI Failure into a GitHub Issue\n\nInvestigate a failing GitHub Actions job, extract the root cause, and file a\nwell-structured bug issue against `NVIDIA\u002FMegatron-LM`.\n\n## Workflow\n\n### 1. Parse the URL\n\nThe argument is a GitHub Actions URL. It will be one of:\n\n- **Job URL**: `https:\u002F\u002Fgithub.com\u002F\u003Cowner>\u002F\u003Crepo>\u002Factions\u002Fruns\u002F\u003Crun_id>\u002Fjob\u002F\u003Cjob_id>`\n- **Run URL**: `https:\u002F\u002Fgithub.com\u002F\u003Cowner>\u002F\u003Crepo>\u002Factions\u002Fruns\u002F\u003Crun_id>`\n\nExtract `run_id` and, if present, `job_id`.\n\n### 2. Identify failed jobs\n\n- If a `job_id` was provided, use that job directly.\n- If only a `run_id` was provided, list all failed jobs in the run:\n\n  ```bash\n  gh run view \u003Crun_id> --repo NVIDIA\u002FMegatron-LM --json jobs \\\n    --jq '[.jobs[] | select(.conclusion == \"failure\") | {id: .databaseId, name: .name, url: .url}]'\n  ```\n\n  If multiple jobs failed, ask the user which one to triage, or triage all of them if they say so.\n\n### 3. Fetch the failure logs\n\nFor each failed job, retrieve the logs and narrow them down to the failure:\n\n```bash\n# Pull the raw log and keep only error-bearing lines\ngh api repos\u002FNVIDIA\u002FMegatron-LM\u002Factions\u002Fjobs\u002F\u003Cjob_id>\u002Flogs 2>&1 \\\n  | grep -E \"(FAILED|ERROR|\\bError\\b|assert|Traceback|Exception|##\\[error\\])\" \\\n  | head -200\n```\n\nAlso capture the full job name:\n\n```bash\ngh run view --job \u003Cjob_id> --repo NVIDIA\u002FMegatron-LM --json name --jq .name\n```\n\nIf the grep output is sparse, download the full logs and look for the pytest\n`FAILURES` section or the last non-zero exit signal.\n\n### 4. Resolve the triggering PR and test author\n\n**Triggering PR**: the run's head branch follows the pattern `pull-request\u002F\u003Cnumber>`.\nExtract it and resolve the PR:\n\n```bash\ngh run view \u003Crun_id> --repo NVIDIA\u002FMegatron-LM --json headBranch --jq .headBranch\n# → e.g. \"pull-request\u002F4332\"\n# Extract PR number and fetch metadata:\ngh pr view \u003Cpr_number> --repo NVIDIA\u002FMegatron-LM --json number,title,url \\\n  --jq '{number: .number, title: .title, url: .url}'\n```\n\n**Test file author**: find the GitHub login of whoever last touched the failing\ntest file. The file may not exist on `main` — first determine the PR's base\nbranch, then search from there:\n\n```bash\n# 1. Get the PR's base branch (e.g. \"main\", \"dev\", \"release\u002FX.Y\")\ngh pr view \u003Cpr_number> --repo NVIDIA\u002FMegatron-LM --json baseRefName --jq .baseRefName\n\n# 2. Search commits on that base branch\ngh api \"repos\u002FNVIDIA\u002FMegatron-LM\u002Fcommits?path=\u003Ctest-file-path>&sha=\u003Cbase-branch>&per_page=1\" \\\n  --jq '.[0] | {login: .author.login, name: .commit.author.name, sha: .sha}'\n```\n\nIf the result is empty (file was introduced by the PR itself), query the PR's\ncommits instead:\n\n```bash\ngh api \"repos\u002FNVIDIA\u002FMegatron-LM\u002Fpulls\u002F\u003Cpr_number>\u002Fcommits\" \\\n  --jq '[.[] | select(.files? \u002F\u002F [] | any(.filename == \"\u003Ctest-file-path>\"))] | .[0].author.login'\n```\n\nAs a last resort, list the PR commits and pick the author of the commit whose\nmessage most closely relates to the failing test file.\n\n### 5. Extract the root cause\n\nFrom the logs, identify:\n\n- **Failed test(s)**: lines matching `FAILED tests\u002F...::...` give the exact pytest node IDs.\n- **Error message**: the assertion failure, exception type, or first meaningful\n  traceback frame — keep it under ~30 lines.\n- **Job name**: the GitHub Actions job name (e.g. `tests\u002Funit_tests\u002Ftransformer\u002Fmoe\u002F**\u002F*.py - latest`).\n- **Run \u002F job URLs** and **PR URL**: for linking in the issue.\n\n### 6. Check for duplicate issues\n\nSearch for open issues that already cover the same test:\n\n```bash\ngh issue list --repo NVIDIA\u002FMegatron-LM \\\n  --state open \\\n  --search \"\u003Cfailed-test-filename>\" \\\n  --json number,title,url \\\n  --limit 10\n```\n\n- If a matching open issue exists, **do not create a new one**. Report the\n  existing issue to the user and stop.\n- If no match is found, proceed to file a new issue.\n\n### 7. Create the issue\n\nPass `--assignee \u003Ctest-author-login>` to assign the issue to the test file's\nauthor. Include the triggering PR URL in the issue body.\n\n```bash\ngh issue create \\\n  --repo NVIDIA\u002FMegatron-LM \\\n  --title \"🐛 CI failure: \u003Cfailed-test-node-id>\" \\\n  --label \"bug\" \\\n  --assignee \"\u003Ctest-author-login>\" \\\n  --body \"...\"\n```\n\nUse the bug-report template body structure:\n\n```markdown\n**Describe the bug**\n\nCI test `\u003Cfailed-test-node-id>` failed in job [`\u003Cjob-name>`](\u003Cjob-url>).\nTag @NVIDIA\u002Fmcore-oncall to get oncall's attention to this issue.\n\n**Failing run**\n\n| Field | Value |\n|-------|-------|\n| PR    | [#\u003Cpr_number>: \u003Cpr_title>](\u003Cpr_url>) |\n| Run   | [\u003Crun_id>](\u003Crun_url>) |\n| Job   | [\u003Cjob_name>](\u003Cjob_url>) |\n\n**Error**\n\n```\n\u003Ccore error message \u002F traceback — 30 lines max>\n```\n\n**Steps\u002FCode to reproduce bug**\n\nRe-run the failing CI job linked above, or locally inside the dev container:\n\n```bash\npytest \u003Cfailed-test-node-id>\n```\n\n**Additional context**\n\nTriaged automatically via `\u002Ftriage-issue`.\n```\n\nIf multiple tests failed in the same job, list each one as a separate bullet\nunder \"Describe the bug\" and include the combined error snippets. Assign the\nissue to the author of whichever test file appears first in the failure list.\n\n### 8. Report back to the user\n\nPrint the URL of the newly created issue (or the duplicate, if found) so the\nuser can review or share it.\n\n## Important guidelines\n\n- Never create an issue if a duplicate already exists — link the existing one instead.\n- Always include the triggering PR link in the issue body.\n- Always assign the issue to the test file's most recent author. If the author\n  lookup fails (e.g. the commit was made by a bot or the login is unavailable),\n  skip `--assignee` and note it in the \"Additional context\" section.\n- Keep the error snippet concise (≤30 lines). Truncate long tracebacks and note that the full log is available via the job URL.\n- Do not guess the root cause — quote the actual log output verbatim.\n- If the job is still in progress or the logs are unavailable, say so and ask the user to retry once the run completes.\n",{"name":5,"license":15,"argument":24,"metadata":25,"description":7,"when_to_use":27,"user_invocable":28},"GitHub Actions run or job URL",{"author":26},"Philip Petrakian \u003Cppetrakian@nvidia.com>","User shares a GitHub Actions URL and wants to file a bug report; 'create an issue for this failure', 'file a bug for this CI run', 'triage this GitHub Actions failure'.",true,"main","c475fc64e94e803b50d14a791dfee8853fbb2c5c","skills\u002Fnvidia\u002Fmcore-create-issue","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory","https:\u002F\u002Fgithub.com\u002FElogic360","2026-11-08 22:21:22",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":28},[37,40,43],{"tool":38,"command":39},"npx","npx skills add Elogic360\u002Fsoftware-factory --skill mcore-create-issue",{"tool":41,"command":42},"bunx","bunx skills add Elogic360\u002Fsoftware-factory --skill mcore-create-issue",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Elogic360\u002Fsoftware-factory --skill mcore-create-issue","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fmcore-create-issue\u002FSKILL.md",[48,54,58,62],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"BENCHMARK.md","REFERENCE","参考文档",2844,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fmcore-create-issue\u002FBENCHMARK.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"evals\u002Fevals.json",3,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fmcore-create-issue\u002Fevals\u002Fevals.json",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"skill-card.md",2448,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fmcore-create-issue\u002Fskill-card.md",{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"skill.oms.sig","OTHER","其他",4589,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fmcore-create-issue\u002Fskill.oms.sig",[69,76,83,90,97,104],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"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":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"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":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"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":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"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":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"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":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},"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",[],[]]