菜单
Use when selecting or maintaining investigation recipes that map goals to skills, scripts, MCP tools, outputs, and project-state updates.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | offensive-macos-maproom-recipes |
| description | Use when selecting or maintaining investigation recipes that map goals to skills, scripts, MCP tools, outputs, and project-state updates. |
| folder | offensive-macos-maproom-recipes |
| source | skillz-wave4 |
| trigger_phrases | ["maproom","recipe registry","which recipe","investigation recipe"] |
Channel boundary:
REPO_MODE=analysis. Recipes route evidence collection; they are not exploit chains or proof by themselves.
docs/playbooks/investigation-recipes.md.inventory-first-manual-routing and record the gap.scripts/validate-recipes.py.docs/playbooks/investigation-recipes.mdscripts/validate-recipes.pySkills/offensive-macos-watch-static-analysis/SKILL.mdUse when choosing or adding macOS research machines: primary, crash-test, cross-platform Apple Silicon, and Intel baseline. Fires on "add a lab machine", "which machine should run this", "primary lab host", "crash-test", "Intel baseline", and "cross-platform verification".
Use when driving Ghidra headless from Cursor for macOS reverse engineering: opening Mach-O binaries, listing functions, decompiling by address, running custom Ghidra scripts, or doing breadth sweeps across many targets. Fires on "ghidra-mcp", "decompile with Ghidra", "run a Ghidra script", "list functions in this binary", and systemic-class scan setup.
Use when starting a macOS reversing pass from an app bundle, installer, framework, XPC bundle, helper, or bare binary path. Fires on "start target", "inventory this app", "point at this bundle", "begin PASS", and "target intake".
Use when mapping a macOS target's attack surfaces to reusable vulnerability classes, generating hunt hypotheses for a new third-party app, or deciding which playbook or scanner applies. Fires on "vulnerability ontology", "bug-class map", "what bug classes apply", "generate hypotheses", and "classify this macOS surface".
Use when a macOS target appears to be Electron-based and needs ASAR, package, preload, IPC, native module, fuse, sandbox, or update review.
Use when a question touches the lab topology: what runs on the workstation, what runs on the primary lab host, how `ghidra-mcp` and `macre-vm-mcp` are wired, how to start a findings repo, which machine role to use, why Hopper is manual-only, or how to troubleshoot MCP/SSH/script sync failures.