strike-report

Convert vulnerability findings into structured bug bounty reports with CVSS 3.1 scoring.

1|Updated Apr 3, 2026

Search Tags:#vulnerability #triage #cvss #report-writing #bug-bounty #hackerone #intigriti

Ready to run

npx skills add https://github.com/mlvpatel/sentinel-ai-offensive --skill strike-report

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: strike-report
Source: https://github.com/mlvpatel/sentinel-ai-offensive/tree/main/skills/strike-report
Command: npx skills add https://github.com/mlvpatel/sentinel-ai-offensive --skill strike-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides ready-to-use templates and guidelines to write high-quality bug bounty reports for major platforms (HackerOne, Bugcrowd, Intigriti, Immunefi). It enforces an accurate, impact-first writing style, CVSS 3.1 scoring, and structured pre-submit checks to reduce back-and-forth with triagers.

Core Features & Use Cases

Templates for HackerOne, Bugcrowd, Intigriti, and Immunefi
Impact-first writing style with explicit evidence and reasoning
CVSS 3.1 scoring, title formula, impact statement formula, and severity decision guide
Downgrade counters and pre-submit checklist
Guidance for after validating a finding and before submitting

Quick Start

Generate a complete bug bounty report using the strike-report templates for a validated finding.

Frequently Asked Questions about strike-report

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

FAQPage Schema

How do I write a bug bounty report that reduces back-and-forth with triagers?▼

To write a bug bounty report that minimizes triager pushback, use an impact-first writing style with explicit evidence, structured templates, and a pre-submit checklist to ensure all required details are included before submission.

Does this bug bounty reporting template support HackerOne, Bugcrowd, Intigriti, and Immunefi?▼

Yes, the reporting templates and workflows are explicitly designed to support HackerOne, Bugcrowd, Intigriti, and Immunefi, applying platform-specific formatting and severity guidance across different report types.

How do I calculate CVSS 3.1 scoring for my vulnerability findings?▼

You can calculate CVSS 3.1 scoring for vulnerability findings by applying the integrated scoring guidance, which maps your technical findings to accurate severity ratings and includes downgrade counters to prevent invalid downgrades.

What's the best way to format a vulnerability title and impact statement?▼

The best way to format a vulnerability title and impact statement is to use the provided title and impact statement formulas, ensuring an impact-first writing style that clearly communicates the vulnerability's severity and business risk.

Can I use this skill after validating a finding and before submitting my report?▼

Yes, this skill provides specific guidance for the phase immediately after validating a finding and before submitting, utilizing a pre-submit checklist to verify completeness and accuracy across major bug bounty platforms.