sc5-report

Compile validated vulnerability findings into a structured bug bounty report.

Updated Jun 23, 2024
One-click install
npx skills add https://github.com/n4igme/randscript --skill sc5-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sc5-report
Source: https://github.com/n4igme/randscript/tree/main/llm/skills/scode/sc5-report
Command: npx skills add https://github.com/n4igme/randscript --skill sc5-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This step consolidates validated vulnerability findings into a professional bug bounty submission report, providing a clear executive summary, detailed findings, and a remediation roadmap.

Core Features & Use Cases

  • Centralizes validated findings into a structured Bug Bounty Report format ready for submission.
  • Maps severities and references to platform rubrics (Immunefi, HackerOne, Bugcrowd) and includes CVSS scoring, CWE references, business impact, and remediation prioritization.
  • Outputs the final document to ./assessment/bug-bounty-report.md and coordinates with supporting context from recon.md and threat-model.md.

Quick Start

Run sc5-report with your validated-vulnerabilities.md to generate the bug bounty report.

Frequently Asked Questions about sc5-report

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

FAQPage Schema
How do I generate a bug bounty report from validated vulnerability findings?

To generate a bug bounty report, provide your validated-vulnerabilities.md file. The system compiles the findings into a structured document with an executive summary, detailed technical evidence, and a remediation roadmap.

What is the best way to format CVSS scores and CWE references for a HackerOne or Immunefi submission?

Formatting CVSS scores and CWE references for submission platforms requires mapping severities to platform rubrics. The report automatically structures these metrics alongside business impact to meet standard bug bounty requirements.

How do I create an executive summary and remediation roadmap for validated vulnerabilities?

Creating an executive summary and remediation roadmap involves consolidating static vulnerability data with supporting context. The output provides clear business impact analysis and prioritized remediation steps suitable for executive review.

Do I need recon and threat model data to compile a comprehensive vulnerability report?

You do not strictly need recon and threat model data, but the system coordinates with recon.md and threat-model.md files. Including this supporting context enriches the vulnerability findings and improves the overall remediation planning quality.

Can I use static vulnerability data to produce a report ready for executive review?

Yes, you can use static vulnerability data to produce an executive-ready report. The process applies to validated-vulnerabilities.md files, transforming them into a polished document with structured remediation planning and business impact analysis.

What limitations exist when automating bug bounty report generation from raw vulnerability data?

A key limitation is that the report relies on pre-validated static vulnerability data. It does not perform dynamic scanning or initial vulnerability discovery, meaning raw, unvalidated findings will not produce an accurate CVSS-scored submission.