Is the Bugcrowd Reporting skill free?

Yes. The skill itself is free from elementalsouls/Claude-BugHunter. SkillProof publishes the install command and an independent test verdict at no cost.

What is the Bugcrowd Reporting SkillProof Score?

8.4/10 — installs cleanly 5/5, triggers reliably 4/5, output vs. baseline 7/10, docs & honesty 5/5.

How do I install Bugcrowd Reporting?

Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.

Can I use Bugcrowd Reporting with Cursor, Copilot, Gemini CLI, Codex or other AI tools?

The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.

Bugcrowd Reporting

Applies Bugcrowd-specific VRT categorization and severity-override reporting tactics.

by elementalsouls · elementalsouls/Claude-BugHunter

Tested · Works

Install — copy the command Download source ↗

Test report

Verdict: Tested · Works
Score: 8.4/10
Tested: Jul 13, 2026
Environment: Claude Code 2.x (agent harness)
Upstream re-checked: Aug 10, 2026 · 961dca8

A responsible-disclosure report-writing skill layering Bugcrowd-specific tactics (VRT category selection, manual severity override, severity-request paragraph, OOS-clause rebuttals) on top of a generic report-writing skill; tested on a fabricated benign reflected-XSS-to-ATO finding with no real program targeted. Verbatim install is clean (single-file SKILL.md, strict-YAML frontmatter, no broken refs) and the frontmatter triggers precisely on Bugcrowd-filing scenarios. In the A/B, the skill arm was clearly better: it opened with the exact literal 'Severity request — please review carefully before applying VRT default' header that pre-empts triager auto-close and followed the skill's severity-request template structure verbatim, while the base arm produced a solid but generic severity argument that missed that recognized-phrase convention.

Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works

Installs cleanly 5/5
Triggers reliably 4/5
Output vs. baseline 7/10
Docs & honesty 5/5

What Bugcrowd Reporting does

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…

How to install Bugcrowd Reporting

git clone https://github.com/elementalsouls/Claude-BugHunter
cd Claude-BugHunter
mkdir -p ~/.claude/skills
cp -r skills/bugcrowd-reporting ~/.claude/skills/bugcrowd-reporting

Skills live in ~/.claude/skills/ (global) or .claude/skills/ (per-project). Restart Claude Code after installing.

Commands — how to trigger Bugcrowd Reporting

/bugcrowd-reporting Applies Bugcrowd-specific VRT categorization and severity-override reporting tactics.

It also activates on plain-language prompts like these:

Write a Bugcrowd report with the right VRT category
Draft a severity-override justification for this finding
Rebut an out-of-scope rejection on this Bugcrowd report

Frequently asked questions

Is the Bugcrowd Reporting skill free?: Yes. The skill itself is free from elementalsouls/Claude-BugHunter. SkillProof publishes the install command and an independent test verdict at no cost.
Does Bugcrowd Reporting work with Claude Code?: We tested it with Claude Code 2.x (agent harness) on Jul 13, 2026. Verdict: Tested · Works. A responsible-disclosure report-writing skill layering Bugcrowd-specific tactics (VRT category selection, manual severity override, severity-request paragraph, OOS-clause rebuttals) on top of a generic report-writing skill; tested on a fabricated benign reflected-XSS-to-ATO finding with no real program targeted. Verbatim install is clean (single-file SKILL.md, strict-YAML frontmatter, no broken refs) and the frontmatter triggers precisely on Bugcrowd-filing scenarios. In the A/B, the skill arm was clearly better: it opened with the exact literal 'Severity request — please review carefully before applying VRT default' header that pre-empts triager auto-close and followed the skill's severity-request template structure verbatim, while the base arm produced a solid but generic severity argument that missed that recognized-phrase convention.
What is the Bugcrowd Reporting SkillProof Score?: 8.4/10 — installs cleanly 5/5, triggers reliably 4/5, output vs. baseline 7/10, docs & honesty 5/5.
How do I install Bugcrowd Reporting?: Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
Can I use Bugcrowd Reporting with Cursor, Copilot, Gemini CLI, Codex or other AI tools?: The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.