bom

Coordinate cross-distributor BOM data from KiCad schematic symbols into CSVs and order files.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/mattpainter701/my-claude-setup --skill bom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bom
Source: https://github.com/mattpainter701/my-claude-setup/tree/main/claude-config/global-skills/bom
Command: npx skills add https://github.com/mattpainter701/my-claude-setup --skill bom

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires kicad_sexp, and includes scripts (resource) and references (resource) components.

What problem does it solve?

BOM management for electronics projects—coordinating KiCad symbol properties with distributor teams to create, maintain, and export accurate BOMs, reducing sourcing delays and version mismatches. This Skill acts as the primary orchestrator that harmonizes DigiKey, Mouser, LCSC, element14, JLCPCB, PCBWay, and KiCad workflows into a single end-to-end process for sourcing, pricing, ordering, and fabrication prep.

Core Features & Use Cases

  • Central BOM orchestration across multiple distributors and fabrication partners.
  • Analyze schematics, validate parts, write properties back to KiCad symbols, export BOM CSVs, and generate distributor-specific order files.
  • Use Case: Prototyping a board by sourcing parts from DigiKey and Mouser while maintaining a synchronized KiCad BOM.
  • Use Case: Production-ready BOM handling with LCSC/JLCPCB for fabrication, including datasheet backfill and stock verification.

Quick Start

Run the BOM analysis on your KiCad schematic and export the BOM tracking CSV for review.

Frequently Asked Questions about bom

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

FAQPage Schema
How do I export a BOM from KiCad for multiple distributors like DigiKey and Mouser?

You can export a BOM for multiple distributors by analyzing KiCad schematic symbols to validate component data, then generating distributor-specific CSV order files for DigiKey, Mouser, LCSC, and element14. This harmonizes sourcing and ordering workflows into a single process.

What is the best way to validate KiCad schematic parts before sending a BOM to fabrication?

Validating KiCad parts before fabrication involves enforcing data quality rules such as MPN presence, manufacturer details, datasheet URL validity, and stock status. This verification ensures production readiness and prevents sourcing delays or version mismatches during board assembly.

Does this BOM workflow support generating order files for JLCPCB and PCBWay?

Yes, the BOM workflow supports fabrication partners like JLCPCB and PCBWay. It coordinates cross-distributor BOM data directly from KiCad symbols to enable end-to-end sourcing, pricing, and fabrication preparation, including datasheet backfill and stock verification.

How do I backfill missing manufacturer part numbers in a KiCad BOM CSV?

To backfill missing manufacturer part numbers, the BOM orchestrator analyzes your KiCad schematic, identifies gaps in component properties like MPNs, and writes the validated data directly back to the KiCad symbols before exporting the tracking CSV.

Can I synchronize KiCad schematic properties with LCSC components for prototyping?

Yes, you can synchronize KiCad properties with LCSC components for prototyping. The workflow validates parts against distributor data, updates schematic symbols with accurate sourcing information, and exports CSVs to maintain a synchronized BOM.

Why does my KiCad BOM export fail when distributor stock is unavailable?

KiCad BOM exports flag unavailable stock because the workflow enforces stock status validation to ensure sourcing readiness. This data quality check prevents ordering errors by verifying component availability across distributors before generating the final CSV files.