redteam-report-template

Convert markdown red-team findings into DOCX reports with Pandoc.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pandoc, python-docx, and includes references (resource) components.

What problem does it solve?

This skill solves the inconsistency and lack of professional rigor in red-team reporting by providing a standardized, client-ready framework that bridges the gap between technical findings and business-level impact.

Core Features & Use Cases

  • Standardized Finding Structure: Enforces a 6-section format (Subject, Observations, Description, Impact, Recommendation, PoC) to ensure clarity for both technical and non-technical stakeholders.
  • Professional Deliverable Generation: Automates the conversion of markdown findings into polished DOCX/PDF reports using Pandoc.
  • Use Case: Use this when finalizing an external red-team engagement for an enterprise client to ensure all findings are severity-ordered, evidence-backed, and aligned with CISO-level expectations.

Quick Start

Use the redteam-report-template skill to convert the final markdown report into a formatted docx document with all embedded screenshots.

Frequently Asked Questions about redteam-report-template

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

FAQPage Schema
How do I automate red-team report generation from markdown findings?

Standardizing red-team reporting requires a structured 6-section format (Subject, Observations, Description, Impact, Recommendation, PoC) to bridge technical vulnerabilities and business impact for non-technical stakeholders.

How do I structure a pentest report for enterprise clients?

To format a red-team report into a DOCX document, you need Pandoc to handle the markdown conversion and python-docx to generate the formatted document with all embedded screenshots and structured findings.

What is the best way to format red-team findings for CISO-level review?

Before generating a report, you must install Pandoc and python-docx, and prepare your final markdown report with embedded screenshots and structured findings to ensure successful conversion into a formatted DOCX deliverable.

Do I need Pandoc to convert markdown security reports into DOCX?

You can use this reporting approach for enterprise-level security assessments and external red-team engagements where clear communication of technical vulnerabilities and business risks to stakeholders is required.

Can I use this reporting framework for internal penetration testing engagements?

This approach is ideal for finalizing external red-team engagements for enterprise clients, ensuring standardized, client-ready deliverables that bridge the gap between technical findings and business-level impact.