Skip to content
SkillModel-led529 tokens in use

competition-firmware-layout

A downstream CTF-sandbox skill for firmware images: it maps partitions, boot and update chains and extracted filesystems to the device behavior or artifact they lead to.

44,996 stars on the repository MIT Licensezhaoxuya520/reverse-skill · CTF-Sandbox-Orchestrator/competition-firmware-layout

Skill label

measured from its files

What installing competition-firmware-layout costs

111tokens idle
529tokens in use
756tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter12/15
  • Structure23/25
  • Examples0/15
  • Output7/15
  • Size15/15
  • Resources7/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity96
  • Maintenance72
  • Community72
  • Maturity28
  • Momentum40

This skill is a specialization of the ctf-sandbox-orchestrator skill for challenges where the hard part is understanding how a firmware image is structured, booted, updated and turned into reachable device behavior. The agent keeps the original image, extracted partitions and patched copies as separate artifacts and records offsets, hashes and entrypoints.

The skill states that it runs only after the orchestrator has set sandbox assumptions.

What You Get

  • A three-step workflow: establish image layout, trace boot or update flow, reduce to the decisive path
  • A reference checklist for container, partitions, filesystems, bootloader, kernel, init and update verifier stages
  • A rule to record offsets and hashes before extraction changes anything
  • A hand-off rule to the broader reverse skill when the task shifts to native crash behavior

Common Use Cases

  • Unpacking a firmware image from a CTF challenge and mapping its partitions
  • Tracing which stage of a boot or update chain consumes a key, certificate or config file
  • Documenting how an extracted init script leads to an exposed service in a lab device

What Makes It Unique

It follows the boot or update chain in order and does not jump to the most interesting file. Its checklist warns against editing extracted files before pristine offsets and hashes are recorded, and against calling a secret decisive before showing where the flow consumes it.

Under The Hood

The skill is instruction text only: a SKILL.md, one reference checklist and an agent configuration file. It ships no scripts. The method involves unpacking images, mounting or extracting filesystems and reading config and init files, so the agent’s own tools run commands and write extracted files in the sandbox the orchestrator set up. The skill does not fetch pages or call APIs on its own.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers