patch-triage
/patch-triage
Triage a set of CVEs — CVSS + EPSS + KEV scoring, prioritization, and recommended remediation order. Use when asked to "triage these CVEs", "which vulnerabilities matter", or "prioritize our patching".
- Author
- tonone-ai ↗
- Repository
- tonone ↗
- Licence
- MIT
- Last repository change
- 14.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 14.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Triage a set of CVEs — CVSS + EPSS + KEV scoring, prioritization, and recommended remediation order. Use when asked to "triage these CVEs", "which vulnerabilities matter", or "prioritize our patching".
Triggers from the description
Original author description
Triage a set of CVEs — CVSS + EPSS + KEV scoring, prioritization, and recommended remediation order. Use when asked to "triage these CVEs", "which vulnerabilities matter", or "prioritize our patching".
How it works
- Steps
- Key Rules
- Delivery
SKILL.md preview
--- name: patch-triage description: Triage a set of CVEs — CVSS + EPSS + KEV scoring, prioritization, and recommended remediation order. Use when asked to "triage these CVEs", "which vulnerabilities matter", or "prioritize our patching". allowed-tools: Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion version: 1.5.0 author: tonone-ai <hello@tonone.ai> license: MIT compatibility: Designed for Claude Code tags: [security, vulnerability-management, triage] --- # Patch Triage You are Patch — Vulnerability Management Engineer on the Security Operations Team. ## Steps ### Step 0: Confirm Context Ask the user for any missing context needed to produce a useful output. If the request is clear, skip questions and proceed. ### Step 1: Gather Context Gather CVE list, affected systems (internet-facing status, data sensitivity), and current patch window constraints. ### Step 2: Produce Output Output a prioritized CVE list: each CVE with CVSS, EPSS, KEV status, asset tier, final priority, and recommended remediation action. ### Step 3: Summary Output a brief summary: - What was produced - Key risks or open questions - Recommended next steps ## Key Rules - Follow the output format defined in docs/output-kit.md - Always flag when outside security expertise is required (legal counsel, law enforcement, regulatory) - Pair every risk finding with a business impact statement ## Delivery If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
Versions
The database has no other skills named patch-triage.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 620974cc47ad (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100vuln-prioritization
Prioritize vulnerabilities by real risk using CISA KEV, EPSS, CVSS v4/v3.1, SSVC decision trees, asset criticality and exposure, rather than CVSS score alone, and set remediation SLAs. Use when a scan produces too many findings, when building a patch priority list, or when… - 100performing-cve-prioritization-with-kev-catalog
Fetch and parse the CISA Known Exploited Vulnerabilities (KEV) catalog, enrich it with EPSS scores and CVSS metrics, and build a multi-factor prioritization engine and report that ranks CVE remediation by real-world exploitation evidence and BOD 22-01 deadlines. Use when… - 100vulnerability-prioritization
Prioritize Wazuh vulnerability-detector findings with CISA KEV, FIRST EPSS, CVSS and asset context into CISA SSVC decisions and remediation SLAs; use for vulnerability sweeps, CVE alerts or patch-priority questions. - 90vulnerability-prioritization
Rank a set of vulnerabilities by real-world risk using CVSS (severity), EPSS (exploit probability), CISA KEV (known exploited), and asset/exposure context — so remediation effort goes to what actually matters first. Use when a triaged finding list needs a defensible "fix this first" order. - 100implementing-epss-score-for-vulnerability-prioritization
Queries FIRST's Exploit Prediction Scoring System (EPSS) API to fetch exploitation-probability and percentile scores for CVEs, then uses those scores to prioritize vulnerability remediation. Use when triaging or ranking a vulnerability backlog by real-world 30-day exploitation… - 100managing-vulnerabilities
Prioritize and drive remediation of a vulnerability backlog by real risk, not raw CVSS — combining severity with exploitation signals (EPSS, CISA KEV), asset exposure and business context, using SSVC-style decisions, distinguishing reachable from merely present, and tracking…