skills.rest
SnailSploit
SnailSploitCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

offensive-reporting

Writes penetration test reports with CVSS scoring, evidence handling, and executive summaries.

3.0k|491|Updated Mar 4, 2026
Search Tags:#penetration testing#executive summary#report writing#Red Team#evidence handling#CVSS scoring#Security assessment
One-click install
npx skills add https://github.com/SnailSploit/Claude-Red --skill offensive-reporting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: offensive-reporting
Source: https://github.com/SnailSploit/Claude-Red/tree/main/Skills/utility/offensive-reporting
Command: npx skills add https://github.com/SnailSploit/Claude-Red --skill offensive-reporting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Penetration testers and red team operators often produce technically strong findings that get lost in poorly structured reports, leading to misunderstood risk, unactionable remediation, and wasted engagement value. This Skill provides a complete methodology for authoring professional security assessment deliverables that executives can read and developers can act on.

Core Features & Use Cases

  • Structured Report Authoring: Standard report skeleton covering executive summary, engagement overview, risk summary heatmap, technical findings, attack chain narratives, strategic recommendations, and appendices.
  • Severity Scoring Discipline: CVSS v3.1/v4.0 vector justification, OWASP risk rating, business impact adjustments, and a reference table of typical vectors for common vulnerability classes.
  • Evidence Hygiene & Chain of Custody: Timestamped evidence logging, credential redaction, PII hashing, EXIF stripping, encrypted storage, and retest/closeout tracking.
  • Use Case: At the end of a web application penetration test, use this Skill to convert raw findings into a client-ready report with an executive summary written for non-technical readers, per-finding reproduction steps, and a JSON export for the client's DefectDojo instance.

Quick Start

Ask Claude to draft a penetration test finding for a critical SQL injection vulnerability including CVSS 3.1 scoring, reproduction steps, impact, and remediation.

Frequently Asked Questions about offensive-reporting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a penetration test report executive summary?▼

Write the executive summary last, keeping it to one page with engagement context, the headline finding in business terms, an overall risk verdict, finding counts by severity, and three strategic recommendations. Avoid technical jargon like RCE or XSS and translate everything into business impact language.

How do I score a vulnerability with CVSS 3.1?▼

Build the vector metric by metric (AV, AC, PR, UI, S, C, I, A) and justify each choice in one sentence, then sanity-check the score against business impact. For example, unauthenticated remote code execution typically scores 9.8 Critical with vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

What should a penetration test finding include?▼

Each finding needs a title, severity with CVSS vector, affected scope, CWE/OWASP mapping, summary, root-cause description, numbered reproduction steps, evidence references, quantified impact, specific remediation steps, references, and retest verification notes.

How do I handle evidence and screenshots in a pentest report?▼

Log every action with UTC timestamp, source IP, target, and result hash in an evidence CSV. Before delivery, redact credentials, hash extracted PII, crop screenshots, strip EXIF metadata with exiftool, and store everything on encrypted volumes with a defined retention period.

What is the difference between a pentest report and a bug bounty report?▼

Bug bounty reports target time-pressured triagers, so they need a title with bug class and endpoint, a single curl reproduction command, and impact anchored to the program's threat model. Pentest reports are formal deliverables with executive summaries, scope documentation, and strategic recommendations.

When should I use CVSS v4.0 instead of v3.1?▼

Use CVSS v4.0 when the client mandates it, such as PCI DSS 4.0-aligned engagements, since it adds environmental and threat metrics. Otherwise v3.1 remains the common standard, and OWASP risk rating is an alternative for web-only engagements.

Related Skills

Explore More Content & Communication Skills→
habrahgithubhabrahgithub

penetration-testing

Perform authorized penetration testing on applications, APIs, and network services.

Community
Advanced
DCx7C5DCx7C5

defectdojo-SKILL.md

Automate DefectDojo vulnerability dashboard provisioning via the REST API.

Community
Advanced
vanducngvanducng
5

plan-audit

Audit vd:plan outputs against the codebase and stated goals.

Community
Advanced
n4igmen4igme

bug-bounty

Automate end-to-end bug bounty workflows across recon, hunting, validation, and reporting.

Community
Advanced