pad-analysis

Detect pad-to-pad and pad-to-via spacing violations on PCB layouts.

2|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/pjcau/esp32-emu-turbo --skill pad-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pad-analysis
Source: https://github.com/pjcau/esp32-emu-turbo/tree/main/.claude/skills/pad-analysis
Command: npx skills add https://github.com/pjcau/esp32-emu-turbo --skill pad-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Analyzing PCB layouts for pad-to-pad and pad-to-via spacing violations is time‑consuming and error‑prone, often leading to costly rework after DFM submission.

Core Features & Use Cases

  • Automated distance calculation using a Python script to check all pad pairs against a configurable threshold.
  • Filtering by net to separate intentional connections from true spacing violations.
  • Violation mapping that links each issue to the source script for quick fixes, ideal for hardware engineers preparing files for manufacturers like JLCPCB.

Quick Start

Run the analysis script with an optional threshold parameter to generate a filtered report of spacing violations.

Frequently Asked Questions about pad-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check PCB pad-to-pad spacing violations before submitting files to manufacturers?

To check PCB pad spacing violations, run the provided Python analysis script to compute distances between all pad pairs and generate a filtered report of gaps below your configured threshold. This catches spacing issues before DFM submission to manufacturers like JLCPCB.

Can I filter out intentional net connections when detecting pad-to-via spacing violations?

Yes, you can filter pad-to-via spacing violations by net to separate intentional electrical connections from true clearance issues. The analysis script maps each detected violation to its source location for quick fixes during PCB design review.

Do I need a specific Python environment to run PCB pad analysis scripts?

You need a Python environment to execute the pad analysis script. The tool requires no additional dependencies and computes all pad-to-pad and pad-to-via distances using an optional threshold parameter to produce the filtered violation report.

What is the best way to configure threshold distances for PCB pad clearance checks?

The best way to configure threshold distances for PCB pad clearance checks is passing an optional threshold parameter to the Python analysis script. It automatically flags any pad or via gaps falling below the specified value before you submit files for DFM.

Why does automated distance calculation help with PCB design review?

Automated distance calculation helps with PCB design review because manually analyzing pad-to-pad and pad-to-via spacing is error-prone and time-consuming. The script flags gaps below a configurable threshold, preventing costly rework after DFM submission.

Are there limitations to using Python scripts for pad spacing violation detection?

A limitation of using Python scripts for pad spacing violation detection is that you must manually configure the threshold parameter and filter results by net. The script identifies gaps but requires hardware engineer review to distinguish true violations from intentional connections.