Loading...
Loading...
Found 13 Skills
ESP32 firmware engineering for ESP-IDF projects. Write, review, and debug embedded C/C++ code involving FreeRTOS tasks/queues/timers, GPIO/I2C/SPI/UART/ADC/PWM peripherals, TWAI/CAN, Wi-Fi/BLE networking, OTA updates, Secure Boot and flash encryption, LVGL display integration, build/flash/monitor workflows, logging, crash analysis, memory/code-size optimization, low-power sleep/wakeup design, on-device USB/serial service terminals, and board bring-up. Use when an agent is asked to implement ESP-IDF firmware features, review embedded changes for correctness or race conditions, investigate boot/runtime failures or Guru Meditation panics, interpret serial logs, fix build/link/flash problems, optimize RAM/flash usage, tune deep sleep/light sleep behavior, harden firmware for production, add a service console/CLI, integrate a display with LVGL, or diagnose hardware-software integration issues on ESP32-class devices.
Rust no_std skill for embedded and bare-metal development. Use when writing
Rust cross-compilation skill. Use when building Rust binaries for a different target architecture or OS, using cross or cargo-zigbuild for hermetic cross-compilation, configuring .cargo/config.toml for cross targets, or targeting embedded and bare-metal systems. Activates on queries about Rust cross-compilation, rustup targets, cross tool, cargo-zigbuild, aarch64-unknown-linux-gnu, thumbv7m-none-eabi, or building for embedded.
Zephyr RTOS skill for embedded development. Use when building Zephyr applications with west, configuring boards and targets, working with Kconfig and devicetree, using the Zephyr shell and logging subsystem, or running on the native_sim target. Activates on queries about Zephyr, west build, Kconfig, devicetree, Zephyr logging, west flash, board targets, or native POSIX simulation.
Linker script skill for embedded bare-metal targets. Use when writing or modifying GNU ld linker scripts, placing code and data in specific flash or RAM regions, understanding VMA vs LMA, configuring startup .bss/.data initialization, using MEMORY and SECTIONS commands, or debugging linker errors about regions. Activates on queries about linker scripts, MEMORY command, SECTIONS command, .bss init, VMA vs LMA, weak symbols, or placing functions in specific memory regions.
This is used when you need to compile embedded projects via the PlatformIO command line, call the built-in script to parse environment configurations, execute builds, and locate firmware artifacts.
Authoritative MCU chip specification query Skill. Auto-activates when users work with MCU/embedded development, chip selection, hardware design, or peripheral configuration. Queries chip parameters, pin definitions, TRM registers, and programming guides via the ChipCtx MCP interface. Trigger keywords: chip models (STM32/ESP32/nRF, etc.), pin definitions, peripheral configuration, UART/SPI/I2C/ADC, registers, datasheets.
Used when you need to chain multiple skills to complete pipeline tasks such as compilation + flashing + monitoring or compilation + flashing + debugging.
Keil MDK project build tool, used to scan .uvprojx/.uvmpw projects, enumerate Targets, execute build/rebuild/clean and parse build logs, return artifact paths that can be reused by jlink/openocd. The flash subcommand is only retained as a compatibility entry. It is automatically triggered when users mention Keil, MDK, uVision, UV4, Target enumeration, compilation, rebuild, clean, flash, firmware download, or flash. It also supports explicit invocation via /keil. Even if users only say "compile" or "flash to the board", this skill should be triggered as long as the context involves embedded Keil projects.
Used when you need to compile embedded projects via the Keil MDK command line, call built-in scripts to parse project files, execute builds, and locate firmware artifacts.
Used when firmware needs to be flashed to the target board via PlatformIO, which automatically completes the flashing using the upload configuration in platformio.ini.
Used when performing GDB debugging on target boards via PlatformIO's built-in debugging features, supporting download-and-halt, attach-only, and crash context analysis.