competition-firmware-layout — Claude Code skill: what it does
competition-firmware-layout — a skill for Claude Code, Codex, Cursor and other platforms that maps firmware images, partition tables, and boot chains.
MIT 109 installs ★ 45,047 updated 2026-09-22
npx skills add zhaoxuya520/reverse-skill --skill competition-firmware-layout -a claude-codeWhat competition-firmware-layout 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.
What it helps with
- 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 for the agent
- Unpack this firmware image and map the partition layout
- Trace the boot chain from bootloader to init
- Recover credentials from the extracted configuration
How to install competition-firmware-layout
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-firmware-layout -a claude-code2Manually: put the files in place
~/.claude/skills/competition-firmware-layout/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/competition-firmware-layout/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-firmware-layout -a codex2Manually: put the files in place
.agents/skills/competition-firmware-layout/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-firmware-layout -a cursor2Manually: put the files in place
.cursor/skills/competition-firmware-layout/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install zhaoxuya520/reverse-skill CTF-Sandbox-Orchestrator/competition-firmware-layout/SKILL.md2Manually: put the files in place
.github/skills/competition-firmware-layout/SKILL.md1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-firmware-layout -a gemini-cli2Platform CLI
gemini skills install https://github.com/zhaoxuya520/reverse-skill --path CTF-Sandbox-Orchestrator/competition-firmware-layoutManually: put the files in place
.devin/skills/competition-firmware-layout/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-firmware-layout -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about competition-firmware-layout
How to install competition-firmware-layout in Claude Code?
Run npx skills add zhaoxuya520/reverse-skill --skill competition-firmware-layout -a claude-code and check ~/.claude/skills/competition-firmware-layout/SKILL.md.
What does competition-firmware-layout do?
It processes firmware images, maps partition tables, tracks boot and update flows, and organizes evidence for reverse engineering tasks.
What is needed to run competition-firmware-layout?
The skill requires the $ctf-sandbox-orchestrator to be active and have established sandbox assumptions before routing.
Source text
SKILL.md · MIT
--- 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. - If the challenge becomes mostly about native crash behavior or exploit primitives after extraction, switch back to the broader reverse skill. ## Read This Reference - Load `references/firmware-layout.md` for the layout checklist, boot-chain checklist, and evidence packaging. ## What To Preserve - Partition offsets, hashes, filesystem types, mount paths, boot entrypoints, and update metadata - Extracted secrets, config paths, init scripts, service units, and credentials tied to the stage that consumes them - Original images, extracted layers, mounted views, and patched copies as separate artifacts
© zhaoxuya520 · MIT · zhaoxuya520/reverse-skill