Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

complete-investigation

Estrelas2

Forks1

Atualizado15 de março de 2026 às 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.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

valITino

valITino/dfireballz

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Analistas de segurança da informaçãoInformática e Matemática·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/

Mais deste repositório

mesmo repositório

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/