Pentest Reporting
Use when turning security findings into a clear, actionable report — scoring severity with CVSS, writing findings with reproduction and impact, prioritizing remediation, producing an executive summary, and tracking retests to closure. The phase that makes testing matter.
Install
/plugin marketplace add mn-youssef/security-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add mn-youssef/security-skills --skill pentest-reportinggit clone --depth 1 https://github.com/mn-youssef/security-skills.git /tmp/security-skills
mkdir -p ~/.claude/skills
cp -r /tmp/security-skills/skills/pentest-reporting ~/.claude/skills/pentest-reportingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Pentest Reporting (REPORT phase — the end that makes the work count) ## Overview A vulnerability nobody fixes isn't security. This phase converts raw findings into a report that engineers can act on and leaders can prioritize: consistent severity, crisp reproduction, honest impact, concrete fixes, and tracked closure. **Core principle:** Write for two readers at once — an executive who needs *risk and priority*, and an engineer who needs *exact steps to reproduce and fix*. ## Structure of a good report 1. **Executive summary** — plain-language risk posture, top 3–5 risks, overall verdict. No jargon. 2. **Scope & methodology** — what was tested, environment, dates, what was out of scope. 3. **Findings** — one entry each (see template), ordered by severity. 4. **Remediation roadmap** — prioritized fix list with effort estimates. 5. **Retest results** — status per finding after fixes (Open / Fixed / Risk-accepted). 6. **Appendix** — tools, raw evidence, references. ## Finding template (use for every issue)
Details
- Skill name
pentest-reporting- Repository
- mn-youssef/security-skills
- Path
skills/pentest-reporting/SKILL.md- License
- MIT
- Repo updated
- 12 June 2026
FAQ
What does the Pentest Reporting skill do?
Use when turning security findings into a clear, actionable report — scoring severity with CVSS, writing findings with reproduction and impact, prioritizing remediation, producing an executive summary, and tracking retests to closure. The phase that makes testing matter.
How do I install the Pentest Reporting skill?
Claude Code plugin: /plugin marketplace add mn-youssef/security-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Pentest Reporting popular?
It lives in mn-youssef/security-skills, which has 49 GitHub stars and 7 forks.
Related skills
Access Control Testing
49mn-youssef/security-skills
Use when testing whether users can access data or actions they shouldn't — IDOR/BOLA, horizontal and vertical privilege escalation, multi-tenant isolation, forced browsing, function-level authorization (BFLA), and mass assignment. The #1 cause of real-world breaches.
Active Pentest
49mn-youssef/security-skills
Use when you need to actually run security tests against a running application you own or are authorized to test — the shared execution harness for lab/proxy/scanner setup, safe non-destructive execution, and standardized proof-of-concept capture that the find/exploit specialist skills rely on.
API Security Testing
49mn-youssef/security-skills
Use when testing REST, GraphQL, gRPC, or WebSocket APIs against the OWASP API Security Top 10 — object- and function-level authorization (BOLA/BFLA), excessive data exposure, mass assignment, unrestricted resource consumption, and GraphQL-specific abuse. For apps you own or are authorized to test.
Recon and Osint
49mn-youssef/security-skills
Use when starting an assessment and you need to discover an application's full attack surface — subdomains, hosts, endpoints, technologies, exposed services, leaked credentials and secrets — on assets you own or are authorized to test. Feeds the threat model with real, not assumed, targets.
Client Side Exploitation
49mn-youssef/security-skills
Use when testing advanced browser-side and HTTP-layer attacks beyond basic XSS/CSRF — DOM XSS, CSP bypass, CORS misconfiguration exploitation, postMessage abuse, prototype pollution, DOM clobbering, clickjacking, web cache poisoning, and HTTP request smuggling. On apps you own or are authorized to test.
Security Code Audit
49mn-youssef/security-skills
Use when you have application source code and want to find security vulnerabilities by reading it — covers OWASP Top 10 across frontend, backend API, and database. Produces a findings register with severity, file:line, and exploitability.
Browse the most popular Claude skills, all security skills, or write your own with the skills generator.