Individual skill
malware-analysis
Orchestrate the complete malware analysis lifecycle across triage, dynamic analysis, detection engineering, and report writing. Use as the single entry point for any malware analysis task — routes to specialized sub-skills by file type and phase, carries findings between phases, and supports multi-sample batch workflows.
SKILL.md
Source commit e1d9a1a8e18e3db8f3534436cfc763c53b6b3350
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 54
- Repository last updated
- Sep 5, 2026
- License
- MIT
Observed agent integration: claude-code
- blue-team Repository topic
- claude-ai Repository topic
- claude-skills Repository topic
- cybersecurity Repository topic
- flarevm Repository topic
- incident-response Repository topic
- malware-analysis Repository topic
- malware-detection Repository topic
- malware-research Repository topic
- malware-triage Repository topic
- engineering Derived category
- writing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
.claude-plugin/marketplace.jsonasset · 788 bytes.claude-plugin/plugin.jsonasset · 731 bytes.github/workflows/mirror.ymlasset · 685 bytes.github/workflows/test.ymlasset · 487 bytes.gitignoreasset · 329 bytesCHANGELOG.mddoc · 7,982 bytesCLAUDE.mddoc · 7,212 bytesLICENSEasset · 1,065 bytesREADME.mdruns · 19,128 bytesSKILL.mdcore · 13,822 bytesSKILL.mdcore · 13,822 bytesSKILL.mdcore · 13,822 bytesdocs/example-triage.mddoc · 5,024 bytesreferences/mcp_integrations.mddoc · 10,217 bytesscripts/ioc_extract.pyruns · 11,830 bytestests/extract_rules.pyruns · 895 bytestests/fixtures/evidence/dns.txtdoc · 146 bytestests/fixtures/evidence/http.txtdoc · 228 bytestests/fixtures/evidence/procmon.csvasset · 2,500 bytestests/fixtures/evidence/syn.txtdoc · 203 bytestests/fixtures/evidence/sysmon.jsonasset · 5,319 bytestests/fixtures/evidence/tls.txtdoc · 89 bytestests/fixtures/scripts/malicious.ps1runs · 421 bytestests/fixtures/scripts/malicious.vbsruns · 188 bytestests/fixtures/yara/fixture.yarasset · 575 bytestests/make_pe.pyruns · 5,521 bytestests/run.shruns · 6,647 bytes
Read excerpt
# Malware Analysis Orchestrator
Single entry point for malware analysis engagements. Routes to specialized sub-skills, carries findings between phases, and manages multi-sample workflows.
## How This Works
You describe what you need — "analyze this sample", "I have 5 files to triage", "create detection rules from my findings" — and this orchestrator:
1. Determines which sub-skill to use based on your file type and intent
2. **Runs the analysis** using that sub-skill: Claude executes the static tooling, parses exported evidence, writes rules and reports itself
3. Records findings in a state file (`analysis_state.md`)
4. Recommends the next phase when the current one completes
5. Waits for your confirmation before proceeding