11 skills · category

Embedded & IoT skills for Claude Code

Skills for firmware and connected devices: Arduino and ESP32, Raspberry Pi, FreeRTOS and Zephyr, embedded Rust with embassy, I2C/SPI/UART debugging, MQTT messaging, low-power design measured in microamps, and over-the-air updates that can roll back.

Download all 11 (.zip) Browse the list

Every embedded & iot skill

Each card opens the full playbook, example prompts and install commands.

No. 457

Arduino Projects

Sketches that never block and never cook a pin

Claude writes Arduino sketches as small non-blocking tasks driven by millis(), debounces inputs, keeps ISRs to a flag, and avoids heap fragmentation on 2 KB AVRs. Before any wiring advice it checks logic voltage and per-pin current, insists on drivers and flyback diodes for inductive loads, and builds with arduino-cli using pinned core and library versions.

arduino-projects 225 lines

No. 458

Embedded Rust

no_std firmware with one owner per peripheral

Claude sets up no_std firmware with the right target triple, pinned toolchain, probe-rs runner and defmt logging, then structures concurrency as embassy tasks that own their peripherals and talk over channels. Drivers are written generically over embedded-hal 1.0 and tested on the host with mocks, memory stays static with heapless and StaticCell, and release builds are checked for size and stack headroom.

embedded-rust 227 lines

No. 459

ESP32 Firmware

Wi-Fi that reconnects, partitions that still fit

Claude pins the chip target and ESP-IDF version, keeps configuration in sdkconfig.defaults, writes Wi-Fi code that logs disconnect reasons and retries with backoff, sizes partition tables with OTA headroom, and versions NVS settings. It flags strapping pins and brownout causes before blaming code, and refuses to burn eFuses for secure boot or flash encryption without explicit sign-off.

esp32-firmware 218 lines · 2 files

★ No. 460

Firmware OTA Updates

Updates that survive power cuts and bad builds

Claude designs OTA so a device always boots something that works: A/B slots, bootloader signature checks, anti-downgrade rules, and a self-test that must pass before the image is confirmed. It writes the confirm and rollback code for ESP-IDF and MCUboot, generates release manifests, runs a power-cut test matrix, and plans staged rollouts with numeric halt gates.

firmware-ota 212 lines · 2 files

No. 461

FreeRTOS Tasks

Tasks that block, ISRs that defer, stacks that fit

Claude designs FreeRTOS systems from a task table of triggers, deadlines and priorities, picks the right primitive per data path (task notifications, queues, stream buffers, mutexes), keeps ISRs to capture-and-notify, and sizes stacks from measured high-water marks with overflow hooks enabled. It diagnoses starvation, priority inversion, deadlocks and ISR priority asserts systematically.

freertos-tasks 206 lines

No. 462

Low-Power Firmware

Measured microamps, not datasheet wishes

Claude builds a per-state power budget from profiler measurements, computes average current and battery life with derating and self-discharge, and attacks the biggest consumer first, usually radio time. It hunts hidden drains such as regulator quiescent current, always-on dividers, floating pins and attached debug probes, and picks sleep modes and wake sources per MCU.

low-power-firmware 196 lines · 2 files

No. 463

MQTT for IoT

Topics, QoS and ACLs that scale past ten devices

Claude designs MQTT systems from a message catalog: one topic scheme with the device ID in a fixed level, a stated QoS and retain choice per message, retained status driven by last will, and commands with expiry and idempotency. It configures Mosquitto or EMQX with TLS, per-device credentials and ACL patterns, and proves isolation with explicit denial tests.

mqtt-iot 194 lines · 2 files

No. 464

Raspberry Pi Projects

Headless Pi builds that survive a pulled plug

Claude sets up a Pi headless with Imager customisation and NetworkManager, writes GPIO code with gpiozero so it runs on Pi 5 where RPi.GPIO fails, checks 3.3 V and per-pin current limits before wiring advice, and ships the app as a systemd service under a dedicated user. It checks undervoltage with vcgencmd and limits SD card writes so the device survives power cuts.

raspberry-pi-projects 202 lines

No. 465

Serial Protocols

Capture the bus before blaming the firmware

Claude treats serial bus failures as physical-layer problems first: it checks ground, voltage levels and wiring, sizes I2C pull-ups from the spec's rise-time and sink-current limits with a bundled calculator, checks UART baud error per divisor scheme, and reads decoded logic analyzer captures against the datasheet before touching driver code.

serial-protocols 162 lines · 3 files

No. 466

STM32 HAL Firmware

CubeMX projects that survive regeneration and real traffic

Claude treats the .ioc as the source of truth, keeps user code inside USER CODE blocks, and verifies the clock tree on a pin. Peripherals run on interrupts or DMA with error callbacks that recover, NVIC priorities are tabulated against the FreeRTOS syscall ceiling, and a bundled map-file script shows exactly where flash and RAM went.

stm32-hal 246 lines · 2 files

No. 467

Zephyr RTOS

Devicetree and Kconfig without the guesswork

Claude sets up a pinned west workspace, describes hardware in board overlays instead of C constants, enables the minimal Kconfig set, and uses DT-spec driver APIs with readiness checks. When builds or devices fail it reads the generated zephyr.dts and .config first, then fixes compatibles, status, or dependencies. Logic is tested on native_sim with twister.

zephyr-rtos 243 lines

Choosing Embedded & IoT skills

Install the skills that match requests you make every week; each costs about 100 tokens of standing context until it loads. If you are not sure where to begin, start with Firmware OTA Updates. For background, read The Best Claude Code Skills in 2026, by Use Case, How to Install Claude Code Skills (5 Ways) and Personal vs Project Skills.

By technology: ESP32 and Arduino skills

Install several

Install several at once

The installer accepts any number of skill names. Add --project to install into the current repository.

curl -fsSL https://claudeskills.page/install.sh | sh -s -- arduino-projects embedded-rust esp32-firmware firmware-ota freertos-tasks low-power-firmware mqtt-iot raspberry-pi-projects serial-protocols stm32-hal zephyr-rtos

Embedded & IoT skills FAQ

How do I install every Embedded & IoT skill at once?

Download the bundle at https://claudeskills.page/downloads/category/embedded.zip and unzip it into ~/.claude/skills/ (or .claude/skills/ inside a repository). To pick a few, pass several names to the installer: curl -fsSL https://claudeskills.page/install.sh | sh -s -- arduino-projects embedded-rust esp32-firmware.

Will installing 11 skills slow Claude Code down?

No. Claude Code keeps only each skill's short description in context — roughly 100 tokens per skill — and loads the full instructions only when a request matches. Install the whole category if it fits your work; unused skills cost almost nothing.

Which Embedded & IoT skill should I start with?

Start with Firmware OTA Updates. They cover the most common requests in this category; add the rest as your work calls for them.