kicad
KiCad Project Analysis Skill
Related Skills
| Skill | Purpose |
|---|---|
bom |
BOM extraction, enrichment, ordering, and export workflows |
digikey |
Search DigiKey for parts (prototype sourcing) |
mouser |
Search Mouser for parts (secondary prototype source) |
lcsc |
Search LCSC for parts (production sourcing, JLCPCB) |
element14 |
Search Newark/Farnell/element14 (international sourcing, reliable datasheets) |
jlcpcb |
PCB fabrication & assembly ordering |
pcbway |
Alternative PCB fabrication & assembly |
spice |
SPICE simulation verification of detected subcircuits |
emc |
EMC pre-compliance risk analysis — consumes schematic + PCB analyzer output |
Handoff guidance: Use this skill to parse schematics/PCBs and extract structured data. Hand off to bom for BOM enrichment, pricing, and ordering. Hand off to digikey/mouser/lcsc/element14 for part searches and datasheet fetching. Hand off to jlcpcb/pcbway for fabrication ordering and DFM rule validation. During design reviews, run spice when a SPICE simulator is installed (check with which ngspice ltspice xyce) and emc when both schematic and PCB analysis are available. Report each result at its strength: a SPICE pass measured against a real criterion (expected cutoff, ratio, gain) is a check; an info bench, or one built on a generic part model, is a measurement, not verification; EMC findings with confidence: heuristic are pre-compliance screening, not a compliance result.
Before analysis: When the user asks to analyze or review a KiCad project, check whether a datasheets/ directory exists in the project. If not, and DigiKey API keys are available (DIGIKEY_CLIENT_ID), offer to sync datasheets first: "I can download datasheets for your components before analysis — this enables pin-level verification and decoupling validation against manufacturer specs. Want me to sync them?" If the user declines or no API keys are set, proceed without datasheets — the analysis works without them but datasheet verification findings won't be available.