Individual skill

reporting-bug-bounty-writeup

Turn a confirmed finding into a triage-friendly bug-bounty report (HackerOne/Bugcrowd) with correct severity and clean evidence. Load when a bug is validated and needs submitting, on "write the report", "CVSS", "severity", or before disclosure. Signals: a reproduced finding, a program's VRT/severity policy.

skills/reporting/reporting-bug-bounty-writeup/SKILL.md

Read pinned source

Source commit ee0e0c50d2f6d941a14b73dd85a2b470d0ab976e

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 27
Repository last updated: Oct 14, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agent-skills Repository topic
ai-agents Repository topic
ai-security Repository topic
application-security Repository topic
blue-team Repository topic
bug-bounty Repository topic
claude-code Repository topic
codex Repository topic
detection-engineering Repository topic
gemini Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 2,570 bytes

Read excerpt


# Bug-bounty report & severity

## When it governs
After you've *reproduced* a finding and confirmed it's in scope. A great report gets triaged
fast and paid fairly; a sloppy one gets closed as informational regardless of the bug.

## Structure (what triagers want)
1. **Title** — `[Vuln class] on <asset> allows <impact>` (specific, no hype).
2. **Summary** — 2–3 sentences: what, where, why it matters.
3. **Severity** — CVSS 3.1 vector + score, reconciled with the program's VRT/policy. Justify the
   Impact metrics from *demonstrated* impact, not theoretical maximum.
4. **Steps to reproduce** — numbered, copy-pasteable, from a clean session. Include exact
   requests (method, URL, headers, body) and account roles used.
5. **Proof** — minimal PoC that proves impact (a screenshot with the URL bar, a request/response