vulnerability-triage

Triage CVEs and scanner findings into remediation decisions with SLAs.

3|2|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/JayRHa/AgentSkills --skill vulnerability-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vulnerability-triage
Source: https://github.com/JayRHa/AgentSkills/tree/main/vulnerability-triage
Command: npx skills add https://github.com/JayRHa/AgentSkills --skill vulnerability-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Vulnerability triage turns a flood of scanner findings or a single CVE into a ranked, justified remediation decision by combining CVSS scores, exploitability signals (EPSS, KEV, PoCs), exposure, and business impact into actionable SLAs.

Core Features & Use Cases

  • Score and rank findings across CVEs and scanner outputs with a transparent, reproducible framework.
  • Deduplicate findings by root cause, assess reachability, and assign remediation SLAs for leadership visibility.
  • Generate risk assessments and remediation memos for audits, leadership reviews, and incident response.

Quick Start

In a triage run, feed the findings into the scorer to obtain a prioritized list with SLAs and rationale, then act on top-P0 items first.

Frequently Asked Questions about vulnerability-triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prioritize CVE scanner findings using CVSS, EPSS, and KEV signals?

Vulnerability triage prioritizes CVE scanner findings by combining CVSS base scores, EPSS exploitability signals, and KEV status with asset exposure to generate defensible remediation SLAs. This multi-signal scoring model outputs a ranked list with clear rationale for patch prioritization.

What is the best way to deduplicate scanner findings by root cause for risk assessments?

Vulnerability triage deduplicates scanner findings by root cause and assesses reachability to produce unified risk assessments. It groups redundant vulnerabilities across production, cloud, and on-prem environments to assign accurate remediation SLAs for leadership visibility.

Can I generate remediation memos and audit reports from CVE triage decisions?

Vulnerability triage generates auditable remediation memos and risk assessments from structured CVE triage decisions. By applying a transparent scoring model to scanner outputs, it produces defensible documentation for audits, leadership reviews, and incident response.

What structured input do I need to perform vulnerability triage and assign SLAs?

Vulnerability triage requires structured input including CVSS base scores, KEV and EPSS signals, exposure data, asset criticality, data sensitivity, and SLA targets. Feeding these parameters into the scorer yields an auditable remediation decision with clear rationale.

How does vulnerability triage handle risk scoring across cloud and on-prem environments?

Vulnerability triage applies a reproducible multi-signal risk scoring framework across cloud and on-prem environments. It evaluates exposure, asset criticality, and exploitability to assign SLA-driven remediation priorities, ensuring consistent patch management decisions.

When should I use multi-signal vulnerability triage instead of relying on CVSS scores alone?

Vulnerability triage is necessary when CVSS scores alone lack business context, requiring EPSS, KEV, and asset criticality to justify remediation. Use it to translate raw scanner findings into SLA-driven, auditable patch decisions for production, cloud, and on-prem environments.