사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/wedsamuel1230/embedded-engineering-skills --skill i2c-bringup-diagnostician시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
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 workflowreferences/scanner-vs-library.md- what to do when the scanner finds the device but the library still failsreferences/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
- 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
- Confirm the electrical basics before library swapping:
- power
- common ground
- SDA and SCL mapping
- pull-ups
- logic level compatibility
- Only after the bus is electrically plausible, check address, device mode, and
library expectations.
- 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-debuggerfor deeper hardware isolation. - Pair with
datasheet-interpreterwhen the correct address, power, or timing
details are not known.
- Pair with
arduino-code-generatorwhen the user needs a minimal test sketch or
a cleaned-up bus probe.
Shared Output Contract
Use the shared Arduino skill contract: state assumptions, required tools and versions, implementation steps, tests/evidence by proof stage, known limitations, and recovery/security notes.
