- Home
- Skills
- Testing & Debugging
- Copperwright: KiCad & ESP32 Board Audits Before You Order
More screenshots
Works with the AI Agents you already use
Copperwright: KiCad & ESP32 Board Audits Before You Order
The expensive mistakes on a small board are rarely exotic: an LED on a boot strap, an EN pin with no RC, a missing 100 nF, an I²C bus with no pull-up.
$19
Copperwright: KiCad & ESP32 Board Audits Before You Order
Example session with this skill installed
Audit sensor_node before I order it from JLCPCB: check the schematic netlist and the ESP32-S3 pins (U1).
- Read your context and instructions
- Compiled the copperwright
Summary
Two audits on the exported netlist found five errors that ERC does not report: a single-pin LED net, a 3V3 pin with only a 22 µF bulk capacitor, an I²C clock with no pull-up, an LED that holds the GPIO0 boot strap low, and an EN pin with no RC delay capacitor.
Netlist audit
$ netlist_audit.py --netlist sensor_node.xml
ERROR single_pin_net ref=U1 pin=38 net=LED_STATUS: expected labelled net with >=2 pins, got 1 pin
ERROR decoupling ref=U1 pin=2 net=+3V3: expected >=1 capacitor <= 1µF (e.g. 100nF) to GND, got C2=22µF
-> Add a 100 nF capacitor from +3V3 to GND next to U1 pin(s) 2.
ERROR i2c_pullups net=I2C_SCL: expected exactly one pull-up to a rail, got none
-> Add one pull-up (e.g. 4.7k for fast mode) from I2C_SCL to the I/O rail.
FAIL: 12 checks, 3 errors, 0 warnings
ESP32-S3 pin audit
$ esp32_pin_audit.py --netlist sensor_node.xml --ref U1 --chip esp32s3
ERROR strap_level ref=U1 pin=27(GPIO0) net=BOOT: expected level 1 at reset, got 0
— LED R3+D1 to GND clamps the pin low -> Move LED R3+D1 off GPIO0, or buffer it with a transistor
ERROR en_rc ref=U1 pin=3(EN) net=EN: expected R≈10kΩ to 3V3 and C≈1µF to GND (RC delay),
got missing C to GND; pull-ups [('R1', '10kΩ')], caps [] -> Add 1 µF from EN to GND near the module.
FAIL: 8 checks, 2 errors, 0 warnings
| Finding | Where | Fix |
|---|---|---|
| No local decoupling | U1 pin 2, +3V3 | 100 nF to GND next to the pin |
| No I²C pull-up | I2C_SCL | one 4.7 kΩ to the I/O rail (fast mode) |
| Boot strap held low | GPIO0 via R3+D1 | move the LED or buffer it |
| No EN delay | EN | 1 µF to GND near the module |
| Single-pin net | LED_STATUS, U1 pin 38 | connect or remove the label |
Next steps
- Fix the five findings in the schematic and re-run both audits until they pass.
- Then run ERC/DRC with the JLCPCB 2-layer rules and generate the BOM and CPL.
Connects securely to your tools. The creator never sees your data.
About this skill
The expensive mistakes on a small board are rarely exotic: an LED on a boot strap, an EN pin with no RC, a missing 100 nF, an I²C bus with no pull-up. Copperwright looks for exactly those, on the netlist, and checks the PCB and release files with deterministic tools before your agent calls a board done.
What it does
- Netlist audit. Single-pin nets, unconnected power pins, rail/ground shorts, decoupling per IC power pin, bulk capacitance, I²C pull-up count and value, net-name collisions (
+3V3vs3V3), missing LCSC/MPN fields. - ESP32 pin rules. Strapping levels at reset and invalid strap combinations, flash/PSRAM-reserved and USB-JTAG pins, input-only pins, ADC2 with Wi-Fi, EN RC delay, for ESP32, S3, C3 and C6. Values come from Espressif documents; it also cross-checks your board-interface map, sdkconfig and firmware GPIO use.
- Power traces. IPC-2221 width and via current, plus a per-net check of the routed board inside KiCad's Python.
- Fab rules. Ready
.kicad_drufiles for JLCPCB 2/4-layer and PCBWay 2-layer, and a check that proves every rule fires (kicad-cli silently ignores a broken rule file). - ERC/DRC. Run headless with schematic parity; a violation is only waived with a written justification.
- Releases. Gerber, drill, BOM, placement and STEP with a manifest; JLCPCB BOM and CPL with DNP and LCSC checks and rotation offsets.
How it works
Requirements → datasheet pass → schematic → netlist and ESP32 pin audits → ERC → PCB with fab rules and IPC-2221 sizing → DRC and parity → board-to-firmware interface map → firmware build → validated release. Every checker prints a JSON report naming the ref, pin and net, the expected and actual values and a fix.
What you get
The workflow (SKILL.md), 16 reference files with sourced rules (ESP32 hardware, PCB current and clearance, fab capabilities, schematic rules, EMC layout, assembly outputs), 17 self-contained scripts, three fab rule files and a JLC rotation-offset template.
Where it stops
It reduces mistakes; it does not certify designs. Confirm critical values in the current datasheet and errata. The fab's own DRC and assembly preview have the final word. Mains, high-current, battery and RF designs need expert review. Bring up a first article before ordering volume.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Testing & Debugging.
Needs local Python 3.11+ and KiCad 10 (kicad-cli; KiCad's own Python for the pcbnew checks); browser-only chat cannot run the scripts. KiCad projects only. ESP32 pin rules cover ESP32, S3, C3 and C6; other MCUs get the netlist, power and fab checks but no pin rules. It reduces mistakes, it does not certify a design: confirm critical values in the current datasheet, and the fab's DRC and assembly preview have the final word.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 16 days ago
- Software
Python 3.11+KiCad 10KiCad Python with pcbnew
- Optional
- ESP-IDForPlatformIO
kicad-cli comes with KiCad. KiCad's bundled Python runs the power-trace and rule-file checks; ESP-IDF or PlatformIO builds firmware.
Permissions
Runs the bundled checker scripts and kicad-cli locally in the terminal, reads the user's KiCad, netlist, board-interface, sdkconfig and firmware files, and writes reports, headers and release files into the project. Reads KICAD_CLI only to locate kicad-cli. No network access.