esp32-firmware-engineer — Claude Code skill: features and setup
Helps build, review, and debug ESP32 firmware projects using ESP-IDF. For hardware work, it first asks about the board, chip variant, and connected devices.
npx skills add adamlipecz/esp32-firmware-engineer-skill --skill esp32-firmware-engineer -a claude-codeWhat esp32-firmware-engineer does
This skill guides ESP32 firmware work with ESP-IDF, from implementing a feature to investigating build or runtime failures. It can review synchronization logic and interpret logs, with attention to areas such as FreeRTOS, peripherals, networking, OTA, and low-power behavior as relevant to the task.
The agent first classifies the request and reads the project files needed for it. A usable ESP-IDF environment is required before build, flash, or monitor steps; it checks that idf.py runs or that the project shell wrapper can load the environment. Hardware debugging must pause if the exact chip, board wiring, or connected devices are unclear. Chip variants differ in peripherals and wake-up behavior, so guessing can send the work in the wrong direction.
For debugging, the skill calls for a failure model before code changes, then a build with build.sh. It also asks for version-specific evidence that framework components work together. A code-only review or refactor can proceed within the supplied code scope, with hardware risks noted when behavior is unchanged.
What it helps with
- implement an ESP-IDF firmware feature
- trace a boot failure or Guru Meditation panic
- review synchronization in embedded code
- interpret serial logs
- fix a build or flash failure
Example prompts for the agent
- Debug this ESP32 boot failure from the logs, and list the board details you need before changing code.
- Review this ESP-IDF change for synchronization issues and suggest a small, focused fix.
- Add this firmware feature, but first ask me for the chip variant, pin map, and OTA requirements.
How to install esp32-firmware-engineer
1Skills CLI (Vercel)
npx skills add adamlipecz/esp32-firmware-engineer-skill --skill esp32-firmware-engineer -a claude-code2Manually: put the files in place
~/.claude/skills/esp32-firmware-engineer/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/esp32-firmware-engineer/
1Skills CLI (Vercel)
npx skills add adamlipecz/esp32-firmware-engineer-skill --skill esp32-firmware-engineer -a codex2Manually: put the files in place
.agents/skills/esp32-firmware-engineer/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add adamlipecz/esp32-firmware-engineer-skill --skill esp32-firmware-engineer -a cursor2Manually: put the files in place
.cursor/skills/esp32-firmware-engineer/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install adamlipecz/esp32-firmware-engineer-skill esp32-firmware-engineer2Manually: put the files in place
.github/skills/esp32-firmware-engineer/SKILL.md1Skills CLI (Vercel)
npx skills add adamlipecz/esp32-firmware-engineer-skill --skill esp32-firmware-engineer -a gemini-cli2Platform CLI
gemini skills install https://github.com/adamlipecz/esp32-firmware-engineer-skill --path esp32-firmware-engineerManually: put the files in place
.devin/skills/esp32-firmware-engineer/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add adamlipecz/esp32-firmware-engineer-skill --skill esp32-firmware-engineer -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 esp32-firmware-engineer
How do I install esp32-firmware-engineer in Claude Code?
Run npx skills add adamlipecz/esp32-firmware-engineer-skill --skill esp32-firmware-engineer -a claude-code. The skill file is at ~/.claude/skills/esp32-firmware-engineer/SKILL.md.
What does esp32-firmware-engineer do?
It assists with ESP-IDF firmware implementation and review, and helps investigate build, runtime, and hardware integration problems.
What does it need for hardware debugging?
Provide the board and exact ESP32 variant, peripherals, pin mapping, electrical constraints, and connected devices. The ESP-IDF environment must also be usable before build, flash, or monitor work.