CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

offensive-iot

IoT and embedded device security testing methodology. Covers hardware reconnaissance (UART, JTAG, SWD, SPI flash, I2C EEPROM, eMMC chip-off), firmware acquisition (vendor portals, OTA capture, flash dump, binwalk extraction), firmware analysis (filesystem mounting, binary triage, hardcoded secrets, default credential discovery), bootloader attacks (U-Boot console, secure-boot bypass, fault injection), runtime attacks on embedded Linux/RTOS (busybox CVEs, MTD writes, /dev/mem), wireless protocol attacks (Zigbee, BLE, Z-Wave, LoRaWAN, Thread/Matter, sub-GHz), MQTT/CoAP/Modbus/BACnet/OPC-UA exploitation, mobile companion app analysis, cloud-IoT API abuse, and side-channel/glitching basics. Use for IoT pentest, smart-home assessment, ICS/OT testing, or embedded vulnerability research.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

80%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 exceptionally actionable, token-efficient methodology body whose main weaknesses are structural: destructive flash/write operations proceed without validation checkpoints, and the entire multi-domain playbook is inlined in one large file rather than split across one-level-deep reference files. Both issues are fixable without touching the strong command content.

Suggestions

Add explicit validation checkpoints around destructive operations: verify the flash dump (compare size/entropy, `flashrom --verify`) before any MTD write or re-flash, and re-read back partitions after `mtd_debug write` to confirm the image landed correctly.

Add a post-exploitation verification step to the Quick Workflow and Engagement Checklist (e.g., confirm shell persistence and document state changes) so each destructive step has a feedback loop.

Split the large subdomain playbooks (Wireless Protocols, ICS/OT Protocols, RTOS/MCU, Companion App/Cloud API) into one-level-deep reference files under references/ with clearly signaled links from SKILL.md, keeping the main file as a workflow-oriented overview.

DimensionReasoningScore

Conciseness

The body is command-dense and nearly every line delivers niche knowledge Claude lacks ('8-pin SOIC = SPI NOR; BGA = eMMC', 'Always try root/<serial number>', 'GoAhead, Boa, mini_httpd — abandoned codebases'); it assumes competence and avoids explaining known concepts.

5 / 5

Actionability

Nearly every section has copy-paste-ready commands (flashrom, binwalk, openocd, gatttool, mosquitto_sub, mitmproxy, a pymodbus snippet, rtl_433) plus concrete specifics like default-credential lists and the Touchlink master key; the fault-injection block is procedural, which is inherent to hardware timing attacks.

5 / 5

Workflow Clarity

The Quick Workflow and Engagement Checklist give a clear, coherent sequence, but destructive operations — MTD writes ('mtd_debug erase/write ... implant.bin'), re-flashing, and chip-off desoldering — lack validation/verification checkpoints (no dump-verify before write, no post-write check), capping this dimension per the destructive-operations rule.

3 / 5

Progressive Disclosure

No bundle files exist and ~430 lines covering distinct subdomains (wireless protocols, ICS/OT, RTOS, companion app/cloud) are all inlined in SKILL.md — content that clearly belongs in separate reference files; good section headers keep it navigable, which lifts it above the 'minimal structure' anchor.

3 / 5

Total

16

/

20

Passed

Description

92%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 strong description: comprehensive concrete capability coverage paired with an explicit 'Use for...' trigger clause naming the natural engagement types. The only gap is a few missing synonyms a user might naturally say, keeping trigger-term coverage just short of comprehensive.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with sub-specifics across the whole domain — 'hardware reconnaissance (UART, JTAG, SWD, SPI flash, I2C EEPROM, eMMC chip-off)', 'bootloader attacks (U-Boot console, secure-boot bypass, fault injection)', 'wireless protocol attacks (Zigbee, BLE, Z-Wave, LoRaWAN...)' — which is comprehensive rather than 'several actions with minor gaps' (the 4 anchor).

5 / 5

Completeness

It explicitly answers both: 'what' ('IoT and embedded device security testing methodology. Covers...') and 'when' with concrete triggers ('Use for IoT pentest, smart-home assessment, ICS/OT testing, or embedded vulnerability research').

5 / 5

Trigger Term Quality

Natural phrases like 'IoT pentest', 'smart-home assessment', 'ICS/OT testing', 'embedded vulnerability research' plus protocol keywords (Zigbee, BLE, MQTT, U-Boot) give good coverage, but common synonyms such as 'hardware hacking', 'device security testing', or 'penetration testing' spelled out are missing.

4 / 5

Distinctiveness Conflict Risk

A clear niche (offensive IoT/embedded testing) with highly distinctive vocabulary (UART, JTAG, binwalk, Zigbee, U-Boot) and domain-qualified triggers ('IoT pentest', 'ICS/OT testing') that keep it from firing for generic pentest or cloud skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

SnailSploit/Claude-Red

Path

Skills/iot/offensive-iot/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.