redteam-report-template

Generate client-facing red-team deliverables using a six-section template.

Updated Jun 23, 2024
One-click install
npx skills add https://github.com/n4igme/randscript --skill redteam-report-template-n4igme
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: redteam-report-template
Source: https://github.com/n4igme/randscript/tree/main/llm/skills/claude-hunter/skills/redteam-report-template
Command: npx skills add https://github.com/n4igme/randscript --skill redteam-report-template-n4igme

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a standardized blueprint for producing client-facing red-team deliverables, codifying the Subject / Observations / Description / Impact / Recommendation / PoC structure and enabling consistent quality across engagements.

Core Features & Use Cases

  • Standardized red-team report structure (Subject, Observations, Description, Impact, Recommendation, PoC) for external engagements
  • Guidance on formatting, evidence, severity classification, and client-facing language to improve clarity and impact
  • Suitable for enterprise red-team engagements with formal deliverables (MD/DOCX) and evidence packaging

Quick Start

Generate a client-facing red-team deliverable using the canonical six-section template.

Frequently Asked Questions about redteam-report-template

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

FAQPage Schema
How do I structure a client-facing red-team report for an external engagement?

A client-facing red-team report should follow a standardized six-section structure: Subject, Observations, Description, Impact, Recommendation, and PoC. This ensures consistent quality, clear evidence integration, and formal packaging for executive audiences.

What sections should a red-team deliverable include for enterprise clients?

Enterprise red-team deliverables should include Subject, Observations, Description, Impact, Recommendation, and PoC sections. This canonical six-section template enforces consistent structure and client-facing language for formal engagements.

How do I integrate proof-of-concept evidence into a pentest report template?

Integrate proof-of-concept evidence into a pentest report template by mapping it directly into the PoC section of the six-part structure. This ensures technical evidence supports the Observations and Impact sections for client-facing delivery.

Can I use a standardized report template for external red-team engagements?

You can use a standardized report template for external red-team engagements to codify the Subject, Observations, Description, Impact, Recommendation, and PoC structure. This enables consistent quality and clear delivery guidelines across multiple client deliverables.

What is the best way to format severity classifications in a red-team report?

Format severity classifications within the Impact section of the red-team report. Applying the canonical six-section template provides specific guidance on severity classification and client-facing language to improve clarity for executive audiences.