wedsamuel1230/arduino-skills/circuit-debugger
Claude Code and agent skill by wedsamuel1230/arduino-skills
- community
Checking that the SKILL.md file is still in the repository.
Systematic hardware debugging guide for Arduino/ESP32/RP2040 circuits. Use when user reports: circuit not working, components getting hot, no power, intermittent failures, unexpected behavior, sensor not responding, LED not lighting, motor not spinning. Guides through power checks, continuity testing, signal tracing, and component isolation using multimeter techniques.
Install
npx vskill@latest install wedsamuel1230/arduino-skills/circuit-debuggerSKILL.md
Circuit Debugger
Systematic approach to diagnosing hardware issues in maker projects.
Resources
This skill includes bundled tools and references:
- scripts/generate_debug_sketch.py - Arduino sketch generator for I2C scanner, GPIO tester, ADC checker, PWM tester
- references/measurement-procedures.md - Comprehensive multimeter and oscilloscope guide
Quick Start
Generate I2C scanner:
Generate GPIO tester:
Generate all debug sketches:
Interactive mode:
Trigger Phrases
- "My circuit doesn't work"
- "Component is getting hot"
- "No power to the board"
- "Sensor not responding"
- "Intermittent/random failures"
- "Works sometimes, not others"
Debugging Protocol
Phase 1: Power System Check (Do First!)
Visual Inspection (30 seconds)
Multimeter Tests (Set to DC Voltage)
Common Power Issues:
| Symptom | Likely Cause | Fix | |
|---|---|---|---|
| No voltage anywhere | Disconnected power, blown fuse | Check continuity from source | |
| Low voltage (< 4V when expecting 5V) | Overloaded supply, bad regulator | Reduce load, check current draw | |
| Voltage drops under load | Undersized power supply | Calculate total current, upgrade PSU | |
| Reverse polarity | Swapped wires | Check all connections, may have damaged components |
Phase 2: Ground Continuity
Check the design: Non-isolated logic normally needs a shared reference. Preserve intentional isolation; do not bond isolated/high-voltage domains just to satisfy a continuity test. Power down before continuity/resistance tests.
Ground Problems Cause:
- Erratic sensor readings
- I2C/SPI communication failures
- Motors behaving randomly
- Displays showing garbage
Phase 3: Signal Verification
Digital Signals (Set multimeter to DC Voltage)
Expected Readings:
| Signal Type | HIGH | LOW | Floating (Bad!) | |
|---|---|---|---|---|
| 5V Logic | 4.5-5.5V | 0-0.5V | 1-3V unstable | |
| 3.3V Logic | 2.8-3.6V | 0-0.3V | 0.8-2V unstable |
I2C Troubleshooting:
| I2C Problem | Check | |
|---|---|---|
| No devices found | SDA/SCL swapped? Pull-ups present? Correct address? | |
| Address conflict | Two devices same address? Check AD0/AD1 pins | |
| Intermittent | Weak pull-ups (try 4.7kΩ), long wires, noise |
Phase 4: Component Isolation
The Divide-and-Conquer Method:
Component-Specific Tests:
LEDs:
Motors/Servos:
Sensors:
Phase 5: Software vs Hardware
Quick Software Test:
| If This Works | If This Fails | |
|---|---|---|
| Hardware likely OK, check your code | Check USB cable, bootloader, board selection |
Quick Reference: Common Failures
| Symptom | First Check | Second Check | Third Check | |
|---|---|---|---|---|
| Nothing works | Power supply | USB cable | Board selection in IDE | |
| Gets hot | Short circuit | Reversed polarity | Overcurrent | |
| Works then stops | Power brownout | Overheating | Memory leak | |
| Erratic behavior | Floating inputs | Missing grounds | Noise/interference | |
| I2C fails | Pull-ups | Address | Wire length | |
| Motor jerky | Power supply | PWM frequency | Driver current |
Multimeter Quick Guide
When to Ask for Help
If after this protocol you still can't find the issue:
- Take clear photos of your wiring
- Draw a schematic (even hand-drawn)
- List exact components with part numbers
- Share your complete code
- Describe what you expected vs what happened
References
- See references/multimeter-guide.md for detailed measurement techniques
- See references/common-mistakes.md for beginner pitfall gallery
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.
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/circuit-debugger/SKILL.md
Popularity
- Repository stars
- 12
- 7-day trend score
- 13
Stars and forks are for the whole GitHub repository, not this skill alone. Refreshed 17 Apr 2026, 6 months ago.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/wedsamuel1230/arduino-skills/circuit-debugger)