Individual skill

reporting-triage-validation

Validate a finding BEFORE you write it up — kill false positives, confirm real impact, check scope, and deduplicate. Load after a candidate bug and before reporting-bug-bounty-writeup or reporting-pentest-report. Signals: "I think I found", "is this reportable", a scanner hit, a reflected value, a 500 error, an open redirect, a CORS wildcard, "should I submit this".

skills/reporting/reporting-triage-validation/SKILL.md

Read pinned source

Source commit ee0e0c50d2f6d941a14b73dd85a2b470d0ab976e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
27
Repository last updated
Oct 14, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Triage & validation — earn the right to report

## When it applies
You have a *candidate* finding and you are about to spend an hour writing it up. Run this gate
first. It applies double on bug bounty (an invalid/duplicate report costs your signal and the
triager's time) and still matters on a pentest (a false positive in the report costs your
credibility with the client).

## Why it works
Most "findings" die on one of a few predictable questions. Asking them up front — cheaply, in
order — kills the weak ones before they cost report-writing time, and forces the survivors to
carry the evidence a triager actually needs. The rule is simple: **one failed gate = stop.**

## Method — four gates, in order
Back to top