[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78TM76JVG64818BTS2RGDG7":3,"skill-same:01M78TM76JVG64818BTS2RGDG7":61},{"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":41,"commitSha":42,"skillDirectory":43,"forksCount":14,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":46,"install":47,"resources":60},"01M78TM76JVG64818BTS2RGDG7","dos-verify-done-claims",null,"Before accepting an agent's 'done \u002F shipped \u002F fixed' claim, verify it against ground truth (git ancestry + the commit's own diff) using the DOS kernel's `dos verify` and `dos commit-audit` — never the agent's own narration.","Elogic360\u002Fsoftware-factory","Elogic360","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F156535519?v=4","01M74NH3F0RB13PWB7JZDE2V80","elogic360","01M74NH3FPC65082MDZVMFHDM3",0,"MIT","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fintegrations\u002Fantigravity-skills\u002Fplugins\u002Fantigravity-awesome-skills-claude\u002Fskills\u002Fdos-verify-done-claims\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: dos-verify-done-claims\ndescription: \"Before accepting an agent's 'done \u002F shipped \u002F fixed' claim, verify it against ground truth (git ancestry + the commit's own diff) using the DOS kernel's `dos verify` and `dos commit-audit` — never the agent's own narration.\"\ncategory: quality\nrisk: safe\nsource: community\nsource_repo: anthony-chaudhary\u002Fdos-kernel\nsource_type: community\ndate_added: \"2026-06-12\"\nauthor: anthony-chaudhary\ntags: [verification, git, ai-agents, trust, quality-gate]\ntools: [claude, cursor, gemini]\nlicense: \"MIT\"\nlicense_source: \"https:\u002F\u002Fgithub.com\u002Fanthony-chaudhary\u002Fdos-kernel\u002Fblob\u002Fmaster\u002FLICENSE\"\n---\n\n# Verify done-claims against ground truth, not the agent's word\n\n## Overview\n\nWhen an AI agent says \"done\", \"shipped\", or \"fixed\", that is a **claim**, not a\nfact — and a claim the agent checks by re-reading its own work is *consistency,\nnot grounding*. This skill replaces that self-report with a verdict from a\nwitness the agent did not author: it shells the **DOS kernel** (`dos verify`,\n`dos commit-audit`) to confirm the claimed effect from git ancestry and the\ncommit's actual diff. DOS is deterministic — no API key, no LLM. The verdict is\ngit-only and offline as used here; the one exception is `dos verify` in a\nworkspace that wires a CI oracle, which `--no-ci` suppresses (see Security &\nSafety Notes).\n\nThis skill adapts the DOS reference \"witness-claim\" pattern\n(`anthony-chaudhary\u002Fdos-kernel`) into a host-agnostic screenplay.\n\n## When to Use This Skill\n\n- Use when an agent reports a task\u002Fphase\u002Ffeature as **complete** and you want\n  that \"done\" confirmed from evidence before building on it.\n- Use right after a commit, to confirm the commit's **message matches its diff**\n  (catch a `fix:` that only touched a README, or a \"tests pass\" that deleted the\n  assertions).\n- Use when folding many sub-agents' results — verify each claimed effect instead\n  of trusting the return string.\n- **Do not** use it to judge whether code is *correct* — that is what the test\n  suite is for. This skill checks did-the-claimed-thing-actually-ship.\n\n## How It Works\n\n### Step 1: Install the kernel (once)\n\n```bash\npip install dos-kernel        # provides the `dos` CLI; deterministic, no key\n```\n\n### Step 2: Audit the latest commit's claim vs its diff\n\nA commit subject is forgeable (whoever wrote the message authored it); the files\nit touched are not (git did). `dos commit-audit` grades the subject against the\nactual diff:\n\n```bash\ndos commit-audit --workspace . HEAD --json\n```\n\n`commit-audit --json` prints a JSON **array** of audited commits (one element\neven for a single `HEAD`), so read `verdict` from the first element — e.g.\n`dos commit-audit --workspace . HEAD --json | jq -r '.[0].verdict'`. (Without\n`--json` the same verdict prints as a one-line text row: `· OK …`,\n`⚑ UNWITNESSED …`, or `· abstain …`.) The verdicts are: `OK` (the diff backs the\nclaim's *kind*), `CLAIM_UNWITNESSED` (the subject's claim is not evidenced by the\ndiff — treat the \"done\" as unproven), or `ABSTAIN`. This judges the *kind* of\nchange, never correctness — run the tests for that.\n\n### Step 3: Verify a named phase actually shipped\n\nIf the agent claims a specific plan\u002Fphase landed, confirm it from git history\nrather than the transcript:\n\n```bash\ndos verify --workspace . PLAN PHASE --json --no-ci\n```\n\n`--no-ci` keeps the verdict git-only (see the Security note below). With `--json`\nyou get the `shipped` and `source` fields. (The default text form prints\n`SHIPPED PLAN PHASE (via grep)` or `NOT_SHIPPED PLAN PHASE (via none)` — the same\nverdict, and the process exit code is non-zero when not shipped.)\n\nGrade `shipped: true` by the `source`, because git fallback grades itself by\n**forgeability** — and forgeable evidence is exactly what this skill exists to\ndistrust:\n\n- `registry` or `grep-artifact` — **non-forgeable** (a registry row, or an\n  artefact\u002Fdiff rung). This closes the claim.\n- `grep-subject` (or bare `grep`) — **forgeable**: a commit *subject* or body\n  carried the phase token, which an agent can write without doing the work (even\n  on an empty commit). Treat this as *shipped-per-the-subject*, not confirmed —\n  corroborate it (run `dos commit-audit` on that commit, below) before you close.\n- `none` — no positive evidence; accept as \"not shipped\", not as a tool failure.\n\n### Step 4: Fold only confirmed effects\n\nAccept the agent's \"done\" **only** when Step 2\u002F3 corroborate it. If\n`CLAIM_UNWITNESSED` or `shipped: false`, the work is not done regardless of how\nconfidently the agent narrated it — send it back.\n\n## Examples\n\n### Example 1: gate an agent's \"I fixed the bug\" claim\n\n```bash\n# The agent committed and said it's fixed. Check the diff backs the claim.\n# commit-audit --json returns an array, so read the first element's verdict:\ndos commit-audit --workspace . HEAD --json | jq -r '.[0].verdict'\n# OK                -> the change is of the claimed kind; now run the tests\n# CLAIM_UNWITNESSED -> the commit doesn't do what it says; reject\n```\n\n### Example 2: confirm a feature phase shipped before closing a ticket\n\n```bash\ndos verify --workspace . AUTH AUTH2 --json --no-ci\n# shipped: true, source: registry|grep-artifact -> non-forgeable; safe to close\n# shipped: true, source: grep-subject|grep       -> forgeable subject\u002Fbody match;\n#   shipped-per-the-subject only -> corroborate with commit-audit before closing\n# shipped: false, source: none -> no evidence; keep the ticket open\n```\n\n## Best Practices\n\n- ✅ Run `dos commit-audit HEAD` immediately after every agent commit.\n- ✅ Treat `source: none` \u002F `CLAIM_UNWITNESSED` as \"not done\", not as a tool error.\n- ✅ Close a claim on a **non-forgeable** `source` (`registry`, `grep-artifact`).\n  Treat `grep-subject` \u002F bare `grep` as forgeable (an agent can write the subject\n  text) — corroborate before closing.\n- ✅ Keep the test suite as the separate correctness gate — this skill checks shipping, not correctness.\n- ❌ Don't accept a \"done\" because the agent's prose was confident.\n- ❌ Don't use this to replace code review or testing.\n\n## Limitations\n\n- This skill does not replace environment-specific validation, testing, or expert review.\n- It checks whether a claimed change *shipped* \u002F matches its diff — not whether the code is *correct*.\n- `dos verify` reads git history; in a repo with no commits there is nothing to witness (it will honestly report `source: none`).\n- Stop and ask for clarification if required inputs (a git repo, the `dos` CLI) are missing.\n\n## Security & Safety Notes\n\n- This skill runs shell commands: `pip install dos-kernel` and the read-only\n  `dos` verbs (`dos commit-audit`, `dos verify`). These verbs never **mutate**\n  the repo or push. `dos commit-audit` only reads git history and the working\n  tree (no network). `dos verify` is also git-only **unless** the workspace has\n  wired a CI oracle (`[verify] non_git_oracle` in its `dos.toml`), in which case\n  it may shell a network check (e.g. `gh api`) for the verdict — pass `--no-ci`\n  (as the examples above do) to force the git-only path and guarantee no network.\n- `pip install dos-kernel` installs from PyPI. The distribution name is\n  `dos-kernel` (the bare `dos` on PyPI is an unrelated package — do not install\n  it). Pin a version in locked environments.\n- Run in the repository you intend to adjudicate; the `--workspace .` argument\n  scopes every verdict to that repo.\n\n## Common Pitfalls\n\n- **Problem:** `dos verify` returns `source: none` and it looks like a failure.\n  **Solution:** That is the honest \"no evidence\" verdict — it means the phase has\n  no ship commit, so the claim is unproven. Re-stamp the real commit or keep the\n  task open.\n- **Problem:** Installing the wrong package.\n  **Solution:** The PyPI name is `dos-kernel`, not `dos`.\n\n## Related Skills\n\n- The upstream DOS reference screenplays (`dos-witness-claim`, `dos-goal-gate`)\n  in `anthony-chaudhary\u002Fdos-kernel` cover the multi-agent fan-out and\n  self-stopping-agent variants of this same witness discipline.\n","# Verify done-claims against ground truth, not the agent's word\n\n## Overview\n\nWhen an AI agent says \"done\", \"shipped\", or \"fixed\", that is a **claim**, not a\nfact — and a claim the agent checks by re-reading its own work is *consistency,\nnot grounding*. This skill replaces that self-report with a verdict from a\nwitness the agent did not author: it shells the **DOS kernel** (`dos verify`,\n`dos commit-audit`) to confirm the claimed effect from git ancestry and the\ncommit's actual diff. DOS is deterministic — no API key, no LLM. The verdict is\ngit-only and offline as used here; the one exception is `dos verify` in a\nworkspace that wires a CI oracle, which `--no-ci` suppresses (see Security &\nSafety Notes).\n\nThis skill adapts the DOS reference \"witness-claim\" pattern\n(`anthony-chaudhary\u002Fdos-kernel`) into a host-agnostic screenplay.\n\n## When to Use This Skill\n\n- Use when an agent reports a task\u002Fphase\u002Ffeature as **complete** and you want\n  that \"done\" confirmed from evidence before building on it.\n- Use right after a commit, to confirm the commit's **message matches its diff**\n  (catch a `fix:` that only touched a README, or a \"tests pass\" that deleted the\n  assertions).\n- Use when folding many sub-agents' results — verify each claimed effect instead\n  of trusting the return string.\n- **Do not** use it to judge whether code is *correct* — that is what the test\n  suite is for. This skill checks did-the-claimed-thing-actually-ship.\n\n## How It Works\n\n### Step 1: Install the kernel (once)\n\n```bash\npip install dos-kernel        # provides the `dos` CLI; deterministic, no key\n```\n\n### Step 2: Audit the latest commit's claim vs its diff\n\nA commit subject is forgeable (whoever wrote the message authored it); the files\nit touched are not (git did). `dos commit-audit` grades the subject against the\nactual diff:\n\n```bash\ndos commit-audit --workspace . HEAD --json\n```\n\n`commit-audit --json` prints a JSON **array** of audited commits (one element\neven for a single `HEAD`), so read `verdict` from the first element — e.g.\n`dos commit-audit --workspace . HEAD --json | jq -r '.[0].verdict'`. (Without\n`--json` the same verdict prints as a one-line text row: `· OK …`,\n`⚑ UNWITNESSED …`, or `· abstain …`.) The verdicts are: `OK` (the diff backs the\nclaim's *kind*), `CLAIM_UNWITNESSED` (the subject's claim is not evidenced by the\ndiff — treat the \"done\" as unproven), or `ABSTAIN`. This judges the *kind* of\nchange, never correctness — run the tests for that.\n\n### Step 3: Verify a named phase actually shipped\n\nIf the agent claims a specific plan\u002Fphase landed, confirm it from git history\nrather than the transcript:\n\n```bash\ndos verify --workspace . PLAN PHASE --json --no-ci\n```\n\n`--no-ci` keeps the verdict git-only (see the Security note below). With `--json`\nyou get the `shipped` and `source` fields. (The default text form prints\n`SHIPPED PLAN PHASE (via grep)` or `NOT_SHIPPED PLAN PHASE (via none)` — the same\nverdict, and the process exit code is non-zero when not shipped.)\n\nGrade `shipped: true` by the `source`, because git fallback grades itself by\n**forgeability** — and forgeable evidence is exactly what this skill exists to\ndistrust:\n\n- `registry` or `grep-artifact` — **non-forgeable** (a registry row, or an\n  artefact\u002Fdiff rung). This closes the claim.\n- `grep-subject` (or bare `grep`) — **forgeable**: a commit *subject* or body\n  carried the phase token, which an agent can write without doing the work (even\n  on an empty commit). Treat this as *shipped-per-the-subject*, not confirmed —\n  corroborate it (run `dos commit-audit` on that commit, below) before you close.\n- `none` — no positive evidence; accept as \"not shipped\", not as a tool failure.\n\n### Step 4: Fold only confirmed effects\n\nAccept the agent's \"done\" **only** when Step 2\u002F3 corroborate it. If\n`CLAIM_UNWITNESSED` or `shipped: false`, the work is not done regardless of how\nconfidently the agent narrated it — send it back.\n\n## Examples\n\n### Example 1: gate an agent's \"I fixed the bug\" claim\n\n```bash\n# The agent committed and said it's fixed. Check the diff backs the claim.\n# commit-audit --json returns an array, so read the first element's verdict:\ndos commit-audit --workspace . HEAD --json | jq -r '.[0].verdict'\n# OK                -> the change is of the claimed kind; now run the tests\n# CLAIM_UNWITNESSED -> the commit doesn't do what it says; reject\n```\n\n### Example 2: confirm a feature phase shipped before closing a ticket\n\n```bash\ndos verify --workspace . AUTH AUTH2 --json --no-ci\n# shipped: true, source: registry|grep-artifact -> non-forgeable; safe to close\n# shipped: true, source: grep-subject|grep       -> forgeable subject\u002Fbody match;\n#   shipped-per-the-subject only -> corroborate with commit-audit before closing\n# shipped: false, source: none -> no evidence; keep the ticket open\n```\n\n## Best Practices\n\n- ✅ Run `dos commit-audit HEAD` immediately after every agent commit.\n- ✅ Treat `source: none` \u002F `CLAIM_UNWITNESSED` as \"not done\", not as a tool error.\n- ✅ Close a claim on a **non-forgeable** `source` (`registry`, `grep-artifact`).\n  Treat `grep-subject` \u002F bare `grep` as forgeable (an agent can write the subject\n  text) — corroborate before closing.\n- ✅ Keep the test suite as the separate correctness gate — this skill checks shipping, not correctness.\n- ❌ Don't accept a \"done\" because the agent's prose was confident.\n- ❌ Don't use this to replace code review or testing.\n\n## Limitations\n\n- This skill does not replace environment-specific validation, testing, or expert review.\n- It checks whether a claimed change *shipped* \u002F matches its diff — not whether the code is *correct*.\n- `dos verify` reads git history; in a repo with no commits there is nothing to witness (it will honestly report `source: none`).\n- Stop and ask for clarification if required inputs (a git repo, the `dos` CLI) are missing.\n\n## Security & Safety Notes\n\n- This skill runs shell commands: `pip install dos-kernel` and the read-only\n  `dos` verbs (`dos commit-audit`, `dos verify`). These verbs never **mutate**\n  the repo or push. `dos commit-audit` only reads git history and the working\n  tree (no network). `dos verify` is also git-only **unless** the workspace has\n  wired a CI oracle (`[verify] non_git_oracle` in its `dos.toml`), in which case\n  it may shell a network check (e.g. `gh api`) for the verdict — pass `--no-ci`\n  (as the examples above do) to force the git-only path and guarantee no network.\n- `pip install dos-kernel` installs from PyPI. The distribution name is\n  `dos-kernel` (the bare `dos` on PyPI is an unrelated package — do not install\n  it). Pin a version in locked environments.\n- Run in the repository you intend to adjudicate; the `--workspace .` argument\n  scopes every verdict to that repo.\n\n## Common Pitfalls\n\n- **Problem:** `dos verify` returns `source: none` and it looks like a failure.\n  **Solution:** That is the honest \"no evidence\" verdict — it means the phase has\n  no ship commit, so the claim is unproven. Re-stamp the real commit or keep the\n  task open.\n- **Problem:** Installing the wrong package.\n  **Solution:** The PyPI name is `dos-kernel`, not `dos`.\n\n## Related Skills\n\n- The upstream DOS reference screenplays (`dos-witness-claim`, `dos-goal-gate`)\n  in `anthony-chaudhary\u002Fdos-kernel` cover the multi-agent fan-out and\n  self-stopping-agent variants of this same witness discipline.\n",{"name":5,"risk":24,"tags":25,"tools":31,"author":35,"source":36,"license":15,"category":37,"date_added":38,"description":7,"source_repo":39,"source_type":36,"license_source":40},"safe",[26,27,28,29,30],"verification","git","ai-agents","trust","quality-gate",[32,33,34],"claude","cursor","gemini","anthony-chaudhary","community","quality","2026-06-12","anthony-chaudhary\u002Fdos-kernel","https:\u002F\u002Fgithub.com\u002Fanthony-chaudhary\u002Fdos-kernel\u002Fblob\u002Fmaster\u002FLICENSE","main","c475fc64e94e803b50d14a791dfee8853fbb2c5c","integrations\u002Fantigravity-skills\u002Fplugins\u002Fantigravity-awesome-skills-claude\u002Fskills\u002Fdos-verify-done-claims","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory","https:\u002F\u002Fgithub.com\u002FElogic360","2026-11-08 22:21:22",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add Elogic360\u002Fsoftware-factory --skill dos-verify-done-claims",{"tool":53,"command":54},"bunx","bunx skills add Elogic360\u002Fsoftware-factory --skill dos-verify-done-claims",{"tool":56,"command":57},"pnpm","pnpm dlx skills add Elogic360\u002Fsoftware-factory --skill dos-verify-done-claims","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fintegrations\u002Fantigravity-skills\u002Fplugins\u002Fantigravity-awesome-skills-claude\u002Fskills\u002Fdos-verify-done-claims\u002FSKILL.md",true,[],[62,70,77,84,91,98],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"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.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-summarize-video\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"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":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"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":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"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":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"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":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"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",[],[]]