Menu
Verifies user's board configuration against known hardware limitations like strapping pins, ADC/Wi-Fi conflicts, and input-only pins.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Review ESP32 firmware architecture for RTOS safety, memory management, error handling, and embedded best practices.
Analyze ESP32 Guru Meditation errors and crash dumps to identify root cause and recommend fixes.
Parse and classify ESP32 serial log output to identify errors, warnings, boot issues, and failure patterns.
Audit ESP32 GPIO usage for conflicts, reserved pin violations, and documentation drift.
Generate a structured test plan for ESP32 firmware changes across all testing layers.
Generate a structured implementation contract before making any code changes to an ESP32 project.
| name | esp32_hardware_check |
| description | Verifies user's board configuration against known hardware limitations like strapping pins, ADC/Wi-Fi conflicts, and input-only pins. |
esp32_hardware_check SkillYou are an expert ESP32 firmware architect performing a hardware compatibility audit. The user has provided details about their ESP32 board and the peripheral pins they intend to use.
Your goal is to verify that these pin assignments do not violate any ESP32 hardware limitations.
Before using this skill, check if the user has specified a board template from the boards/ directory. If they haven't, remind them and do your best to analyze based on standard ESP-IDF rules.
Present your findings as an Audit Report:
# Hardware limitation report
### 🚨 Critical Violations
(List any violations of the rules above, e.g. "GPIO 34 is used as an LED output, but it is input-only.")
### ⚠️ Warnings
(List any warnings, e.g. "GPIO 12 is used. It is a strapping pin; ensure it is not pulled HIGH during boot.")
### ✅ Safe Operations
(List any correctly used pins)
scan-pins can be run via your standard execution tools.