- Home
- Skills
- Business & Operations
- nex-component-library-formatter
Works with the AI tools you already use
Nex Component Library Formatter
Normalize and validate electronics component library metadata against a strict canonical schema.
Free
nex-component-library-formatter
Example session with this skill installed
Format my component library at data/parts.csv and fix any lifecycle naming issues.
- Read your context and instructions
- Compiled the nex-component-library-formatter
- Generated the UI component
I've processed data/parts.csv.
- Validated 142 rows.
- Normalized 12 manufacturer names to title-case.
- Fixed 5 lifecycle strings (e.g., 'active' to 'Active').
- Reported 3 rows missing required MPNs (Rows: 42, 87, 101).
Cleaned file saved to data/parts_fixed.csv.
nex-component-library-formatter.tsx
TSX · React component
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
About this skill
The problem
Component libraries often suffer from inconsistent naming, missing manufacturer part numbers, and non-standard lifecycle statuses. Manually auditing CSVs for PCB design software is tedious and prone to human error, leading to fabrication delays or procurement issues.
What it does
- Normalizes component metadata into a canonical schema including footprints, MPNs, and manufacturers.
- Automatically trims whitespace, title-cases manufacturer names, and standardizes lifecycle strings.
- Validates required fields like symbol name and description length to ensure library integrity.
- Generates detailed gap reports identifying exactly which rows and fields are missing data.
- Exports cleaned and formatted CSV files ready for import into EDA tools.
Frameworks & tools
Python, pytest, and CLI-based CSV processing scripts.
Why this beats prompting it yourself
General-purpose LLMs struggle with strict schema enforcement across large datasets and often hallucinate "fixes" for part numbers. This skill uses a deterministic validation script paired with an agent to ensure 100% compliance with your specific library standards without manual data entry.
Use cases
- Cleaning up legacy component libraries before migrating to new EDA software.
- Validating a new batch of parts from a distributor or contractor.
- Standardizing footprint and symbol naming conventions across a hardware team.
- Auditing BOM components for lifecycle status and datasheet links.
How to install
Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.
- 1
Download the ZIP
Free skills download straight away. Paid skills unlock right after purchase.
- 2
Unzip into your skills folder
Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.
- 3
Ask your agent to use it
Restart the agent if it was already running. It picks the skill up automatically - no config needed.
Skills folder by agent
Click the path to copy it. Create the folder if it does not exist yet.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
3 installs
Downloaded by developers to date
Free forever
No account required to browse
Trust & safety
Security scanned
Verified clean 1 month ago
- Free to download with an account