Run1 vulnerability json parsing
[COLM'26] SkillLearnBench is the first benchmark for evaluating continual learning methods that automatically generate agent skills.
npx -y skills add cxcscmu/SkillLearnBench --skill run1_vulnerability-json-parsingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Extracting specific security metadata (CVE, CVSS, Fix versions) from structured vulnerability reports like npm audit JSON or OSV.
SKILL.md
1.5 KB, 350 tokens by cl100k_base, as published. Nobody here has run it
Extracting Metadata
When parsing the JSON output from a security audit tool (like npm audit --json), focus on the following fields within the advisories or vulnerabilities objects:
- Package Name: The key or
namefield in the vulnerability object. - Installed Version: Cross-referenced from the
package-lock.jsonor theversionfield in the audit report. - CVE ID: Found under
cves(array) oridentifiers. Use the primary CVE ID (e.g., CVE-2023-xxxx). If unavailable, look for GHSA (GitHub Security Advisory) IDs. - Severity: The
severityfield (e.g.,high,critical). - CVSS Score: Often found under
cvss.scoreor within the advisory metadata. If missing from the local audit, it may need to be fetched via the reference URL provided. - Fixed Version: Look for
fixAvailable.versionorpatched_versions. If no patch is available, denote asN/A. - Title/Description: Found in the
titleorsummaryfield. - Reference URL: Found in the
urlorreferencesarray.
Python Processing Example
Use the json and csv modules in Python to transform the audit data:
import json
import csv
def extract_vulnerabilities(json_data):
results = []
# Logic to iterate through JSON nodes, filter by severity,
# and map to the target CSV columns.
return results