skills.rest
brukal001
brukal001COMMUNITY
Explore all skills by this author →
GitHub

offensive-reporting

Write penetration test reports with CVSS scoring, evidence hygiene, and executive summaries.

Updated Jun 26, 2026
Search Tags:#penetration testing#executive summary#red team#report writing#remediation tracking#cvss scoring#evidence redaction
One-click install
npx skills add https://github.com/brukal001/brukal --skill offensive-reporting-brukal001
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: offensive-reporting
Source: https://github.com/brukal001/brukal/tree/main/skills/claude-red/utility/offensive-reporting
Command: npx skills add https://github.com/brukal001/brukal --skill offensive-reporting-brukal001

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Penetration testers often produce technically strong findings that get lost in poorly structured reports, leaving clients unable to understand risk, reproduce issues, or prioritize fixes. This Skill provides a complete professional methodology for authoring engagement deliverables that executives can read and developers can act on. ## Core Features & Use Cases - Structured Finding Templates: Standardized format covering severity, affected scope, reproduction steps, impact, remediation, and retest notes, with CVSS v3.1/v4.0 and OWASP risk scoring guidance. - Executive Summary & Risk Communication: Risk-led narrative techniques for non-technical readers, severity heatmaps, attack chain narratives, and strategic programmatic recommendations. - Evidence Hygiene & Deliverables: Timestamped evidence logging, credential redaction rules, chain-of-custody practices, and multi-format output (PDF, DOCX, HTML, JSON for SIEM ingestion) generated from a single Markdown source via Pandoc. - Use Case: At the end of a red team engagement, use this Skill to convert raw findings and evidence logs into a client-ready report with an executive summary, scored findings, and a retest tracking table. ## Quick Start Use the offensive-reporting skill to draft a penetration test report from my engagement findings, including an executive summary, CVSS-scored technical findings, and a retest plan.

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 anchor every finding to business impact.

How to score vulnerabilities with CVSS v3.1 in a pentest report?▼

Score each metric honestly and justify every choice in one sentence, such as AV:N for internet-exposed services. Treat CVSS as a floor rather than a ceiling, and add a business impact adjustment paragraph when context makes a finding more severe than its score suggests.

What should a technical finding template include?▼

A finding should include severity with CVSS vector, affected scope, CWE and OWASP mapping, summary, root-cause description, numbered reproduction steps, evidence references, quantified impact, ordered remediation steps, references, and notes for retest verification.

How do I handle evidence redaction in pentest reports?▼

Replace credentials with placeholders, hash extracted PII, crop screenshots to relevant areas, strip EXIF metadata with exiftool, and verify URLs contain no session tokens. Log every action with UTC timestamps, source IP, target, and result hashes for chain of custody.

What formats should a penetration test report be delivered in?▼

Deliver PDF for executives, DOCX for client editing, HTML for searchable portals, and JSON or CSV for SIEM and GRC tools like DefectDojo or Jira. Generate all formats from a single Markdown source using Pandoc rather than maintaining parallel versions.

How is bug bounty reporting different from client pentest reports?▼

Bug bounty reports target time-pressured triagers, so keep the title under 80 characters with bug class and impact, provide a single curl reproduction command, and anchor impact to the program's threat model. A good bounty report is read in two minutes and reproduced in five.

Related Skills

Explore More Software Engineering Skills→
brucesongsbrucesongs
60

terminal-ops

Capture timestamped, tamper-evident terminal commands with status markers during pentests.

Community
Advanced
braydos-hbraydos-h
4

building-vulnerability-dashboard-with-defectdojo

Deploy DefectDojo to aggregate scanner findings, deduplicate vulnerabilities, and track remediation metrics.

Community
Intermediate
Kisilev13Kisilev13

triage-validation

Validate bug bounty findings using a structured 7-question process.

Community
Advanced
brucesongsbrucesongs
60

pentest-reporting

Integrate Dradis and Faraday to unify evidence and findings into templated reports.

Community
Advanced