triage-validation

Validate bug bounty findings through sequential gate checks and evidence requirements.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/ajtazer/briyani-hunter --skill triage-validation-ajtazer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage-validation
Source: https://github.com/ajtazer/briyani-hunter/tree/main/.gemini/skills/triage-validation
Command: npx skills add https://github.com/ajtazer/briyani-hunter --skill triage-validation-ajtazer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces a strict, repeatable triage and validation process for bug bounty findings, ensuring only well-supported issues proceed to reporting.

Core Features & Use Cases

  • 7-Question Gate: validates findings through a sequential, authoritative checklist; one incorrect answer stops the process.
  • 4 Pre-Submission Gates: ensures readiness and evidence before submission.
  • Chain Table & CVSS Guidance: helps classify impact, scope, and remediation effort to align with program policies.

Quick Start

Run the 7-Question Gate to validate a finding before drafting a report.

Frequently Asked Questions about triage-validation

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

FAQPage Schema
How do I validate bug bounty findings before submitting a report?

To validate bug bounty findings before reporting, run a 7-Question Gate sequence that applies strict triage checks. One incorrect answer halts the process, ensuring only well-supported vulnerability reports proceed to submission.

What is triage validation for vulnerability reports?

Triage validation for vulnerability reports is an automated process enforcing sequential gate checks, deduplication, and evidence requirements. It ensures findings meet quality criteria and align with program policies before responsible disclosure.

How do I ensure I have enough evidence before submitting a vulnerability report?

To ensure enough evidence before submitting a vulnerability report, pass the finding through 4 pre-submission gates. These readiness checks verify evidence requirements are satisfied prior to drafting the final disclosure.

How do I classify the impact and scope of a vulnerability finding?

To classify the impact and scope of a vulnerability finding, use a Chain Table and CVSS guidance. This helps map remediation effort and impact severity to align with specific bug bounty program policies.

What happens if a finding fails a gate check during triage validation?

If a finding fails a gate check during triage validation, the sequential process stops immediately. This authoritative checklist approach prevents unsupported issues from advancing toward bug bounty report submission.