What problem does it solve? Security researchers often lose payouts because their vulnerability reports are vague, theoretical, or formatted for the wrong platform, causing triagers to downgrade or dismiss valid findings. ## Core Features & Use Cases - Platform-Specific Templates: Provides ready-to-use report structures for HackerOne, Bugcrowd, Intigriti, and Immunefi, each matching that platform's triager expectations and severity mechanisms. - Severity & CVSS Guidance: Includes CVSS 3.1 and 4.0 quick scoring tables, a severity decision guide, and downgrade counters to defend your severity claim against triager pushback. - Impact-First Writing Rules: Enforces a title formula, proven-impact-only language (no "could potentially"), and a 60-second pre-submit checklist. - Use Case: After validating an IDOR finding on a target's API, use this Skill to produce a Bugcrowd report with the correct VRT category, a copy-paste-ready HTTP request, a CVSS vector string, and a severity-request paragraph. ## Quick Start Write a HackerOne report for my validated IDOR finding on the /api/users/{id}/orders endpoint using two test accounts.