exploits-search

# Vulnetix Exploit Search Skill ## Use when - You need to know what is being exploited in YOUR ecosystem this week (e.g. `--ecosystem npm --since 2026-04-01`). - Building a watchlist of weaponised CVEs for a specific package family or vendor. - Filtering for CISA-KEV-only items at HIGH/CRITICAL severity with EPSS > 0.5. - Looking for exploits from a specific source (e.g. Metasploit-only) for a red-team scenario. - Producing a weekly threat newsletter scoped to one ecosystem. ## Don't use for - Deep-diving a single CVE — use `/vulnetix:exploits`. - Daily SOC queue intersected with this repo's deps — use `/vulnetix:soc-triage`. - Listing CVEs for a single package — use `/vulnetix:vuln <package>`. ## 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 searches for vulnerabilities with known exploits across the entire VDB, with filtering by ecosystem, severity, exploit source, EPSS score, and CISA KEV status. Use it to **discover** exploited vulnerabilities relevant to your repository's technology stack. **This skill does not modify application code** -- it only updates ...