Esp32 Hardware Check
Verifies user's board configuration against known hardware limitations like strapping pins, ADC/Wi-Fi conflicts, and input-only pins.
Install
$ agentstack add skill-agodianel-esp32-claude-workbench-hardware-check ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-agodianel-esp32-claude-workbench-hardware-check) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
esp32_hardware_check Skill
You 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.
Context Needed
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.
Audit Checklist
- Input-Only Pins: Check if GPIOs 34, 35, 36 (VP), or 39 (VN) are configured as outputs or have internal pull-ups/pull-downs enabled. Rule: These must be INPUT ONLY.
- Strapping Pins: Check if GPIOs 0, 2, 5, 12, or 15 are being used. Rule: These pins control the boot state. Warn the user about potential boot failures if external components hold them in the wrong state at power-on.
- ADC2 & Wi-Fi Conflict: Check if ADC2 pins (0, 2, 4, 12, 13, 14, 15, 25, 26, 27) are used for analog measurements while Wi-Fi is enabled. Rule: ADC2 cannot be read when Wi-Fi is running. Advise moving to ADC1.
- JTAG Debugging: If the user mentions hardware debugging, check if they are using JTAG pins (12, 13, 14, 15) for other purposes.
Output Format
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)Tools Available
- Command line scripts:
scan-pinscan be run via your standard execution tools.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: agodianel
- Source: agodianel/esp32-claude-workbench
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.