What problem does it solve?
This Skill prevents wasting time and submitting invalid security findings by forcing a strict 7-question validation gate and additional pre-submission checks before any report is written.
Core Features & Use Cases
7-Question Gate (ordered stop rules): Disqualifies a finding immediately when step-by-step attackerability, scope acceptance, in-scope asset targeting, realistic access assumptions, novelty/duplication, impact beyond “technically possible,” or known-invalid bug class rules fail.
4 Pre-Submission Gates: Ensures the bug is real, confirms impact quality, performs deduplication against public/disclosed sources, and checks report-quality essentials like title, reproducible steps, evidence, and non-theoretical remediation language.
Conditional validity & severity guidance: Uses chain-required vs standalone tables to decide when a finding is only valid after end-to-end exploitation, plus a CVSS 3.1 quick reference and severity decision discipline.
Quick Start
Use the triage-validation skill to evaluate a single draft finding (including your Q1 HTTP request template, proposed impact claim, scope justification, and evidence) before writing any report.