Menu

Individual skill

reporting-security-findings

0upvotes

Write security findings and assessment reports — severity scoring with CVSS and business impact, reproducible proof of concept, remediation guidance, executive summaries, and coordinated disclosure. Use when writing up a vulnerability, producing a pentest or audit report, triaging a bug bounty submission, or preparing a disclosure timeline.

secskills-core/skills/reporting-security-findings/SKILL.md

Read pinned source

Source commit ca53957bcd8e3b83b5d4d190bb3ad008a4f15c84

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 11, 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)
191
Repository last updated
Sep 4, 2026
License
MIT

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

Files and excerpt

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

Browse files
Read excerpt

# Reporting Security Findings

The report is the product. Findings that are not understood are not fixed, and
findings that cannot be reproduced are disputed. Most of the value an
assessment creates is destroyed or preserved in the write-up.

## When to Use

- Writing up a single vulnerability
- Producing a penetration test, code audit, or red team report
- Submitting to a bug bounty program or triaging inbound submissions
- Scoring severity and arguing priority with an engineering team
- Planning coordinated disclosure for an unpatched issue
Back to top