byelementalsouls· 56 skills
Bugcrowd-specific reporting tactics complementing report-writing: VRT category search-and-fallback strategy when no exact match exists, manual severity override when VRT defaults underrate impact, severity-request paragraph as first body section, OOS-clause rebuttal templates (rate limiting on auth-flow endpoints, debug-info framing, user-enumeration with sensitive PII, theoretical-issue counter), chained-finding cross-reference patterns, target selection for QA-vs-prod programs, researcher-side hygiene (Bugcrowdninja email alias, account state restoration, friendly-tester posture). Use when filing a Bugcrowd submission, when VRT default seems wrong, when triager closes as OOS or downgrades severity, when chaining linked submissions, or when scope distinguishes production from QA. Pairs with report-writing and triage-validation.
$npx -y skills add elementalsouls/claude-bughunter --skill bugcrowd-reportingInstalls into the current project.
Run `npx skills use "https://github.com/elementalsouls/claude-bughunter" --skill "elementalsouls/claude-bughunter/bugcrowd-reporting"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/elementalsouls/claude-bughunter" that are relevant to the current task. Run `npx skills add "https://github.com/elementalsouls/claude-bughunter"` and select the relevant skills, then follow their instructions.