tool-setup_skill

This skill helps you install and configure reverse engineering tools across platforms, ensuring ready-to-use environments for cross-architecture analysis.

JavaScript

30

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill 2389-research/claude-plugins --skill tool-setup

SKILL.md10.6 KB

Overview

This skill helps install, verify, and configure common reverse-engineering tools when they are missing, failing, or need cross-architecture setup. It provides concrete installation commands, verification scripts, and platform-specific tips for Ubuntu/Debian, WSL2, macOS (Homebrew/Docker), and Arch. The goal is a reliable analysis environment with radare2, QEMU, GDB, Ghidra, Frida, and cross toolchains.

How this skill works

The skill inspects your environment for required tools and sysroots, offers step-by-step install commands per platform, and supplies verification scripts you can run. It includes tool-specific setup (r2 plugins, Ghidra headless, GEF, frida/unicorn/angr), Docker/Colima guidance for missing qemu-user targets, and troubleshooting recipes for common errors. Use the verification script to confirm each tool and sysroot is correctly installed.

When to use it

Before first reverse-engineering session to prepare the environment
When commands like r2, qemu-arm, or gdb-multiarch return errors
Setting up a new machine or WSL2 instance for binary analysis
After updating tools when plugins or decompilers stop working
When cross-architecture emulation or sysroots are missing

Best practices

Use package managers per platform (apt, brew, pacman) for core tools and pip/venv for Python bindings
Prefer WSL2 on Windows and copy binaries into home (~) to avoid permission issues
Keep r2 and r2ghidra versions aligned; verify r2ghidra with a quick pdg check
Use Docker/Colima to provide qemu-user targets on macOS when Homebrew qemu lacks targets
Create and activate virtual environments for angr, Unicorn, and other Python libs to avoid global conflicts

Example use cases

Install a complete Ubuntu toolchain (radare2, qemu-user, gdb-multiarch, cross libc packages) before analyzing ARM binaries
Fix r2 'pdg unknown command' by reinstalling r2ghidra with r2pm and re-verifying
Run Docker with binfmt registration to eliminate 'exec format error' when testing ARM containers
Prepare a Ghidra headless server with increased MAXMEM for decompiling large binaries
Collect a device sysroot over SSH to run QEMU with correct libraries and avoid 'ld-linux.so.* not found'

FAQ

Run r2 -qc 'pdg?' - and check for a Usage line or run r2 -c 'Ld' /bin/ls and grep for ghidra. Reinstall via r2pm -ci r2ghidra if missing.

What to do if Docker shows 'exec format error'?

Register binfmt handlers with tonistiigi/binfmt --install arm (run privileged) and verify /proc/sys/fs/binfmt_misc/qemu-arm is present. For Colima, ensure mounts use ~/ not /tmp.