security-writeup

amattas's avatarfrom amattas

Document security research, CTF solutions, and malware analysis. Includes REPORT.md and STATUS.md templates.

⭐0stars🔀0forks📁View on GitHub🕐Updated Dec 26, 2025
[Security Operations]

When & Why to Use This Skill

This Claude skill provides a professional framework for documenting security research, CTF (Capture The Flag) solutions, and malware analysis. By utilizing standardized templates like REPORT.md and STATUS.md, it enables researchers to maintain technical rigor, track progress across complex tasks, and produce high-quality, reproducible security reports that cover everything from binary properties to mitigation strategies.

Use Cases

  • CTF Competition Tracking: Manage multi-problem challenges efficiently by using the STATUS.md template to track progress, document failed attempts, and maintain session continuity.
  • Malware Analysis Documentation: Create detailed technical reports that include binary checksec properties, vulnerability root causes, and step-by-step exploitation analysis.
  • Vulnerability Research & Disclosure: Standardize the documentation of security findings, including payload structures, memory offsets, and specific mitigation recommendations for developers.
  • Security Education and Lab Work: Provide students and researchers with a structured methodology for documenting technical solutions in multi-problem security environments, focusing on the 'why' behind the exploits.
namesecurity-writeup
descriptionDocument security research, CTF solutions, and malware analysis. Includes REPORT.md and STATUS.md templates.

Security Writeup

Documentation standards for security research and CTF challenges.

Document Types

Document Purpose When to Create
STATUS.md Progress tracking Start of work, update throughout
REPORT.md Technical writeup After solution or significant progress

STATUS.md

Track progress for restartability. Update after:

  • Starting work on a problem
  • Finding key information (offsets, addresses)
  • Failed attempts (document what didn't work!)
  • Completing a phase (recon → analysis → exploit → docs)
  • Session end

Status Icons

  • ✅ Solved
  • 🔄 In Progress
  • ❌ Not Started
  • ⏸️ Blocked

REPORT.md

Combine technical writeup with learning explanation.

Required Sections

  1. Overview - Accessible summary
  2. Binary Properties - checksec output as table
  3. Vulnerability - Type, location, root cause
  4. Exploitation - Step-by-step approach
  5. Payload - Structure and key addresses
  6. Flag - The solution
  7. Mitigations - How to prevent

Writing Guidelines

  • Technical enough to reproduce
  • Accessible enough to learn from
  • Include actual addresses and offsets
  • Explain the "why" not just the "what"

Multi-Problem Labs

For CTFs with multiple problems:

lab/
├── STATUS.md           # Overview of ALL problems
├── problem1/
│   ├── STATUS.md       # Detailed for this problem
│   ├── exploit.py
│   └── REPORT.md
└── problem2/
    └── ...

Root STATUS.md tracks overall progress; per-problem STATUS.md tracks details.

Templates

  • templates/REPORT.md - Full technical writeup
  • templates/STATUS.md - Progress tracking