bugbounty-reporter

Create and submit bug bounty reports with structured sections.

30|6|Updated May 13, 2026
One-click install
npx skills add https://github.com/Rifteo/skills --skill bugbounty-reporter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bugbounty-reporter
Source: https://github.com/Rifteo/skills/tree/main/bugbounty-reporter
Command: npx skills add https://github.com/Rifteo/skills --skill bugbounty-reporter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill eliminates the challenges of writing clear, actionable bug bounty reports by providing a structured process that guides users through every step of the bug reporting lifecycle.

Core Features & Use Cases

  • Structured Reporting: Guides users through creating complete, triage-ready reports.
  • Pre-Submission Triage: Helps identify reportable issues and avoid duplicates.
  • Template-based Reporting: Utilizes standardized templates for consistency and clarity.
  • Use Case: A bug bounty hunter can use this Skill to format and submit a detailed report on a confirmed IDOR vulnerability in a web application.

Quick Start

Run the bugbounty-reporter skill and follow the prompts to enter your bug details for a formatted report.

Frequently Asked Questions about bugbounty-reporter

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

FAQPage Schema
How do I write a structured bug bounty report for a vulnerability submission?

To write a structured bug bounty report, you need to parse your findings, conduct pre-submission triage to identify reportable issues, and format the vulnerability details into standardized markdown sections for a clear, actionable submission.

What is pre-submission triage in pentest reporting?

Pre-submission triage in pentest reporting is the process of reviewing identified security issues before submission to identify valid reportable vulnerabilities and avoid duplicates, ensuring your bug bounty reports are triage-ready.

How do I format and submit an IDOR vulnerability report?

You format and submit an IDOR vulnerability report by entering your confirmed bug details into a structured methodology that uses standardized templates, outputting a detailed markdown report with all required sections for the bounty program.

Do I need YAML and markdown to create bug bounty reports?

Yes, you need YAML for configuration and markdown for report formatting when using automated reporting methodologies to generate structured, triage-ready bug bounty submissions for security researchers.

Can I use this structured reporting methodology for web application security findings?

Yes, you can use this structured reporting methodology for web application security findings, as it is designed for bug bounty hunters to guide the creation of detailed reports on vulnerabilities like IDOR.

What is the best way to avoid duplicate bug bounty submissions?

The best way to avoid duplicate bug bounty submissions is to conduct pre-submission triage, which helps identify reportable issues and filter out duplicates before you format and submit the final vulnerability report.