Skip to content

meltedinhex/analyst-ai-pack / skills/writing-a-malware-analysis-report

writing-a-malware-analysis-report

Verified

Structures a clear, actionable malware analysis report covering summary, sample identity, capabilities, IOCs, ATT&CK mapping, and detection guidance for both technical and decision-making audiences. Activates for requests to write, structure, or review a malware analysis or reverse-engineering report.

FileKindSize
LICENSEother340 B
SKILL.mdskill md4.0 KB
references/api-reference.mdmarkdown1.2 KB
scripts/analyst.pyscript3.0 KB

references/api-reference.md

View on GitHub
# API Reference: Writing a Malware Analysis Report

## Overview

`scripts/analyst.py` generates a structured Markdown report skeleton and checks a draft for the
required sections, presence of ATT&CK technique IDs, and accidental clickable URLs.

## Dependencies

| Package | Version | Purpose |
|---------|---------|---------|
| (stdlib) | — | Templating, regex, file IO |

## Core functions

### `scaffold(sha256, name)`
Returns a complete Markdown report template with the standard section order and example
tables for identity, capabilities, IOCs, and detection.

### `check(text)`
Returns a list of completeness problems: missing required sections, no ATT&CK IDs, or
clickable URLs that should be defanged.

## Usage

```bash
python scripts/analyst.py scaffold --sha256 <sha256> --name "Sample" > report.md
python scripts/analyst.py check report.md
```

## Sources

- MITRE ATT&CK technique catalog — https://attack.mitre.org/
- MISP core format and STIX 2.1 for structured IOC representation —
  https://www.misp-project.org/
- Common DFIR reporting structure (executive summary → identity → capabilities → IOCs →
  detection), standard practice across CERT/IR teams
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall