competition-firmware-layout

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.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

72%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise and well-structured with appropriate one-level-deep disclosure, but it stays in instructive-prose form without executable commands and omits explicit validation checkpoints for its mutation-prone extraction workflow.

Suggestions

Add an explicit verification step to the Workflow (e.g. re-hash pristine inputs and confirm offsets/recorded boundaries before and after extraction) to create a validate-then-proceed feedback loop.

Provide at least one concrete executable command or script invocation for the common actions (e.g. a binwalk/unsquashfs snippet or a reference to a bundled unpack script) so guidance is copy-paste ready.

Surface the 'Common Pitfalls' content from references/firmware-layout.md inline in the body's Workflow so the avoid-editing-before-recording warning is part of the main flow, not only the reference.

Dimension	Reasoning	Score
Conciseness	Lean and efficient body that assumes Claude's competence — it never explains what a bootloader, partition table, or filesystem is, and every line (preserve, map, trace, reduce) earns its place.	3 / 3
Actionability	Guidance is concrete ('Record offsets, sizes, hashes, mount points') but delivered as instructive prose with no executable commands or code; for an extraction-heavy skill this is one level below copy-paste-ready.	2 / 3
Workflow Clarity	The Establish → Trace → Reduce sequence is clear, but the workflow mutates artifacts (extraction) yet lacks an explicit validation/verification checkpoint, which caps destructive/batch workflows at 2 per the rubric.	2 / 3
Progressive Disclosure	The body is a concise overview with a single clearly-signaled one-level-deep reference ('Load `references/firmware-layout.md` for the layout checklist, boot-chain checklist, and evidence packaging'), and that file exists in the bundle.	3 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, trigger-rich, and complete, clearly stating both capabilities and when to use the skill in third person. It is well-scoped to a distinct niche with low conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'unpack firmware, map partition layout, inspect bootloader or init chains, recover update keys or credentials, trace config loading' — rather than vague language.	3 / 3
Completeness	Explicitly answers what ('CTF-sandbox workflow for firmware images, partition tables, boot chains...') and when ('Use when the user asks to unpack firmware...') in third person, with an explicit 'Use when' trigger clause.	3 / 3
Trigger Term Quality	Uses natural user phrases ('unpack firmware', 'map partition layout', 'inspect bootloader or init chains', 'recover update keys or credentials', 'trace config loading') that a user would plausibly say when needing this skill.	3 / 3
Distinctiveness Conflict Risk	Narrow CTF-sandbox firmware-layout niche scoped as a downstream of `$ctf-sandbox-orchestrator`, with distinct firmware-specific triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: zhaoxuya520/reverse-skill
Path: CTF-Sandbox-Orchestrator/competition-firmware-layout/SKILL.md
Commit: 6aa1362

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.