triage-validation

Validate vulnerability reports through structured multi-criteria gating with CVSS 3.1 guidance.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/venkatas/obsidian --skill triage-validation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: triage-validation
Source: https://github.com/venkatas/obsidian/tree/main/skills/triage-validation
Command: npx skills add https://github.com/venkatas/obsidian --skill triage-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Security programs struggle with noisy vulnerability submissions and inconsistent triage processes. This Skill provides a rigorous gate-based workflow to validate findings before they are escalated to remediation, reducing false positives and speeding up high-quality reports.

Core Features & Use Cases

  • 7-Question Gate enforces a strict, stepwise assessment where any incorrect answer stops the submission immediately.
  • 4 Pre-Submission Gates offer quick, deterministic validation to filter out invalid or out-of-scope reports early.
  • Chain Validation & CVSS Guidance standardizes risk assessment, including conditional validity with chain tables and a quick reference to CVSS 3.1.
  • 60-Second Pre-Submit Checklist provides a fast, repeatable sanity check before drafting the final report.
  • Use Case: security teams and bug bounty program operators can apply this process to improve consistency, reduce noise, and accelerate high-confidence findings to remediation.

Quick Start

Run the 7-Question Gate and 4 pre-submission gates in sequence, then document the final decision and rationale.

Frequently Asked Questions about triage-validation

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

FAQPage Schema
How do I validate vulnerability reports to reduce false positives in bug bounty triage?▼

Vulnerability report validation uses a structured, multi-criteria gating process to assess scope, impact, evidence, and novelty. Reviewers apply a 7-question gate and 4 pre-submission gates to enforce consistent triage and filter out invalid findings.

What is the best way to filter out-of-scope bug bounty submissions before remediation?▼

Filtering out-of-scope bug bounty submissions is handled by 4 pre-submission gates that offer quick, deterministic validation. These gates stop invalid reports early, reducing noise and accelerating high-confidence findings to remediation.

How does CVSS 3.1 guidance work with vulnerability chain validation?▼

CVSS 3.1 guidance standardizes risk assessment by providing a quick reference for scoring, while chain validation tables determine conditional validity. This combination ensures consistent evaluation of complex vulnerability chains during triage.

Can I use a step-by-step gate check for security researchers before drafting a report?▼

Security researchers can run a 60-second pre-submit checklist as a fast sanity check before drafting a final report. This stepwise process ensures findings pass initial validation gates and meet submission requirements.

Why does my vulnerability triage process produce inconsistent pass/fail decisions?▼

Inconsistent vulnerability triage decisions occur when reviewers lack a structured gating process. Applying a strict 7-question gate where any incorrect answer stops submission immediately enforces consistent, stepwise assessment across all reports.

What are the limitations of using gate checks for vulnerability report validation?▼

Gate checks for vulnerability validation require all criteria to pass sequentially, meaning a single incorrect answer stops the submission immediately. This strict approach may not accommodate nuanced reports that require conditional validity assessments.