redteam-report-template

Generate client-facing red-team reports with a six-section finding structure.

13|2|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/chatbotkit/rook --skill redteam-report-template-chatbotkit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: redteam-report-template
Source: https://github.com/chatbotkit/rook/tree/main/skills/redteam-report-template
Command: npx skills add https://github.com/chatbotkit/rook --skill redteam-report-template-chatbotkit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Client-facing red-team deliverable format codifies the Subject / Observations / Description / Impact / Recommendation / PoC structure used for external red-team engagements (not bug-bounty platform reports). Different audience, different tone, different cadence. Built from an authorized engagement deliverable where 14 findings were packaged into a 52KB MD + 2.2MB DOCX with 16 embedded screenshots. Use when the engagement is "external red team for an enterprise client" (not H1/Bugcrowd/Intigriti), when generating the final report, when the client has specified a file format, or when packaging findings into DOCX/PDF.

Core Features & Use Cases

This skill provides a canonical template that standardizes the structure, formatting, and terminology of red-team deliverables across external engagements, enabling consistent client communications and handoffs.

Quick Start

Generate a client-facing red-team report skeleton that enforces the Subject / Observations / Description / Impact / Recommendation / PoC structure for external enterprise engagements.

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 red-team pentest report for an external enterprise client?

Package red-team findings into final deliverables by enforcing the Subject, Observations, Description, Impact, Recommendation, and PoC structure. This format standardizes client-facing reports for external enterprise engagements delivered in DOCX or PDF formats.

What is the difference between a red-team engagement report and a bug-bounty platform report?

Red-team engagement reports target enterprise clients with consistent tone, formatting, and a six-section structure per finding, whereas bug-bounty platform reports differ in audience, tone, and cadence. This template is built strictly for external enterprise red-team deliverables.

Can I generate a DOCX deliverable with embedded screenshots for a pentest report?

Yes, you can generate DOCX deliverables with embedded screenshots for pentest reports. The template supports final report packaging in DOCX and PDF formats, accommodating client-specified file formats and reproducible proof-of-concept structures.

How do I enforce consistent severity statuses across multiple red-team findings?

Enforce consistent severity statuses across red-team findings by applying a canonical template that supports predefined severity statuses. This ensures uniform terminology and structure across all findings in the final client-facing deliverable.

When should I use a standardized report template for an enterprise red-team engagement?

Use a standardized report template when the engagement is an external red-team operation for an enterprise client, when generating the final report, or when the client has specified a file format requiring DOCX or PDF packaging.