exploits

# Vulnetix Exploit Analysis Skill ## Use when - A specific CVE just landed in your inbox and you need to decide patch urgency THIS WEEK. - You need MITRE ATT&CK technique mapping for a vulnerability before writing detection content. - Computing CWSS priority for a triage decision and want the full exploit-source breakdown. - Building an incident-response brief and need cached PoC source code for static review. - Cross-referencing `exploitationSignals` (from `package-search`) with the actual exploit count and source diversity. ## Don't use for - Listing exploits across many CVEs — use `/vulnetix:exploits-search`. - Just looking up the CVE record — use `/vulnetix:vuln`. - Generating IDS/IPS detection rules — use `/vulnetix:detection-rules`. - Executing a PoC against a target — Pix never executes; use `/vulnetix:exploit-test` to GENERATE a runnable command for manual execution. ## 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 analyzes exploit intelligence for a specific vulnerability (CVE, GHSA, etc.) and assesses its impact against the current repository. **This ...