What problem does it solve? Bugcrowd submissions often get auto-closed or downgraded because researchers pick the wrong VRT category, accept an underrated default severity, or fail to rebut out-of-scope clauses. This Skill provides the program-specific tactics needed to file Bugcrowd reports that survive triage. ## Core Features & Use Cases - VRT Search & Fallback Strategy: Ordered search hierarchy for the VRT dropdown, common finding-to-category mappings, and guidance for writing a VRT mapping note when no exact node exists. - Manual Severity Override: Instructions for setting Technical Severity independently of the VRT default, plus a severity-request paragraph template placed first in the report body. - OOS-Clause Rebuttal Templates: Ready-made in-scope justification sections for rate-limiting, debug-info, user-enumeration, and theoretical-issue objections. - Chained Findings & Submission Order: Cross-reference templates for multi-report chains, QA-vs-production target selection, and researcher hygiene (Bugcrowdninja alias, account restoration, session rotation). - Use Case: You found a password-verification endpoint with no rate limiting on a Bugcrowd program. Use this Skill to map it to the right VRT node, override the P4 default to P3 with a severity-request paragraph, and pre-empt the "non-authentication endpoint" OOS clause. ## Quick Start Help me file a Bugcrowd submission for a no-rate-limiting finding on a login endpoint, including the right VRT category and a severity-request paragraph.
