redteam-report-template

Generate a markdown red-team report template with six-section findings and severity fields.

1|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/jellaharshith/SWIFT --skill redteam-report-template-jellaharshith
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: redteam-report-template
Source: https://github.com/jellaharshith/SWIFT/tree/main/swift/skills/cbh/skills/redteam-report-template
Command: npx skills add https://github.com/jellaharshith/SWIFT --skill redteam-report-template-jellaharshith

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of producing consistent, client-ready external red-team deliverables with a clear, evidence-backed structure that different stakeholders can understand.

Core Features & Use Cases

  • Canonical 6-section finding template: Subject, Observations, Description, Impact, Recommendation, and Proof of Concept in a repeatable format.
  • Client-facing severity and red-team status discipline: Uses business-oriented severity plus red-team statuses like Confirmed and Suspected (1 signal) to avoid ambiguity.
  • DOCX/PDF-ready packaging workflow: Supports a markdown-to-DOCX pipeline designed to embed screenshots and produce final reports that match enterprise engagement expectations.

Quick Start

Use the redteam-report-template skill to structure your findings into the required 6-section format for an external enterprise client deliverable, then render the final report into DOCX/PDF with embedded screenshots.

Frequently Asked Questions about redteam-report-template

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

FAQPage Schema
What is the standard structure for an enterprise red-team report finding?

To format red-team report findings, use a 6-section structure: Subject, Observations, Description, Impact, Recommendation, and Proof of Concept. This deterministic, markdown-first template provides disciplined severity and status fields for client-facing deliverables.

How do I package markdown security documentation into a client-ready DOCX file?

You package markdown security documentation into a DOCX file using a markdown-to-DOCX pipeline designed for external red-team engagements. This workflow embeds screenshots and produces final reports matching enterprise client expectations.

What severity and status fields should I use for external red-team documentation?

For external red-team documentation, use business-oriented severity alongside red-team statuses like Confirmed and Suspected. This disciplined approach avoids ambiguity and ensures clear communication across technical and non-technical stakeholders.

Can I use this red-team finding template for both technical and non-technical stakeholders?

Yes, you can use this red-team finding template for both technical and non-technical stakeholders. The Subject/Observations/Description/Impact/Recommendation/PoC format clearly communicates evidence, impact, and remediation across diverse audiences.

Does the red-team report template support inserting proof of concept evidence?

Yes, the red-team report template supports inserting proof of concept evidence. It includes a dedicated PoC section and a DOCX-ready packaging workflow designed specifically for embedding screenshots into the final security documentation.