Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Penetration Test Reporting — Professional Methodology · snailsploit | DecimalAI

securityby snailsploit

Penetration Test Reporting — Professional Methodology

snailsploit/offensive-reporting

Source snailsploit/claude-red ↗License MIT

Penetration test and red team report writing methodology. Covers executive summary structuring (risk-led narrative for non-technical readers), technical finding format (title, severity, affected scope, narrative, reproduction steps, impact, remediation, references), CVSS v3.1 / v4.0 scoring with vector justification, OWASP risk rating, evidence hygiene (redacting credentials, hashing client data, time-stamping every action), screenshot and PoC artifact management, finding chain narratives, scope

SkillScore63Maintained

Automatic

Security & AppSec pack

Last verified 8/12/2026

What it changes

Passed 15 of 24 test cases with the skill, and 9 of 24 without it.

Without skill38%

With skill63%

Checks it passed that the model alone missed

Restricts Executive Summary length to one page maximum.
Hashes extracted PII records rather than displaying raw customer data.
Retains only the final report document and an evidence hash manifest post-engagement.

and 6 more in the full report

7 fixed8 passed either way8 still failing1 broke

Pass-rate lift: +25 pp
Tokens: +174%
Agent turns: 0%
Response time: -2%

Model gemini-3.6-flashMeasured 8/12/2026v115 of 24 cases passed with skill

Tokens, turns and time describe resource use, not a dollar price.

Use this skill

Save it into your project's skills folder. Claude Code picks it up in its next session.

curl -fsSL --create-dirs -o .claude/skills/snailsploit-offensive-reporting/SKILL.md https://app.decimal.ai/s/snailsploit-offensive-reporting/SKILL.md

Want it pinned and updatable? pip install "decimalai>=0.15", then decimalai skills add snailsploit-offensive-reporting, and start Claude Code with claude --plugin-dir "$(git rev-parse --show-toplevel)/.agents"

1 · One-time — install the CLI (docs ↗)

pip install "decimalai>=0.15"

2 · Get the skill — writes .agents/skills/snailsploit-offensive-reporting/ and pins it in .decimal/skills.lock

decimalai skills add snailsploit-offensive-reporting

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/snailsploit-offensive-reporting/SKILL.md https://app.decimal.ai/s/snailsploit-offensive-reporting/SKILL.md

Raw file: /s/snailsploit-offensive-reporting/SKILL.md ↗ · machine-readable summary at /s/snailsploit-offensive-reporting.json ↗

Safety checks: 3 of 3 passed

Code scan CleanIntent PassedContent Clean

See it in action

One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.

1 of 7

Prompt

We are drafting the Executive Summary section for an enterprise security review deliverable. What maximum document length constraint should be observed for this section?

What was checked, without and with the skill
Checked	Without skill	With skill
Restricts Executive Summary length to one page maximum.	Missed	Passed

case-17 · gemini-3.6-flash · 8/12/2026 · answers are capped and redacted

What's inside

The instructions your model reads when the skill loads.

SKILL.md366 linessingle file

Penetration Test Reporting — Professional Methodology

A great finding lost in a bad report is a wasted finding. Reports are the artifact the client pays for, the auditor reads, and the developer fixes from. Treat the report with the same rigor as the exploit.

Quick Workflow

Capture evidence as you exploit — never reconstruct after the fact
Draft each finding immediately while context is fresh; one finding = one numbered file
Build the executive summary last, after all findings are scored
Two-pass review: technical accuracy first, then read-as-CISO for narrative
Hand off with a retest plan and a JSON/CSV index for the client's tracking system

Report Structure (Standard)

1. Executive Summary             ← Last to write, first read
2. Engagement Overview
   2.1 Scope
   2.2 Methodology
   2.3 Limitations / Assumptions
   2.4 Timeline
   2.5 Team
3. Risk Summary                  ← Heatmap, finding count by severity
4. Technical Findings            ← One per finding, sorted by severity
5. Attack Narratives / Chains    ← Critical chains called out separately
6. Strategic Recommendations     ← Programmatic, not finding-by-finding
7. Appendices
   A. Tools Used
   B. Indicators of Compromise (for blue team)
   C. Raw Evidence Pointers
   D. Glossary

Executive Summary — The 90-Second Read

The executive summary is for the CISO, the GRC officer, and the board member. They read this and nothing else.

Track record

Benchmark

15 / 24

test cases passed, vs 9 / 24 without

Adoption

Users: 0
Times used: 0

Safety and source details

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v4 — 8/3/2026

View 15 scanner checks

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

snailsploit / claude-red

Skills/utility/offensive-reporting/SKILL.md

View on GitHub ↗

License MITImported 8/3/2026Version v1

More skills from the same source and nearby in the registry, with their headline benchmark lift.

Ready to supercharge your AI agents?

See it in action

What's inside

Penetration Test Reporting — Professional Methodology

Quick Workflow

Report Structure (Standard)

Executive Summary — The 90-Second Read

Track record

Benchmark

Adoption

SkillSafety

Source

Related skills