triaging-findings

Verify, deduplicate, and rank scanner findings into TRIAGE.json and TRIAGE.md.

125|42|Updated May 19, 2025
One-click install
npx skills add https://github.com/SocketDev/socket-mcp --skill triaging-findings
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triaging-findings
Source: https://github.com/SocketDev/socket-mcp/tree/main/.claude/skills/fleet/triaging-findings
Command: npx skills add https://github.com/SocketDev/socket-mcp --skill triaging-findings

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Adversarial triage of raw security-scanner output. It verifies each finding, collapses duplicates, re-ranks by derived exploitability, and tags with an owner, producing a concise, actionable triage view.

Core Features & Use Cases

  • Verification: validate that each finding is real, actionable, and worth remediation.
  • Deduplication: collapse duplicates across scanners to a single canonical finding.
  • Ranking by exploitability: prioritize survivors using derived exploitability rather than scanner severity.
  • Routing: assign each finding to an appropriate owner for remediation and follow-up.
  • Input/output flexibility: accepts VULN-FINDINGS.json, scanner results, or markdown reports and emits TRIAGE.json + TRIAGE.md for downstream workflow.
  • Use cases include triaging vulnerability backlog, preparing engineering backlogs, and coordinating across security and development teams.

Quick Start

Feed a findings file or directory to triaging-findings to normalize, deduplicate, verify, and triage the results into TRIAGE.json and TRIAGE.md.

Frequently Asked Questions about triaging-findings

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

FAQPage Schema
How do I triage raw security scanner output to verify real vulnerabilities?

Security scanner triage validates each finding for authenticity and actionability, deduplicates results across multiple tools, and re-ranks survivors by derived exploitability. It processes raw scanner outputs, markdown, or JSON reports to produce concise actionable triage views.

What's the best way to deduplicate vulnerability findings across multiple scanners?

Vulnerability deduplication collapses duplicate findings from multiple scanners into a single canonical finding. This triage process normalizes raw outputs and markdown or JSON reports, ensuring each unique vulnerability appears only once for downstream remediation.

How do I rank security findings by exploitability instead of scanner severity?

Ranking by exploitability prioritizes verified findings using derived exploitability metrics rather than relying on default scanner severity. This approach re-ranks survivors after deduplication to ensure remediation efforts target genuinely exploitable vulnerabilities first.

Can I use markdown and JSON reports as input for vulnerability triage?

Vulnerability triage accepts VULN-FINDINGS.json, raw scanner results, and markdown or JSON reports as input. It normalizes these formats during interactive ingestion, supporting checkpointed processing to ensure reproducible triage sessions before outputting TRIAGE.json and TRIAGE.md.

How do I route deduplicated security findings to owners for remediation?

Routing assigns each verified and deduplicated finding to an appropriate owner for remediation and follow-up. The triage process tags every surviving vulnerability after exploitability ranking, coordinating remediation across security and development teams through structured output files.

What output formats does security findings triage generate for downstream workflows?

Security findings triage generates TRIAGE.json and TRIAGE.md outputs for downstream remediation workflows. These files contain verified, deduplicated, and exploitability-ranked findings routed to owners, enabling coordination across security and engineering backlogs.