competition-firmware-layout

Maps firmware partitions, boot chains, and update flows to recover decisive secrets.

21|8|Updated Aug 3, 2026
One-click install
npx skills add https://github.com/chengzongcai/reverse-skill-backup --skill competition-firmware-layout-chengzongcai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: competition-firmware-layout
Source: https://github.com/chengzongcai/reverse-skill-backup/tree/main/CTF-Sandbox-Orchestrator/competition-firmware-layout
Command: npx skills add https://github.com/chengzongcai/reverse-skill-backup --skill competition-firmware-layout-chengzongcai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? CTF and reverse-engineering tasks involving firmware images often stall because analysts jump straight to interesting files without understanding partition layout, boot order, or update verification. This Skill provides a structured workflow for unpacking firmware images, tracing boot and update chains, and proving how a device surface reaches the decisive artifact. ## Core Features & Use Cases - Image Layout Mapping: Identify containers, partition tables, compression, filesystems, and nested images while recording offsets, sizes, and hashes before extraction. - Boot and Update Chain Tracing: Follow control flow from bootloader to kernel to init to services, or from update package to verifier to installer, tracking which credentials and configs each stage consumes. - Decisive Path Reduction: Reduce the analysis to the smallest chain from image boundary to service exposure, auth bypass, credential recovery, or flag artifact. - Use Case: Given a CTF firmware image, map its partition table, extract the rootfs, trace the init scripts to a debug service, and recover the credentials that service consumes. ## Quick Start After $ctf-sandbox-orchestrator is active, use $competition-firmware-layout to map this firmware image, extract its partitions, trace the boot chain, and recover the decisive secret.

Frequently Asked Questions about competition-firmware-layout

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

FAQPage Schema
How do I unpack and analyze a firmware image for a CTF challenge?▼

Start by identifying the container type, partition headers, compression, and filesystem type, recording offsets and hashes before extraction. Then separate bootloader, kernel, initramfs, rootfs, and config layers, and trace the boot or update chain to the decisive artifact.

How to trace a firmware boot chain from bootloader to services?▼

Map control flow in order: boot ROM or vendor bootstrap, bootloader or secure boot stage, kernel and initramfs, then rootfs init path and services. Record which keys, certificates, passwords, or config files each stage consumes.

What evidence should I preserve when extracting firmware partitions?▼

Preserve partition offsets, sizes, hashes, filesystem types, mount paths, boot entrypoints, and update metadata. Keep original images, extracted layers, mounted views, and patched copies as separate artifacts so pristine inputs are never mutated.

When should I use this firmware skill instead of a general reverse engineering skill?▼

Use it when the hard part is understanding how a firmware image is structured, booted, or updated. If the challenge becomes mostly about native crash behavior or exploit primitives after extraction, switch back to the broader reverse skill.

Why is editing extracted firmware files before recording offsets a problem?▼

Editing before recording pristine offsets and hashes destroys boundary evidence needed to prove where secrets are consumed. It also risks mixing config from one partition with behavior sourced from another without proving the link.