Skip to content

zhaoxuya520/reverse-skill / CTF-Sandbox-Orchestrator/competition-firmware-layout

competition-firmware-layout

Verified

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.

FileKindSize
SKILL.mdskill md3.2 KB
agents/openai.yamlconfig402 B
references/firmware-layout.mdmarkdown1.1 KB

references/firmware-layout.md

View on GitHub
# Firmware Layout Checklist

## First Pass

- Identify outer container, partition headers, compression, checksums, and appended images
- Record partition names, offsets, sizes, filesystem types, mount points, and hashes
- Separate bootloader, kernel, initramfs, rootfs, config, and update payloads

## Boot Or Update Chain

1. Boot ROM or vendor bootstrap
2. Bootloader or secure boot stage
3. Kernel and initramfs
4. Root filesystem init path and services
5. Update verifier, installer, and post-install hooks

## Evidence To Keep Together

- Boundary facts: offsets, sizes, signatures, hashes, partition names
- Consumed state: keys, certs, passwords, default configs, scripts, or service files
- Reachable effect: debug service, auth branch, update bypass, or recovered artifact

## Common Pitfalls

- Editing extracted files before recording pristine offsets and hashes
- Mixing config recovered from one partition with behavior sourced from another without proving the link
- Treating an extracted secret as decisive without showing where the boot or update flow actually consumes it
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall