# Set Up Binary Reverse Engineering Tools

Binary analysis often fails when required tools, emulators, or sysroots are missing. This skill gives platform-specific setup and troubleshooting guidance for a complete reverse engineering environment.

## Install

```bash
npx skillstore add 2389-research/binary-re-tool-setup
```

## Metadata

- - Slug: 2389-research-binary-re-tool-setup
- - Version: 1.0.0
- - Author: 2389-research
- - GitHub username: 2389-research
- - License: MIT
- - Repository: https://github.com/2389-research/claude-plugins/tree/main/binary-re/skills/tool-setup
- - Ref: main
- - Supported tools: Claude, Codex, Claude Code
- - Risk level: medium
- - Risk factors: external\_commands, network, filesystem
- - Quality score: 50
- - Quality tier: warning
- - Public page: https://skillstore.pages.dev/skills/2389-research-binary-re-tool-setup
- - Manifest: https://skillstore.pages.dev/api/skills/2389-research-binary-re-tool-setup/manifest

## Capabilities

- Lists required and recommended tools for binary reverse engineering workflows.
- Provides setup steps for Ubuntu, Debian, WSL2, macOS, Docker, and Arch Linux.
- Covers radare2, r2ghidra, Ghidra headless, GEF, Frida, Unicorn, Angr, and YARA.
- Explains sysroot setup for ARM, ARM64, custom device libraries, and musl environments.
- Includes a verification script outline for checking installed tool availability.
- Documents common troubleshooting steps for QEMU, Docker, GDB, Ghidra, and missing libraries.

## Use Cases

- Prepare a Linux analysis workstation: Install core disassembly, debugging, emulation, and binary utility packages before starting firmware or malware analysis.
- Configure cross-architecture testing: Set up QEMU, sysroots, and Docker-based emulation for ARM, ARM64, and x86 test cases.
- Troubleshoot missing reverse engineering tools: Diagnose missing commands, plugin failures, Docker binfmt errors, and library resolution problems.

## Prompt Templates

### Check my setup needs

```
I am setting up a binary reverse engineering workstation on Ubuntu. Tell me which required tools I should install first and why.
```

### Fix a missing tool error

```
I tried to analyze an ARM binary, but qemu-arm is missing. Help me install and verify the required tools on my platform.
```

### Plan cross-architecture emulation

```
I need to run ARM32 and ARM64 Linux binaries from a macOS host. Recommend the safest setup path using this skill.
```

### Audit risky setup commands

```
Review the privileged and network-based commands in this setup guide. Identify which commands need approval before I run them.
```

## Limitations

- It provides setup instructions, not automated installation or sandbox enforcement.
- Some commands require administrator privileges and can change system configuration.
- Tool versions and package names may differ across distributions and release dates.
- Remote installer commands should be reviewed before execution in production environments.

## Best Practices

- Run setup commands in a disposable virtual machine or container when possible.
- Review network-delivered installer scripts before executing them locally.
- Record installed tool versions so analysis results can be reproduced.

## Anti Patterns

- Do not run privileged Docker or sudo commands on a production host without review.
- Do not pipe remote installer scripts into a shell without inspecting the source.
- Do not mix host and target libraries without tracking the active sysroot.

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-06-27T16:11:28.74\+00:00
- - Summary: The static findings are mostly true positives for documented setup commands, not hidden executable behavior. The skill contains privileged package installs, privileged Docker binfmt registration, remote installer execution, and shell configuration changes, so publication should include a clear warning for users to review commands before running them.

## Stats

- - Views: 280
- - Downloads: 9
- - Favorites: 1
- - Popularity score: 0