Embedded Systems
Use when developing firmware for microcontrollers, implementing RTOS applications, or optimizing power consumption.
Before & after
Same prompt, same agent — the only difference is the skill.
Building a low-power sensor logger is a classic embedded systems project. You'll need to think about several things: selecting the right microcontroller for your power budget, configuring the sensor interface (I2C or SPI), setting up interrupts or timers for sampling, and implementing some form of storage. Power optimization is key—you'll probably want to use sleep modes, disable unused peripherals, and maybe manage the clock frequency. You'd also want to consider data storage, whether on flash or external memory. If you let me know what sensors you're using, your target battery life, and your storage requirements, I can help you design something more specific.
LOW-POWER SENSOR LOGGER ARCHITECTURE MICROCONTROLLER CONFIG • MCU: STM32L476 (ultra-low-power, 32KB RAM, 256KB flash) • Clock: 16 MHz HSI (sufficient for sensor read rate) • Sleep mode: STOP2 (0.9 µA consumption, RTC wakeup active) PERIPHERAL SETUP • I2C sensor interface: DMA-driven (no CPU polling) • Timer interrupt: Every 60 seconds, wakes MCU from STOP2 • UART: Used only for config, disabled during logging (saves 1 mA) • Unused peripherals: ADC, SPI disabled at startup DMA TRANSFER PATTERN 1. Timer triggers ADC conversion (DMA writes to sensor register) 2. I2C DMA reads sensor data (interrupt on completion) 3. CPU wakes on interrupt, copies data to ring buffer (SD card write batched) 4. CPU returns to STOP2 POWER PROFILE • Active (sensor read + write): 12 mA, 50 ms duration • Sleep (STOP2): 0.9 µA • Cycle: Read every 60 sec = avg 10 µA (10 mAh per day from 2000 mAh battery = 200 day runtime) STORAGE • Ring buffer: 512-byte on-chip (SPI flash fallback if SD card fails) • Batch write: Every 10 reads (reduces SD card power overhead) • Format: Binary + CRC per record (faster parse, ~100 bytes per reading) DEBUG: pprof endpoint logs latency, sleep-wake transitions, battery voltage every log cycle
About this skill
name: embedded-systems description: Use when Use when developing firmware for microcontrollers, implementing RTOS applications, or optimizing power consumption.
Embedded Systems
Use when developing firmware for microcontrollers, implementing RTOS applications, or optimizing power consumption. Invoke for STM32, ESP32, FreeRTOS, bare-metal, power optimization, real-time systems, configure peripherals, write interrupt handlers, implement DMA transfers, debug timing issues.
What you get
- Public GitHub repo
- the skills/embedded-systems folder with SKILL.md and references.
Customize your output
- Fork the repo and extend the skill's reference files for your own stack conventions.
Example output
Activates on a matching request (e.g. building or reviewing Embedded Systems code) and can chain with other skills in the pack.
Best for
Full-stack developers and engineering teams using Claude Code.
SKILL.md preview
---
name: embedded-systems
description: Use when developing firmware for microcontrollers, implementing RTOS applications, or optimizing power consumption on embedded hardware.
version: 1.0.0
category: Development / Engineering
author: AgentVolt
license: proprietary
tags:
- development
- engineering
---
# Embedded Systems
Develops firmware for microcontrollers, implements RTOS applications, and optimizes power consumption, covering STM32, ESP32, FreeRTOS, and bare-metal work.
## When to use
… (sign up to view the full skill)More development skills
View all Development skills →Generate
Scaffold code, tests, and boilerplate from a short spec.
Performance Profiler
Systematic performance profiling for Node.js, Python, and Go applications.
Threat Detection
Use when hunting for threats in an environment, analyzing IOCs, or detecting behavioral anomalies in telemetry.
Agent Harness
Turns a domain folder of skills into a bounded agentic loop: compile a goal into a task plan, execute with the domain's tools, verify every task, retry within a budget.