Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

complete-investigation

Étoiles2

Forks1

Mis à jour15 mars 2026 à 08:19

Run a full 11-phase forensic investigation across all MCP servers — disk, memory, Windows artifacts, malware, network, OSINT, threat intel, timeline, and reporting.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

valITino

valITino/dfireballz

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en sécurité de l'informationProfessions informatiques et mathématiques·SOC 15-1212

SKILL.md

readonly

name	complete-investigation
description	Run a full 11-phase forensic investigation across all MCP servers — disk, memory, Windows artifacts, malware, network, OSINT, threat intel, timeline, and reporting.

Run the complete forensic investigation workflow against the specified target.

Usage: /complete-investigation <target>

Where <target> is the evidence path or subject — e.g. /evidence/disk.dd, /evidence/memdump.raw, suspicious-domain.com.

If no target is provided, ask the user what they want to investigate.

Instructions

Load the investigation template: call get_template(name="complete-investigation", target="$ARGUMENTS")
Follow all 11 phases in order — do NOT skip any phase
Use the MCP servers and their tools for every phase (kali-forensics, winforensics, osint, threat-intel, binary-analysis, network-forensics, filesystem)
Log chain of custody for every evidence access
Write findings incrementally to /workspace/output/findings/ (containerized) or ./output/findings/ (host)
Generate the final report in /reports/

Plus depuis ce dépôt

même dépôt

full-investigation

valITino/dfireballz

Run a 6-phase forensic investigation — evidence intake, artifact collection, network analysis, threat intel, timeline reconstruction, and reporting.

2026-03-152

incident-response

valITino/dfireballz

Run a 7-phase incident response — triage, containment assessment, evidence collection, attack chain reconstruction, threat intel, impact assessment, and reporting.

2026-03-152

malware-analysis

valITino/dfireballz

Analyze a malware sample — static analysis with Ghidra/Radare2/Capa, YARA scanning, string extraction, and VirusTotal/MalwareBazaar lookup.

2026-03-152

memory-forensics

valITino/dfireballz

Analyze a memory dump — process analysis, network connections, persistence mechanisms, malware detection with Volatility3, and reporting.

2026-03-152

network-forensics

valITino/dfireballz

Analyze network traffic — PCAP triage, protocol analysis, anomaly detection, IoC extraction, stream reconstruction, and reporting.

2026-03-152

osint-domain

valITino/dfireballz

Investigate a domain — DNS/subdomain enumeration, infrastructure analysis, threat assessment, web presence mapping, and reporting.

2026-03-152

name	complete-investigation
description	Run a full 11-phase forensic investigation across all MCP servers — disk, memory, Windows artifacts, malware, network, OSINT, threat intel, timeline, and reporting.

Run the complete forensic investigation workflow against the specified target.

Usage: /complete-investigation <target>

Where <target> is the evidence path or subject — e.g. /evidence/disk.dd, /evidence/memdump.raw, suspicious-domain.com.

If no target is provided, ask the user what they want to investigate.

Instructions

Load the investigation template: call get_template(name="complete-investigation", target="$ARGUMENTS")
Follow all 11 phases in order — do NOT skip any phase
Use the MCP servers and their tools for every phase (kali-forensics, winforensics, osint, threat-intel, binary-analysis, network-forensics, filesystem)
Log chain of custody for every evidence access
Write findings incrementally to /workspace/output/findings/ (containerized) or ./output/findings/ (host)
Generate the final report in /reports/