CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bootloader-uboot

U-Boot bootloader attack playbook — console interrupt to break the autoboot countdown, environment variable inspection and manipulation, bootargs override to spawn init=/bin/sh, secure-boot bypass techniques, and fault-injection basics (voltage and clock glitching). Covers MIPS, ARM, and AArch64 targets.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

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

A strong, action-dense attack playbook with a clearly sequenced six-phase workflow and executable code for the main exploitation path. The main weaknesses are the absence of validation checkpoints around destructive flash operations (which caps workflow clarity) and a few non-executable command lines presented as if runnable at the U-Boot prompt.

Suggestions

Add explicit validation checkpoints around the destructive flash operations in Phase 4/5d: dump the environment/bootloader region before saveenv or sf write, verify the image size against mtdparts before erase, and verify the write afterward, with a fix-and-retry loop on mismatch.

Fix or flag command lines that will not execute in U-Boot's shell — 'printenv | grep -i ...' has no pipe support in U-Boot; either replace with manual inspection of printenv output or mark such lines as host-side equivalents.

Move the full automation script and the ChipWhisperer glitching snippet into a scripts/ bundle file, keeping SKILL.md as an overview with one-line pointers, to reduce inline length and improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is dense and command-first with almost no filler; the only trimmable material is the intro blockquote explaining what U-Boot is and a few framing sentences like 'This is the primary exploitation primitive: replace the kernel init process...'. Anchor 4 (efficient, minor instances of over-explanation) fits better than 5, and 3 would understate how little padding exists.

4 / 5

Actionability

The primary attack path (console interrupt, printenv, setenv bootargs with init=/bin/sh, run bootcmd) is fully copy-paste ready, and both the serial automation script and the ChipWhisperer snippet are executable. Minor gaps keep it below anchor 5: placeholders like '<0>', '<original_value>', and a few U-Boot lines that would not execute as written (e.g. 'printenv | grep' — U-Boot's shell has no pipes).

4 / 5

Workflow Clarity

Phases 1–6 are clearly sequenced with some error recovery (power-cycle retry on missed autoboot, the script's prompt check), but destructive flash operations (saveenv, sf erase/sf write) carry warnings only, not explicit validation checkpoints or feedback loops (no dump-before-erase, no verify-after-write). Per the judging guideline, missing validation in destructive workflows caps workflow_clarity at 3.

3 / 5

Progressive Disclosure

Sections are well organized with clear phase headers and a clearly labeled References list of external URLs, with no nested references. It falls short of anchor 5 because the ~340-line body inlines two complete standalone scripts and the full hardware-glitching details that would naturally live in scripts/ or references/ bundle files — anchor 4's 'minor organization gaps'.

4 / 5

Total

15

/

20

Passed

Description

83%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, comprehensive description that names concrete attack techniques and the target architectures, with explicit trigger terms supplied via the when_to_use metadata. Its only gap is that the 'when to use' guidance lives in metadata rather than in the description sentence itself.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete actions covering the domain comprehensively: 'console interrupt to break the autoboot countdown, environment variable inspection and manipulation, bootargs override to spawn init=/bin/sh, secure-boot bypass techniques, and fault-injection basics (voltage and clock glitching)'. This matches the anchor-5 example's breadth; anchor 4 would imply a notable coverage gap, and none exists.

5 / 5

Completeness

The 'what' is clear and concrete, and explicit trigger guidance exists in the frontmatter via metadata.when_to_use ('U-Boot, uboot, bootloader, autoboot, printenv, setenv, bootargs, init=/bin/sh, secure boot bypass, fault injection, glitching, boot console, UART bootloader, embedded Linux boot'), so the cap-at-3 rule for missing 'Use when' guidance is not triggered. It is not a 5 because the description text itself contains no 'when' clause — the trigger guidance is in a separate metadata field rather than integrated into the description.

4 / 5

Trigger Term Quality

Good natural-term coverage: 'U-Boot', 'bootloader', 'autoboot', 'bootargs', 'init=/bin/sh', 'secure-boot', 'fault-injection', 'glitching', plus MIPS/ARM/AArch64. A few natural phrases a user might say are absent (e.g. 'root shell', 'UART console', 'embedded device'), placing it at anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

A clear niche — U-Boot bootloader attacks against embedded MIPS/ARM/AArch64 targets — with distinct triggers (uboot, autoboot, bootargs, glitching) that are unlikely to fire for the wrong skill. Anchor 5 fits; no meaningful overlap with adjacent firmware-analysis skills is evident.

5 / 5

Total

18

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

PurpleAILAB/Decepticon

Path

packages/decepticon/decepticon/skills/standard/iot/bootloader-uboot/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.