CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

reverser-firmware

Router / IoT firmware extraction pipeline — unpack nested filesystems, locate web server, identify backdoor credentials.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./packages/decepticon/decepticon/skills/standard/reverser/firmware/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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.

An excellent, token-efficient playbook: concrete commands, a coherent extract-to-record sequence, and clean section structure with no filler. The only meaningful gap is the absence of explicit validation/error-recovery checkpoints (e.g., what to do when extraction finds no root filesystem).

DimensionReasoningScore

Conciseness

The body is lean and command-driven — every line is an executable command or a terse, high-value tip (e.g., 'CGI binaries under www/cgi-bin/ are the highest-yield targets'), with no explanation of concepts Claude already knows like binwalk or squashfs.

5 / 5

Actionability

Sections 1–2 provide copy-paste-ready bash and sections 4–6 give concrete tool invocations (bin_strings, cve_by_package), but sections 5 and 7 are audit checklists and recording directives rather than executable commands — mostly executable with minor gaps.

4 / 5

Workflow Clarity

A clearly sequenced 7-step numbered pipeline where each step's output feeds the next ($ROOT from step 2 reused throughout), but validation checkpoints are only implicit — there is no guidance for error paths such as find returning no squashfs-root directory.

4 / 5

Progressive Disclosure

The skill is a self-contained ~46-line playbook (under the 50-line simple-skill threshold) with no bundle files, cleanly organized into numbered sections, and nothing inlined that belongs in a separate reference file.

5 / 5

Total

18

/

20

Passed

Description

66%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.

A specific, appropriately terse description with concrete actions and a distinct niche, but it lacks an explicit 'Use when...' trigger clause, leaving the activation conditions only weakly implied. Adding trigger phrases and natural synonyms would raise both completeness and trigger term quality.

Suggestions

Append an explicit trigger clause, e.g. 'Use when analyzing router or IoT firmware images, .bin firmware dumps, or embedded device filesystems for hidden credentials.'

Include natural trigger variations users would actually say, such as 'firmware image', '.bin', 'binwalk', or 'embedded Linux', to broaden trigger term coverage.

Mention the remaining pipeline stages (authentication bypass audit, CVE cross-referencing) so the description comprehensively covers what the skill does.

DimensionReasoningScore

Specificity

The description names the domain ('Router / IoT firmware extraction pipeline') and lists three concrete actions ('unpack nested filesystems, locate web server, identify backdoor credentials'), but omits other capabilities the skill covers (authentication bypass audit, CVE cross-referencing, recording findings), leaving minor gaps in coverage.

4 / 5

Completeness

The 'what' is clearly stated as a three-stage pipeline, but there is no 'Use when...' clause or equivalent explicit trigger guidance — the 'when' is only weakly implied by 'Router / IoT', which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Natural domain keywords like 'Router', 'IoT', 'firmware extraction', 'web server', and 'backdoor credentials' are present and would be said by users needing this skill, but common variations and file extensions ('firmware image', '.bin', 'binwalk', 'embedded device') are missing.

4 / 5

Distinctiveness Conflict Risk

The router/IoT firmware niche with backdoor-credential triggers is clearly distinguishable, with only minor overlap risk against general reverse-engineering or security-audit skills; not a 5 because 'identify backdoor credentials' and 'firmware extraction' could still collide with adjacent security skills.

4 / 5

Total

15

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

PurpleAILAB/Decepticon

Path

packages/decepticon/decepticon/skills/standard/reverser/firmware/SKILL.md

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.