CtrlK
BlogDocsLog inGet started
Tessl Logo

binwalk-extract

Firmware image extraction with binwalk and firmware-mod-kit — recursive archive carving, squashfs/jffs2/ubifs mounting, entropy analysis to detect packed/encrypted regions, and nested container handling. Entry point for all static filesystem analysis after a raw binary image is acquired.

64

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./packages/decepticon/decepticon/skills/standard/iot/binwalk-extract/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

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

The content is a strong, executable firmware-extraction playbook: copy-paste commands covering all common container types, a clearly sequenced 8-step workflow with verification checkpoints, and clean section organization. It is efficient and actionable, with only minor room to tighten explanatory comments and split detail into reference files.

DimensionReasoningScore

Conciseness

The body is command-heavy and lean, assuming Claude knows the tools without explaining what binwalk or squashfs are; a few inline explanatory comments (e.g., the entropy reading table, the sasquatch compression note) could be trimmed but mostly earn their place.

4 / 5

Actionability

Fully executable, copy-paste-ready bash with real flags across all common cases — 'binwalk -eM -C "$OUTDIR" "$FW"', 'sasquatch -p 1 -le -d /tmp/squashfs_root "$SQFS"', the python3 magic-byte carving script, and dd carving — with no meaningful gaps.

5 / 5

Workflow Clarity

A clearly numbered 8-step sequence (Identify+Entropy → Recursive Extraction → Squashfs → JFFS2 → UBIFS → Manual Carving → Nested → Triage) with checkpoints such as 'Verify extraction' and fallback compression flags; minor validation gaps and no full validate→fix→retry loop keep it just below anchor 5.

4 / 5

Progressive Disclosure

Well-organized single-file structure with clear section headers and a dedicated References section linking external URLs; no bundle files exist to split into, and at 232 lines some detail (manual carving script, entropy table) could be offloaded to reference files, so anchor 5 is not reached.

4 / 5

Total

17

/

20

Passed

Description

71%Weight 40%Scale 1-5

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, tool-named, and domain-clear, but it lacks an explicit 'Use when...' trigger clause, which caps completeness at 3 and leaves trigger-term coverage just below comprehensive. Adding a concrete trigger phrase and file extensions would lift the two weakest dimensions.

Suggestions

Append an explicit 'Use when...' trigger clause naming natural user phrases (e.g., 'Use when the user asks to extract firmware, unpack a squashfs/jffs2/ubifs rootfs, or run entropy analysis on a raw binary image') to raise completeness above 3.

Add file extensions and synonyms to the trigger terms (e.g., .bin, .squashfs, .ubi, .img, 'unpack rootfs') to move trigger_term_quality from 4 to 5.

Tighten the broad 'Entry point for all static filesystem analysis' framing to reduce overlap with sibling firmware skills and sharpen distinctiveness.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'recursive archive carving', 'squashfs/jffs2/ubifs mounting', 'entropy analysis to detect packed/encrypted regions', 'nested container handling' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

The 'what' is clear and detailed, but there is no explicit 'Use when...' trigger clause; 'Entry point for all static filesystem analysis after a raw binary image is acquired' is a workflow-sequencing condition, only weakly implying 'when', so completeness is capped at 3 per the missing-trigger-guidance rule.

3 / 5

Trigger Term Quality

Includes strong natural tool/domain keywords ('binwalk', 'firmware-mod-kit', 'squashfs', 'jffs2', 'ubifs', 'entropy analysis') a user would say, but omits synonyms and file extensions (.bin, .squashfs, .ubi) that anchor 5 requires.

4 / 5

Distinctiveness Conflict Risk

Names specific tools (binwalk, firmware-mod-kit) and a clear firmware-extraction niche, making it mostly distinct; minor overlap risk with sibling skills (firmware-acquisition, bootloader-uboot) and the broad 'all static filesystem analysis' framing keep it just short of anchor 5.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
PurpleAILAB/Decepticon
Reviewed

Table of Contents

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.