i2c-bringup-diagnostician — Claude Code skill: setup & overview
i2c-bringup-diagnostician diagnoses I2C bring-up failures on Arduino and ESP32 boards, covering wiring, scanner mismatches, and driver bugs.
MIT 134 installs ★ 33 updated 2026-10-15
npx skills add wedsamuel1230/embedded-engineering-skills --skill i2c-bringup-diagnostician -a claude-codeWhat i2c-bringup-diagnostician does
This skill guides the assistant through a structured I2C troubleshooting workflow. When address scanners fail, libraries cannot initialize detected parts, or multiple chips collide on the bus, it enforces hardware checks first. Ground connections, voltage levels, pin mapping, and pull-up resistors get verified before touching driver code.
The logic separates raw electrical faults from software bugs. A successful scan does not guarantee that a library reads registers properly, while driver failures do not necessarily mean damaged silicon. Board-family guides handle ESP32 pin selection and multi-channel quirks, along with Arduino Uno R4 notes.
Without valid bus voltages and pull-ups confirmed early, debugging firmware libraries leads nowhere. For complex setups, this diagnostics flow connects directly with circuit-debugger and datasheet-interpreter.
What it helps with
- Fix I2C scanner detecting nothing on custom board wiring
- Isolate library init failures when the scanner already detects the target address
- Verify pull-up resistor values and logic level matching on SDA and SCL lines
- Resolve pin assignments and secondary bus issues on ESP32 boards
- Trace conflicting addresses when two peripherals share one I2C channel
Example prompts for the agent
- The scanner finds address 0x3C on my ESP32, but the display library fails to begin
- I get no I2C devices found on my Arduino Uno R4 setup, help me debug the bus
- Check why my sensor drops off the I2C bus after running for a few seconds
How to install i2c-bringup-diagnostician
1Skills CLI (Vercel)
npx skills add wedsamuel1230/embedded-engineering-skills --skill i2c-bringup-diagnostician -a claude-code2Manually: put the files in place
~/.claude/skills/i2c-bringup-diagnostician/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/i2c-bringup-diagnostician/
1Skills CLI (Vercel)
npx skills add wedsamuel1230/embedded-engineering-skills --skill i2c-bringup-diagnostician -a codex2Manually: put the files in place
.agents/skills/i2c-bringup-diagnostician/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add wedsamuel1230/embedded-engineering-skills --skill i2c-bringup-diagnostician -a cursor2Manually: put the files in place
.cursor/skills/i2c-bringup-diagnostician/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install wedsamuel1230/embedded-engineering-skills skills/i2c-bringup-diagnostician2Manually: put the files in place
.github/skills/i2c-bringup-diagnostician/SKILL.md1Skills CLI (Vercel)
npx skills add wedsamuel1230/embedded-engineering-skills --skill i2c-bringup-diagnostician -a gemini-cli2Platform CLI
gemini skills install https://github.com/wedsamuel1230/embedded-engineering-skills --path skills/i2c-bringup-diagnosticianManually: put the files in place
.devin/skills/i2c-bringup-diagnostician/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add wedsamuel1230/embedded-engineering-skills --skill i2c-bringup-diagnostician -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 i2c-bringup-diagnostician
How to install i2c-bringup-diagnostician in Claude Code?
Run npx skills add wedsamuel1230/embedded-engineering-skills --skill i2c-bringup-diagnostician -a claude-code in your terminal.
What does i2c-bringup-diagnostician do?
It provides ordered fault isolation for I2C issues across Arduino and ESP32 platforms, inspecting bus power, pull-ups, and library logic.
Does this skill work with multiple I2C buses on ESP32?
Yes, its workflow explicitly accounts for ESP32 multi-bus routing, pin choices, and variant-specific peripheral behaviors.
Source text
SKILL.md · MIT
---
name: i2c-bringup-diagnostician
description: Use when users need to diagnose I2C bring-up failures on Arduino or ESP32-class boards, including no devices found, wrong readings, address conflicts, scanner-detects-but-library-fails cases, pull-up problems, or board-family-specific bus quirks.
metadata: {triggers: "I2C failure, address conflict, pull-up, scanner, bus bring-up"}
---
# I2C Bringup Diagnostician
Use this skill when the sensor or device should be on the bus, but the I2C path
is still not trustworthy.
## Resources
- `references/bringup-flow.md` - ordered I2C fault-isolation workflow
- `references/scanner-vs-library.md` - what to do when the scanner finds the device but the library still fails
- `references/esp32-and-board-quirks.md` - ESP32-family and board-specific caveats
- `../../docs/board-support/uno-r4-family.md` - Uno R4 family board notes when relevant
## When to Use
Use this skill when the request includes:
- "no I2C devices found"
- scanner finds the address but the library cannot initialize the device
- two I2C devices conflict or one disappears
- ESP32 pin, bus, or second-channel confusion
- pull-up, wire-length, or voltage-level questions
- obviously wrong sensor values after basic detection succeeds
## Workflow
1. Establish the basic failure shape:
- no scanner detection -> open `references/bringup-flow.md`
- scanner detects but library fails -> open
`references/scanner-vs-library.md`
- ESP32-family multi-bus or pin issue -> open
`references/esp32-and-board-quirks.md`
2. Confirm the electrical basics before library swapping:
- power
- common ground
- SDA and SCL mapping
- pull-ups
- logic level compatibility
3. Only after the bus is electrically plausible, check address, device mode, and
library expectations.
4. If the board is Uno R4 family and the failure involves board-specific I2C or
support questions, also open `../../docs/board-support/uno-r4-family.md`.
## Core Rules
- Scanner success does not prove the library is using the device correctly.
- Library failure does not prove the sensor is dead.
- Bus voltage, pull-ups, and pin mapping must be explicit before changing code
blindly.
- For ESP32-family boards, pin choices and multi-bus assumptions are not always
portable across variants.
## Verification
- Confirm whether the scanner sees the expected address.
- Confirm whether a minimal register or identification read works.
- Confirm whether the failing behavior tracks a board family, bus instance, or
library rather than the sensor alone.
- Confirm whether the final fix survives repeated scans and actual sensor reads.
## Integration
- Pair with `circuit-debugger` for deeper hardware isolation.
- Pair with `datasheet-interpreter` when the correct address, power, or timing
details are not known.
- Pair with `arduino-code-generator` when the user needs a minimal test sketch or
a cleaned-up bus probe.
## Shared Output Contract
Use [the shared Arduino skill contract](../../docs/arduino-skill-contract.md):
state assumptions, required tools and versions, implementation steps,
tests/evidence by proof stage, known limitations, and recovery/security notes.
© wedsamuel1230 · MIT · wedsamuel1230/embedded-engineering-skills