What problem does it solve? Security researchers often lose payouts because their vulnerability reports are vague, theoretical, or formatted wrong for the platform. This Skill turns a validated finding into a submission-ready report that triagers can act on quickly. ## Core Features & Use Cases - Platform-Specific Templates: Provides ready-to-use report structures for HackerOne, Bugcrowd, Intigriti, and Immunefi, including VRT mapping and severity-request paragraphs. - CVSS Scoring & Severity Guidance: Includes CVSS 3.1 and CVSS 4.0 quick-scoring tables, typical scores by bug class, and a severity decision guide from Critical to Low. - Tone & Quality Controls: Enforces impact-first writing, a title formula, downgrade counters for triager pushback, and a 60-second pre-submit checklist that bans theoretical language like "could potentially". - Use Case: After confirming an IDOR on /api/users/{id}/orders with two test accounts, use this Skill to produce a HackerOne report with exact HTTP requests, a CVSS 6.5 vector string, quantified impact, and a concrete remediation snippet. ## Quick Start Write a HackerOne report for my validated IDOR finding on the orders endpoint using the report-writing skill.
