Individual skill

reporting-pentest-report

Structure a professional penetration-test report (engagement deliverable, not a single bug). Load at the end of a pentest, on "write the pentest report", "executive summary", "deliverable", or compiling findings for a client. Signals: engagement wrap-up, multiple findings, client report.

skills/reporting/reporting-pentest-report/SKILL.md

Read pinned source

Source commit ee0e0c50d2f6d941a14b73dd85a2b470d0ab976e

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Instructions only
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): 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
security Derived category
testing 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,469 bytes

Read excerpt


# Penetration-test report

## When it governs
End of a pentest engagement, when findings become a client deliverable. Different from a
bug-bounty report (`reporting-bug-bounty-writeup`): this is the whole engagement — executive
narrative plus detailed findings — read by both executives and engineers.

## Structure
1. **Executive summary** — non-technical: what was tested, overall risk posture, the 3–5 things
   that matter, and business impact. One page. No jargon.
2. **Scope & methodology** — assets/IPs/apps in scope, dates, testing type (black/grey/white),
   standards followed (PTES/OWASP WSTG/NIST), and limitations.
3. **Findings** — one per issue, ordered by risk. Each: title, severity (CVSS vector + rating),
   affected assets, description, **reproduction steps** (exact requests/commands), **evidence**