dashboard

# Vulnetix Vulnerability Dashboard ## Use when - You want a single view of every vulnerability tracked in this repo, grouped by status and decision. - Someone asks "where did we leave triage last week?". - Onboarding to a repo and you want to see prior security decisions before duplicating work. - You want to spot stale `under_investigation` items that need re-triaging. - Pre-release: confirm no high-severity entries remain open before tagging. ## Don't use for - Fetching new vulnerability data — use `/vulnetix:soc-triage` or `/vulnetix:vuln`. - Applying fixes — use `/vulnetix:fix`. - Cross-repo dashboards — this skill reads only the current repo's memory file. ## Conventions This skill follows [`_lib/contract.md`](../_lib/contract.md): the Vulnetix CLI is auto-installed by hooks, `.vulnetix/capabilities.yaml` is always present, every `vulnetix vdb` call is piped through a verified `jq` filter from [`_lib/jq/`](../_lib/jq/), independent calls run in parallel as concurrent Bash tool calls, and trailing follow-ups are limited to one line. See the contract for output style, memory write rules, and cooldowns. This skill reads `.vulnetix/memory.yaml` and displays a comprehensive vulnerability status report. It is read-only and does not modify any files. ## Workflow ### Step 1: Load Memory 1. Use **Glob** to check if `.vulnetix/memory.yaml` exists in the repo root 2. If it does not exist, display: **"No vulnerability data found. Run `/vulnetix:vuln <package>` or `/vulnet...