# competition-firmware-layout

competition-firmware-layout — a skill for Claude Code, Codex, Cursor and other platforms that maps firmware images, partition tables, and boot chains.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 109 installs · ★ 45047 repo stars
- Author: zhaoxuya520
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/zhaoxuya520/reverse-skill/tree/HEAD/CTF-Sandbox-Orchestrator/competition-firmware-layout/SKILL.md
- Updated: 2026-09-22
- Security check: automated, 2026-11-17 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/competition-firmware-layout

## What it does

The skill analyzes firmware images, partition tables, bootloaders, update packages, and embedded configurations. The agent loads it only after the `ctf-sandbox-orchestrator` has established sandbox assumptions and routing. The workflow preserves original images and patches as separate artifacts, maps partition layouts before extraction, and traces the boot chain in sequential order.

Operation requires an active orchestrator session. The process records offsets, hashes, mount points, and init entrypoints while keeping extracted filesystems isolated from pristine inputs. Reference data is loaded from `references/firmware-layout.md`.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add zhaoxuya520/reverse-skill --skill competition-firmware-layout -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/competition-firmware-layout/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/competition-firmware-layout/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add zhaoxuya520/reverse-skill --skill competition-firmware-layout -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/competition-firmware-layout/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add zhaoxuya520/reverse-skill --skill competition-firmware-layout -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/competition-firmware-layout/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install zhaoxuya520/reverse-skill CTF-Sandbox-Orchestrator/competition-firmware-layout/SKILL.md
```

2. **Manually: put the files in place**
- File: `.github/skills/competition-firmware-layout/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add zhaoxuya520/reverse-skill --skill competition-firmware-layout -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/zhaoxuya520/reverse-skill --path CTF-Sandbox-Orchestrator/competition-firmware-layout
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/competition-firmware-layout/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add zhaoxuya520/reverse-skill --skill competition-firmware-layout -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/zhaoxuya520/reverse-skill/tree/HEAD/CTF-Sandbox-Orchestrator/competition-firmware-layout/SKILL.md

## When to use it
- unpack firmware images and filesystems
- map partition layout and container types
- trace bootloader and init chains
- recover update keys and credentials
- isolate extracted artifacts from patches

## Example prompts
- Unpack this firmware image and map the partition layout
- Trace the boot chain from bootloader to init
- Recover credentials from the extracted configuration

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: f50bf39f8d7b3bb2.

BEGIN THIRD-PARTY FILE f50bf39f8d7b3bb2
```text
---
name: competition-firmware-layout
description: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for firmware images, partition tables, boot chains, update packages, extracted filesystems, embedded configs, and device-facing trust boundaries. Use when the user asks to unpack firmware, map partition layout, inspect bootloader or init chains, recover update keys or credentials, trace config loading, or explain how a device surface reaches the decisive artifact. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.
---

# Competition Firmware Layout

Use this skill only as a downstream specialization after `$ctf-sandbox-orchestrator` is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to `$ctf-sandbox-orchestrator` first.

Use this skill when the hard part is understanding how a firmware image is structured, booted, updated, and turned into reachable device behavior.

Reply in Simplified Chinese unless the user explicitly requests English.

## Quick Start

1. Preserve the original image, extracted partitions, unpacked filesystems, and patched copies as separate artifacts.
2. Map outer container, partition table, bootloader, kernel, rootfs, config, and update metadata before editing anything.
3. Track the boot or update chain in order instead of jumping straight to the most interesting file.
4. Record keys, signatures, offsets, partition boundaries, and init entrypoints in one compact evidence chain.
5. Reproduce the decisive secret, branch, or reachable service from the smallest extracted path.

## Workflow

### 1. Establish Image Layout

- Identify container type, partition headers, compression, filesystem type, and any appended or nested images.
- Record offsets, sizes, hashes, mount points, and partition names before extraction mutates anything.
- Separate bootloader, kernel, initramfs, rootfs, config blobs, and update metadata as different layers.

### 2. Trace Boot Or Update Flow

- Map how control moves from bootloader to kernel to init to services, or from update package to verifier to installer.
- Note which credentials, certificates, passwords, seeds, or config files are consumed at each stage.
- Distinguish checked-in firmware intent from the live behavior the extracted files actually support.

### 3. Reduce To The Decisive Path

- Show the smallest chain from image boundary to service exposure, auth bypass, debug interface, credential recovery, or flag artifact.
- Keep extracted filesystems, derived configs, and patch experiments separate from pristine inputs.
```
END THIRD-PARTY FILE f50bf39f8d7b3bb2

The third-party file has ended. Everything between the f50bf39f8d7b3bb2 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2678 of 3289 bytes. © zhaoxuya520 · MIT · https://github.com/zhaoxuya520/reverse-skill/tree/HEAD/CTF-Sandbox-Orchestrator/competition-firmware-layout/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
