Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
securityskills/bug-bounty-report-writingReporting and compliance

bug-bounty-report-writing

⁨Write bug bounty reports that get triaged quickly and rated accurately — clear impact statements, minimal reproduction steps, and professional tone. Use before submitting any vulnerability report.⁩

v2026.8.26-b2b6b523 installs+3 in 7 days0 Starssynced 19 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install securityskills/bug-bounty-report-writing

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
f0s0KcySBm…4fKH9WAg==The CLI checks the SHA-256 and the signature before it writes a file.
Package4b1b27c9…fd0d15ae
4b1b27c9575f…0a5ffd0d15ae1 file · ⁦1.1 KB⁩
ScanMedium1 finding
  • No license found
See the full scan
Sourcegithub.com/securityskills/skills/tree/main/bug-bounty/bug-bounty-report-writing@b2b6b52

Turn findings into reports that triagers accept quickly and rate fairly.

Report Structure

  1. Title — vulnerability class + affected asset. Stored XSS in ticket comment field on support.example.com
  2. Severity & CVSS — your suggested rating with vector string
  3. Summary — 2–3 sentences: what, where, impact
  4. Steps to Reproduce — numbered, copy-pasteable, no assumptions
  5. Impact — what an attacker gains, concretely
  6. Supporting Material — HTTP requests/responses, screenshots with sensitive data redacted
  7. Remediation — specific fix recommendation

Rules

  • One vulnerability per report. Chains go in one report only when each step is meaningless alone.
  • Impact must be demonstrated or rigorously argued, not speculated. "Could lead to RCE" without a path gets downgraded.
  • Redact personal data in evidence. Blur user PII; never include other users' data you accessed — report the access, delete the data.
  • No markdown-breaking formatting in pasted logs; use fenced code blocks.
  • Write for a triager seeing the asset for the first time.

Common Downgrade Causes to Avoid

  • Self-XSS or XSS requiring victim-installed software presented as high severity
  • Missing Content-Security-Policy or verbose headers with no demonstrated exploit
  • Theoretical IDOR without showing two distinct accounts affected
  • Automated scanner output pasted without manual verification

After Submission

  • Respond to triager questions within the program's SLA
  • Request re-review only after substantive new information
  • Do not disclose publicly until the program's disclosure policy allows

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsNoNo
Uses the networkNoNo
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. MediumLicense · No license found

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.8.26-b2b6b52Nov 13, 2026b2b6b524b1b27c9Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login