native-triage
Evidence-first first-contact triage of a native binary (ELF/PE/Mach-O/firmware/shared library) before any deep reading - identify format/arch, harvest free names (symbols, RTTI, debug info, build paths), classify strings with their referrers, read the import table as an attack-surface/capability map, fold away known library code, recover symbols for stripped functions, and decide decompiler vs disassembly per question. Use for "analyze this binary", "what does this exe/dll/so do", "stripped binary", "recover function names", "decompiler output looks wrong", "바이너리 분석", "리버싱 시작", "스트립된 바이너리 심볼 복구", "문자열/임포트 분석", "디컴파일 vs 디스어셈블리".
Pinned to revision cb2330c1f074, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/native-triage/SKILL.md
- skills/native-triage/references/decompile-vs-disasm.md
- skills/native-triage/references/strings-and-imports.md
- skills/native-triage/references/symbol-recovery.md
- skills/native-triage/references/triage-checklist.md
- skills/native-triage/scripts/strings_report.py
Every link opens the file at its source, pinned to the revision this page describes.