GPIO Config
GPIO pin assignment, conflict validation, and init code for Pi and ESP32.
Test report
- Verdict
- Works with setup
- Score
- Tested
- Jul 15, 2026
- Environment
- Claude Code 2.x (agent harness)
- Upstream re-checked
- Aug 10, 2026 · 084a891
Real, working pin-safety logic — validate_pinmap.py correctly caught a GPIO2 strapping-pin hazard on an ESP32 status LED that a naive baseline answer would have missed. But the script crashes on the exact JSON the docs teach: SKILL.md's own schema and worked Section-8 example pass protocol_bus as an integer (0, 1), while the code calls protocol_bus.lower() expecting a string like "i2c" — AttributeError: 'int' object has no attribute 'lower'. Fix is to pass protocol_bus as a lowercase protocol name string, undocumented.
Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works
- Installs cleanly 5/5
- Triggers reliably 5/5
- Output vs. baseline 7/10
- Docs & honesty 2/5
What GPIO Config does
Assigns and validates GPIO pin maps for Raspberry Pi and ESP32 boards, flagging strapping pins, flash-reserved pins, and current-budget issues before they brick hardware. Triggers on GPIO/wiring/pin-conflict questions or when a named sensor/board pair (e.g. 'BME280 on a Pi 4') implies pin selection, and generates gpiozero/RPi.GPIO/Arduino/ESP-IDF init code.
How to install GPIO Config
git clone https://github.com/claudius-ars/embedded-agent-skills
cd embedded-agent-skills
mkdir -p ~/.claude/skills
cp -r embedded-agent-skills/gpio-config ~/.claude/skills/gpio-config
Skills live in ~/.claude/skills/ (global) or .claude/skills/
(per-project). Restart Claude Code after installing.
Commands — how to trigger GPIO Config
-
/gpio-configGPIO pin assignment, conflict validation, and init code for Pi and ESP32.
It also activates on plain-language prompts like these:
-
Wire a BME280 and an SSD1306 OLED to my ESP32 over I2C, give me the pins -
Check this Raspberry Pi pinout for strapping-pin or current-budget conflicts -
Generate gpiozero init code for a sensor I'm wiring to a Pi 4
Frequently asked questions
- Is the GPIO Config skill free?
- Yes. The skill itself is free from claudius-ars/embedded-agent-skills. SkillProof publishes the install command and an independent test verdict at no cost.
- Does GPIO Config work with Claude Code?
- We tested it with Claude Code 2.x (agent harness) on Jul 15, 2026. Verdict: Works with setup. Real, working pin-safety logic — validate_pinmap.py correctly caught a GPIO2 strapping-pin hazard on an ESP32 status LED that a naive baseline answer would have missed. But the script crashes on the exact JSON the docs teach: SKILL.md's own schema and worked Section-8 example pass protocol_bus as an integer (0, 1), while the code calls protocol_bus.lower() expecting a string like "i2c" — AttributeError: 'int' object has no attribute 'lower'. Fix is to pass protocol_bus as a lowercase protocol name string, undocumented.
- What is the GPIO Config SkillProof Score?
- 7.6/10 — installs cleanly 5/5, triggers reliably 5/5, output vs. baseline 7/10, docs & honesty 2/5.
- How do I install GPIO Config?
- Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
- Can I use GPIO Config with Cursor, Copilot, Gemini CLI, Codex or other AI tools?
- The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.