bugcrowd-reporting is a skill for Claude that covers what is particular to Bugcrowd submissions. It explains how to search the Vulnerability Rating Taxonomy for the most specific accurate category, how to ask for a manual severity change when the default rating underrates impact, and why the severity request belongs in the first paragraph of the report body.
It also holds templates for answering out-of-scope clauses, advice on cross-referencing chained findings, guidance on QA versus production targets, researcher-side hygiene and an order for submitting several findings from one engagement. It complements the general report-writing skill in the same bundle.
What You Get
- A search order for finding the right VRT category and a table of common finding-to-category mappings
- A method for requesting a manual severity override with a short first paragraph
- Rebuttal templates for common out-of-scope clauses
- Advice on linking chained findings filed as separate reports
- Researcher-side hygiene and a submission-order strategy for multi-finding engagements
Common Use Cases
- Filing a Bugcrowd report whose default VRT priority looks too low
- Answering a triager who cites an out-of-scope clause
- Planning the order of several related submissions for one program
What Makes It Unique
It focuses on one platform’s mechanics, such as how the dropdown ties a default priority to each taxonomy node, and it insists on accuracy: pick the most specific true category, then argue severity in the open. Generic report templates for other platforms live in a separate skill.
Under The Hood
The skill is a single SKILL.md of guidance with no bundled scripts. It is a set of reporting tactics, report snippets and tables, so using it means the agent drafts text, and it may write the report to a file in the working folder. The text mentions test-account practices and account-state restoration after testing, and it quotes example report wording. It does not tell the agent to fetch pages or call services itself.