triage-validation

Validate bug bounty findings through 7-question and 4 pre-submission gates.

1|1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/guib1/red-team-docker --skill triage-validation-guib1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage-validation
Source: https://github.com/guib1/red-team-docker/tree/main/pentest-lab/.agents/skills/bug-bounty/skills/triage-validation
Command: npx skills add https://github.com/guib1/red-team-docker --skill triage-validation-guib1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates rigorous validation of bug bounty findings to prevent unverified reports from being submitted.

Core Features & Use Cases

  • 7-Question Gate: enforces a fixed sequence of critical checks to disqualify invalid findings.
  • 4 Pre-Submission Gates: ensures required criteria (scope, impact, reproducibility, evidence) are met before reporting.
  • Standardized Evidence & Templates: provides consistent checklists and templates to document findings.
  • Deduplication & Documentation: helps avoid duplicate disclosures and references supporting the finding.

Quick Start

Follow the 7-question gate and 4 pre-submission gates to validate a finding before submission.

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?

Validating bug bounty findings before reporting requires passing a 7-question gate and 4 pre-submission gates that verify scope, impact, reproducibility, and evidence to prevent unverified submissions.

What is triage validation for security vulnerability reports?

Triage validation is a rigorous process that applies fixed gate criteria and evidence requirements to security findings, ensuring reproducible and consistent triage outcomes before disclosure to bug bounty programs.

How do I prevent submitting duplicate or invalid bug bounty disclosures?

To prevent duplicate or invalid bug bounty disclosures, apply standardized checklists and deduplication steps during triage to confirm each finding meets required reporting standards and supporting documentation.

What checks are required for bug bounty reproducibility and evidence?

Bug bounty reproducibility and evidence checks are enforced through 4 pre-submission gates that verify required criteria including scope, impact, reproducibility, and supporting evidence before a finding is reported.

Can I automate triage gates for security research findings?

Automating triage gates for security research findings is supported by codifying the 7-question gate, pre-submission criteria, and evidence templates into reproducible steps, enabling consistent validation outcomes across programs.

What are the limitations of using standardized triage gates for vulnerability reporting?

Standardized triage gates for vulnerability reporting enforce strict criteria that may disqualify edge-case findings, requiring all 7 gate questions and 4 pre-submission checks to pass before submission is permitted.