📝
WritingPython

Bug Bounty Report Writing

by shuvonsec

Bug Bounty Report Writing is a Writing skill for Claude Code, published by shuvonsec in claude-bug-bounty.

4.2K stars767 forkson shuvonsec/claude-bug-bountyAdded 2026/08/16+1% in starsRepository updated 2026/08/10
ai-securitybug-bountybugcrowdclaude-aiclaude-codectiethical-hackinghackeronehackinghacking-toolpenetration-testingreconvulnerability-scanner
Install in seconds
Install Bug Bounty Report Writing
Copy Bug Bounty Report Writing into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.
terminal
npx degit https://github.com/shuvonsec/claude-bug-bounty/tree/main/skills/report-writing ~/.claude/skills/report-writing

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/shuvonsec/claude-bug-bounty.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file
skills/report-writing/SKILL.md in shuvonsec/claude-bug-bounty
Installs to
~/.claude/skills/report-writing
Collection
One of 16 skills cataloged from this repository
Category
Writing1012 skills

What Bug Bounty Report Writing does

Bug Bounty Report Writing provides templates, tone guidelines, CVSS scoring, and checklists for writing bug bounty reports for HackerOne, Bugcrowd, Intigriti, and Immunefi. Use it after validating a finding and before submitting.

Bug Bounty Report Writing is cataloged under Writing on DirSkills. Bug Bounty Report Writing comes from a repository tagged ai-security, bug-bounty, bugcrowd, claude-ai and claude-code.

Documentation

README

REPORT WRITING

Impact-first. Human tone. No theoretical language. Triagers are people.


THE MOST IMPORTANT RULE

Never use "could potentially" or "could be used to" or "may allow". Either it does the thing or it doesn't. If you haven't proved it, don't claim it.

BAD:  "This vulnerability could potentially allow an attacker to access user data."
GOOD: "An attacker can access any user's order history by changing the user_id
       parameter to the target user's ID. I confirmed this using two test accounts:
       attacker@test.com (ID 123) successfully retrieved victim@test.com (ID 456)
       orders, including their shipping address and payment method last 4 digits."

PERSISTENCE RULE

This is the opening of the README. Read the full README on GitHub.

Commands Bug Bounty Report Writing provides

Slash commands named in this skill’s SKILL.md, listed in the order they first appear.

  • /endpoint

Frequently asked about Bug Bounty Report Writing

  • What else does shuvonsec publish alongside Bug Bounty Report Writing?

    Bug Bounty Report Writing is one of 16 skills that DirSkills catalogs from shuvonsec/claude-bug-bounty, the repository it ships in. Its siblings there include Argus, Bug Bounty and Bug Bounty. Each one is a separate skill with its own page in this directory, installs the same way Bug Bounty Report Writing does, and is maintained by shuvonsec in that same repository. The rest of the collection is listed on the shuvonsec/claude-bug-bounty page.

  • How does Bug Bounty Report Writing compare to other Writing skills?

    Bug Bounty Report Writing ranks #166 by stars among the 1012 Writing skills in this catalog. The most-starred ones next to it are Article Writing, Social Media Content Calendar and Knowledge Comic Creator. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Bug Bounty Report Writing against them. Open each page to compare what they document and how they install.

More from shuvonsec/claude-bug-bounty

Bug Bounty Report Writing is one of 16 skills cataloged on DirSkills from shuvonsec/claude-bug-bounty.

See all 16 skills
🔍
2w ago

Argus

Argus runs six automated scanners for web and LLM vulnerabilities: CORS misconfig, CRLF/host-header injection, NoSQL injection, JWT attacks, blind bug confirmation via OOB, and LLM red-teaming. Use it on JSON APIs, login endpoints, JWT auth, or any parameter that might reach the server.
Automation
4.2K767
🐞
2w ago

Bug Bounty

Bug Bounty guides a complete bug bounty workflow from reconnaissance and vulnerability hunting through validation and report writing, including LLM/AI security testing and A-to-B bug chaining. Use it for any bug bounty task, from starting a new target to writing the final submission.
Quality
4.2K767
🐞
2w ago

Bug Bounty

Bug Bounty provides a complete bug bounty workflow covering reconnaissance, vulnerability hunting, AI/LLM security testing, bug chaining, and report writing. Use it for starting new targets, hunting specific vuln classes, auditing source code, validating findings, or writing reports.
Quality
4.2K767
🎯
2w ago

Bug Bounty Methodology

Bug Bounty Methodology structures a hunting session around a five-phase workflow and a critical-thinking framework, so an agent can choose a goal, select techniques, and derive next actions. Use it at the start of a bug bounty session, when switching targets, or when unsure what to do next.
Quality
4.2K767
🛡️
2w ago

CI/CD Security

CI/CD Security audits CI/CD pipelines for workflow injection, secret exfiltration, self-hosted runner poisoning, OIDC token theft, and supply chain attacks. Use it when a target has public repos or CI/CD infrastructure.
DevOps
4.2K767
🔓
2w ago

Client Reverse

Client Reverse helps bug bounty hunters recover client-side request-signing and anti-bot token logic so they can replay protected API requests outside the browser. Use it when Burp or mitmproxy replay fails with 401/403 and you need to isolate the signer before hunting IDOR or auth issues.
Automation
4.2K767