What problem does it solve? Bugcrowd submissions often get auto-closed or downgraded because the VRT category defaults to a low severity, triagers map findings to out-of-scope clauses, or chained findings are filed without clear cross-references. This Skill provides the program-specific tactics to file Bugcrowd reports that survive triage. ## Core Features & Use Cases - VRT Search-and-Fallback Strategy: Ordered search hierarchy for picking the most accurate VRT node, with common mappings for IDOR, ATO, rate-limiting, and GraphQL findings, plus a fallback plan when no exact VRT exists. - Manual Severity Override & Severity-Request Paragraph: Instructions for overriding the VRT default in the form and leading the report body with a severity-request paragraph that cites the program's Focus Areas. - OOS-Clause Rebuttal Templates: Ready-made in-scope justification sections for rate-limiting, debug-info, user-enumeration, and theoretical-issue objections. - Use Case: You found a password-verification oracle with no rate limiting on a Bugcrowd program. Use this Skill to pick the right VRT, override the P4 default to P3 with a severity-request paragraph, rebut the "non-authentication endpoint" OOS clause, and cross-reference the chained ATO report. ## Quick Start Help me file a Bugcrowd submission for my finding, including the right VRT category, a severity-request paragraph, and rebuttals to likely out-of-scope objections.
