Back to catalog
Static reviewDevelopment

Skill dossier

performing-cve-prioritization-with-kev-catalog

Source declaration

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 triaging a vulnerability backlog, deciding patch order across many CVEs, or building an automated KEV+EPSS prioritization workflow.

The author's original description, preserved in English. It describes intent, not verified performance.

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 triaging a vulnerability backlog, deciding patch order across many CVEs, or building an automated KEV+EPSS prioritization workflow.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

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 triaging a vulnerability backlog, deciding patch order across many CVEs, or building an automated KEV+EPSS prioritization workflow. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/performing-cve-prioritization-with-kev-catalog/SKILL.md:L100]
  • Step 1: Fetch and Parse the KEV Catalog [Source statement; provisional, not tested. Evidence: skills/performing-cve-prioritization-with-kev-catalog/SKILL.md:L102]
  • Step 2: Enrich with EPSS Scores [Source statement; provisional, not tested. Evidence: skills/performing-cve-prioritization-with-kev-catalog/SKILL.md:L139]
  • Step 3: Build the Prioritization Engine [Source statement; provisional, not tested. Evidence: skills/performing-cve-prioritization-with-kev-catalog/SKILL.md:L161]
  • Step 4: Generate Prioritization Report [Source statement; provisional, not tested. Evidence: skills/performing-cve-prioritization-with-kev-catalog/SKILL.md:L227]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/performing-cve-prioritization-with-kev-catalog/SKILL.md:L1-L38]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
8
Markdown files
5
scripts
2
references
4
Size
49.4 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/performing-cve-prioritization-with-kev-catalog/assets/template.mdReference1.2 KB
skills/performing-cve-prioritization-with-kev-catalog/LICENSEOther11 KB
skills/performing-cve-prioritization-with-kev-catalog/references/api-reference.mdReference5.2 KB
skills/performing-cve-prioritization-with-kev-catalog/references/standards.mdReference1.2 KB
skills/performing-cve-prioritization-with-kev-catalog/references/workflows.mdReference2.8 KB
skills/performing-cve-prioritization-with-kev-catalog/scripts/agent.pyScript8.7 KB
skills/performing-cve-prioritization-with-kev-catalog/scripts/process.pyScript9.4 KB
skills/performing-cve-prioritization-with-kev-catalog/SKILL.mdInstruction10 KB

SKILL.md frontmatter

{
  "name": "performing-cve-prioritization-with-kev-catalog",
  "description": "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 triaging a vulnerability backlog, deciding patch order across many CVEs, or building an automated KEV+EPSS prioritization workflow.",
  "domain": "cybersecurity",
  "subdomain": "vulnerability-management",
  "tags": [
    "cisa-kev",
    "cve",
    "vulnerability-prioritization",
    "epss",
    "bod-22-01",
    "threat-intelligence",
    "remediation"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_ai_rmf": [
    "MEASURE-2.7",
    "MAP-5.1",
    "MANAGE-2.4"
  ],
  "atlas_techniques": [
    "AML.T0070",
    "AML.T0066",
    "AML.T0082"
  ],
  "nist_csf": [
    "ID.RA-01",
    "ID.RA-02",
    "ID.IM-02",
    "ID.RA-06"
  ],
  "mitre_attack": [
    "T1190",
    "T1203",
    "T1068"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Action

    Overview

    Source-described action candidate under “Overview”; not verified execution.

  2. 02
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  3. 03
    Action

    Core Concepts

    Source-described action candidate under “Core Concepts”; not verified execution.

  4. 04
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  5. 05
    Action

    Step 1: Fetch and Parse the KEV Catalog

    Source-described action candidate under “Step 1: Fetch and Parse the KEV Catalog”; not verified execution.

  6. 06
    Action

    Step 2: Enrich with EPSS Scores

    Source-described action candidate under “Step 2: Enrich with EPSS Scores”; not verified execution.

Inspect all extracted workflow candidates (18 candidate steps)
  1. 07
    Action

    Step 3: Build the Prioritization Engine

    Source-described action candidate under “Step 3: Build the Prioritization Engine”; not verified execution.

  2. 08
    Output

    Step 4: Generate Prioritization Report

    Source-described output candidate under “Step 4: Generate Prioritization Report”; not verified execution.

  3. 09
    Action

    Best Practices

    Source-described action candidate under “Best Practices”; not verified execution.

  4. 10
    Action

    Update the KEV catalog daily since CISA adds new entries multiple times per week

    Source-described action candidate under “Best Practices”; not verified execution.

  5. 11
    Action

    Always cross-reference KEV with EPSS; a CVE may have high EPSS but not yet be in KEV

    Source-described action candidate under “Best Practices”; not verified execution.

  6. 12
    Action

    Treat all KEV-listed CVEs as P1-Emergency regardless of CVSS score

    Source-described action candidate under “Best Practices”; not verified execution.

  7. 13
    Action

    Pay special attention to KEV entries flagged with "Known Ransomware Campaign Use"

    Source-described action candidate under “Best Practices”; not verified execution.

  8. 14
    Action

    Automate KEV comparison against your vulnerability scan results in CI/CD pipelines

    Source-described action candidate under “Best Practices”; not verified execution.

  9. 15
    Action

    Track KEV due dates separately for FCEB compliance requirements

    Source-described action candidate under “Best Practices”; not verified execution.

  10. 16
    Decision

    Use KEV as a leading indicator for threat hunting; if a CVE is added, check for prior exploitation in your environment

    Source-described decision candidate under “Best Practices”; not verified execution.

  11. 17
    Action

    Common Pitfalls

    Source-described action candidate under “Common Pitfalls”; not verified execution.

  12. 18
    Action

    Related Skills

    Source-described action candidate under “Related Skills”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Items warrant review

56 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Medium

Network access is mentioned

35 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 35 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

21 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 21 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/performing-cve-prioritization-with-kev-catalog/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 8 collected file(s), 5 Markdown file(s), and 2 script file(s), enabling source-level inspection. [Evidence: skills/performing-cve-prioritization-with-kev-catalog/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/performing-cve-prioritization-with-kev-catalog
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.