rev-firmware

Identify and analyze firmware images to extract bootloaders, root filesystems, and RTOS artifacts.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/Xerrion/opencode --skill rev-firmware
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rev-firmware
Source: https://github.com/Xerrion/opencode/tree/main/skills/rev-firmware
Command: npx skills add https://github.com/Xerrion/opencode --skill rev-firmware

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Firmware analysis and reverse engineering of embedded images, bootloaders, root filesystems, and RTOS binaries to extract structure, identify architectures, and enable safe emulation.

Core Features & Use Cases

  • Extraction and carving of filesystem and bootloader data using binwalk, squashfs, and jefferson workflows.
  • Bootloader and firmware analysis (U-Boot and Coreboot) with architecture identification and extraction records.
  • Emulation and testing guidance with qemu-system and firmadyne to validate behavior in a safe environment.
  • Hardware-interface documentation guidance (non-invasive) for UART/JTAG notes.

Quick Start

Provide a firmware image to the skill and begin automated extraction and analysis.

Frequently Asked Questions about rev-firmware

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I emulate an embedded device firmware image using QEMU?

Firmware analysis involves identifying and analyzing embedded images to extract bootloaders, root filesystems, and RTOS artifacts. This skill automates extraction using binwalk and supports architecture identification to enable safe reverse engineering.

Can I analyze U-Boot and Coreboot bootloader images?

Yes, the skill supports bootloader analysis for U-Boot and Coreboot images, including architecture identification and extraction records. It helps you reverse engineer the bootloader structure without needing invasive hardware access.

What is the best way to carve filesystem data from a binary firmware blob?

The best way to extract filesystem data from a firmware image is using binwalk, squashfs, and jefferson carving workflows. The skill automates this extraction process to isolate root filesystems and bootloader data from embedded binaries.

Does firmware emulation with firmadyne work for all extracted rootfs images?

Firmware emulation with firmadyne and qemu-system is intended to validate behavior in a safe environment. While it supports testing extracted rootfs images, emulation success depends on the specific architecture and hardware dependencies of the target firmware.

Do I need invasive hardware access to document UART and JTAG interfaces?

No, invasive hardware access is not required. The skill provides non-invasive hardware-interface documentation guidance for UART and JTAG notes, allowing you to map interfaces safely during the firmware reverse engineering workflow.