embedded-iot — Claude Code skill: firmware, RTOS and IoT
embedded-iot — a skill for firmware work: GPIO, I2C and MQTT patterns, FreeRTOS tasks and power rules for ESP32, STM32 and Arduino boards.
MIT 212 installs ★ 114 updated 2026-10-25
npx skills add travisjneuman/.claude --skill embedded-iot -a claude-codeWhat embedded-iot does
The skill hands the agent a reference on firmware work. One table maps boards to jobs: ESP32 for WiFi and BLE, STM32 where real-time response matters, Arduino for quick prototypes, the RP2040-based Pico, nRF52 for BLE gear. Each row also names the language, C/C++ or MicroPython, and the toolchain, from PlatformIO to STM32CubeIDE and the nRF Connect SDK.
Code samples come in C: GPIO setup with ESP-IDF, a sensor register read over I2C, a FreeRTOS task feeding a queue, a mutex around SPI, an MQTT client publishing to /sensors/temp. A second table sorts protocols by transport. MQTT rides TCP/TLS, CoAP sits on UDP/DTLS, BLE and LoRaWAN go over radio, Matter over IP.
The samples call ESP-IDF directly, so an Arduino core or a Zephyr port means rewriting them. On practice the skill pushes a watchdog timer and OTA through two partitions that roll back when boot fails. Static allocation gets the nod too, since heap fragmentation is what bites on a microcontroller.
What it helps with
- Wire up a GPIO and poll a sensor over I2C on ESP32
- Split the work into FreeRTOS tasks with a queue and a mutex
- Publish telemetry through an MQTT client
- Pick a protocol for a constrained device: MQTT, CoAP, BLE or LoRaWAN
- Plan OTA with dual partitions and a boot rollback
Example prompts for the agent
- Set up GPIO on the ESP32 with ESP-IDF and read the temperature sensor over I2C
- Write a FreeRTOS task that pushes a reading into a queue every second and guard SPI with a mutex
- Start an MQTT client and publish telemetry to
/sensors/temp
How to install embedded-iot
1Skills CLI (Vercel)
npx skills add travisjneuman/.claude --skill embedded-iot -a claude-code2Manually: put the files in place
~/.claude/skills/embedded-iot/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/embedded-iot/
1Skills CLI (Vercel)
npx skills add travisjneuman/.claude --skill embedded-iot -a codex2Manually: put the files in place
.agents/skills/embedded-iot/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add travisjneuman/.claude --skill embedded-iot -a cursor2Manually: put the files in place
.cursor/skills/embedded-iot/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install travisjneuman/.claude skills/embedded-iot2Manually: put the files in place
.github/skills/embedded-iot/SKILL.md1Skills CLI (Vercel)
npx skills add travisjneuman/.claude --skill embedded-iot -a gemini-cli2Platform CLI
gemini skills install https://github.com/travisjneuman/.claude --path skills/embedded-iotManually: put the files in place
.devin/skills/embedded-iot/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add travisjneuman/.claude --skill embedded-iot -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about embedded-iot
How do I install embedded-iot in Claude Code?
Run npx skills add travisjneuman/.claude --skill embedded-iot -a claude-code. The skill file lands at ~/.claude/skills/embedded-iot/SKILL.md.
What does the embedded-iot skill do?
It gives the agent ready patterns for firmware: peripheral setup, RTOS tasks, IoT protocol work, plus rules on power, watchdogs and OTA updates.
Which boards and RTOSes does it cover?
ESP32, STM32, Arduino, Raspberry Pi Pico and nRF52, with FreeRTOS and Zephyr on the RTOS side. Code is in C/C++ or MicroPython.
Source text
SKILL.md · MIT
---
name: embedded-iot
description: Embedded systems firmware, microcontrollers (ESP32, STM32, Arduino, Raspberry Pi), RTOS (FreeRTOS, Zephyr), IoT protocols (MQTT, CoAP, BLE), bare-metal C/C++, and hardware peripheral interfaces (I2C, SPI, UART, GPIO). Use when developing firmware, working with microcontrollers, or building IoT devices.
---
# Embedded Systems & IoT
## Microcontroller Platforms
| Platform | Best For | Language | IDE |
|----------|----------|----------|-----|
| **ESP32** | WiFi/BLE IoT devices | C/C++, MicroPython | PlatformIO, Arduino IDE |
| **STM32** | Industrial, real-time | C/C++ | STM32CubeIDE, PlatformIO |
| **Arduino** | Prototyping, learning | C++ (Arduino) | Arduino IDE, PlatformIO |
| **Raspberry Pi Pico** | RP2040, dual-core | C/C++, MicroPython | Thonny, VS Code |
| **nRF52** | BLE-focused IoT | C, Zephyr | nRF Connect SDK |
## Firmware Patterns
### GPIO & Peripherals
```c
// ESP-IDF GPIO example
gpio_config_t io_conf = {
.pin_bit_mask = (1ULL << GPIO_NUM_2),
.mode = GPIO_MODE_OUTPUT,
.pull_up_en = GPIO_PULLUP_DISABLE,
.pull_down_en = GPIO_PULLDOWN_DISABLE,
.intr_type = GPIO_INTR_DISABLE,
};
gpio_config(&io_conf);
gpio_set_level(GPIO_NUM_2, 1);
```
### I2C Communication
```c
// Read sensor via I2C
i2c_cmd_handle_t cmd = i2c_cmd_link_create();
i2c_master_start(cmd);
i2c_master_write_byte(cmd, (SENSOR_ADDR << 1) | I2C_MASTER_WRITE, true);
i2c_master_write_byte(cmd, REG_TEMP, true);
i2c_master_start(cmd);
i2c_master_write_byte(cmd, (SENSOR_ADDR << 1) | I2C_MASTER_READ, true);
i2c_master_read(cmd, data, 2, I2C_MASTER_LAST_NACK);
i2c_master_stop(cmd);
i2c_master_cmd_begin(I2C_NUM_0, cmd, pdMS_TO_TICKS(1000));
i2c_cmd_link_delete(cmd);
```
## RTOS (FreeRTOS)
```c
// Task creation
void sensor_task(void *pvParameters) {
while (1) {
float temp = read_temperature();
xQueueSend(data_queue, &temp, portMAX_DELAY);
vTaskDelay(pdMS_TO_TICKS(1000));
}
}
xTaskCreate(sensor_task, "sensor", 4096, NULL, 5, NULL);
// Mutex for shared resources
SemaphoreHandle_t spi_mutex = xSemaphoreCreateMutex();
if (xSemaphoreTake(spi_mutex, pdMS_TO_TICKS(100)) == pdTRUE) {
spi_transfer(data);
xSemaphoreGive(spi_mutex);
}
```
## IoT Protocols
### MQTT
```c
// ESP-IDF MQTT client
esp_mqtt_client_config_t mqtt_cfg = {
.broker.address.uri = "mqtt://broker.hivemq.com",
};
esp_mqtt_client_handle_t client = esp_mqtt_client_init(&mqtt_cfg);
esp_mqtt_client_start(client);
esp_mqtt_client_publish(client, "/sensors/temp", "23.5", 0, 1, 0);
```
### Key IoT Protocols
| Protocol | Transport | Use Case |
|----------|-----------|----------|
| **MQTT** | TCP/TLS | Pub/sub messaging, telemetry |
| **CoAP** | UDP/DTLS | Constrained devices, REST-like |
| **BLE** | Radio | Short-range, low power |
| **LoRaWAN** | Radio | Long-range, low data rate |
| **Matter** | IP | Smart home interoperability |
## Best Practices
- **Power management:** Deep sleep modes, wake-on-interrupt, duty cycling
- **Watchdog timers:** Always enable, reset periodically, catch firmware hangs
- **OTA updates:** Dual partition scheme, rollback on boot failure, signature verification
- **Memory:** Static allocation preferred, avoid heap fragmentation, use memory pools
- **Testing:** Hardware-in-the-loop (HIL), mock hardware interfaces for unit tests
© travisjneuman · MIT · travisjneuman/.claude