nex-component-library-formatter
Normalize and validate electronics component library metadata against a strict canonical schema. Use when: Standardize manufacturer and lifecycle strings across large component CSVs; Identify missing required fields like footprints or MPNs in part libraries; Enforce character limits on component descriptions for EDA compatibility.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 6
- Forks
- 0
01 前言 Front Matter
- name
- nex-component-library-formatter
- license
- MIT
- metadata
- { "author": "Nex AI", "version": "1.0", "agensi-slug": "nex-component-library-formatter" }
- description
- Normalize and validate electronics component library metadata against a strict canonical schema. Use when: Standardize manufacturer and lifecycle strings across large component CSVs; Identify missing required fields like footprints or MPNs in part libraries; Enforce character limits on component descriptions for EDA compatibility.
- compatibility
- Claude Code, Cursor, Aider, Windsurf, Cline, VS Code
02 资源文件 1
- 参考文档skill-report.json12.2 KB
03 SKILL.md 正文
Nex Component Library Formatter
Free skill by Nex AI. This file is the public guide from Agensi. Scripts, extension source, and templates from the original package are not in this folder.
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.
Known limitations
Requires the scripts/validate_library.py file to exist in the environment. Only supports CSV format.
Example
Request
Format my component library at data/parts.csv and fix any lifecycle naming issues.
Result
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.
Questions
What specific data issues does the nex-component-library-formatter resolve?
This skill acts as a rigorous quality gate for electronics metadata, fixing inconsistent naming, standardizing manufacturer names, and validating part numbers to ensure your PCB component libraries are ready for production and procurement.
Which PCB design tools is this skill compatible with?
The skill exports cleaned CSV files that are pre-formatted for seamless import into industry-standard EDA tools like Altium Designer, KiCad, and Eagle, following your team's specific naming conventions.
How does this perform better than just asking an AI to clean my CSV?
Unlike standard AI prompts, this skill uses a deterministic Python-based validation engine to ensure 100% schema compliance, preventing the "hallucinated" part numbers or formatting errors common with general-purpose LLMs.
What exactly is included in the purchase of this skill?
You will receive the core Python processing scripts, the canonical schema definitions, a suite of pytest validation tests, and the agent configuration required to run the formatter in your environment.
Can I customize the validation rules to fit my company's specific internal standards?
Yes, while it comes with a strict canonical schema, you can adjust the validation rules to match your organization’s specific requirements for symbol naming, footprint libraries, and mandatory metadata fields.
Built by Nex AI. More skills, including the paid catalog: https://www.agensi.io/creators/ch1n4-g3nd4x
04 同仓库更多 Skills
serpmaven
Scrape Google search results (SERP) to JSON with SERP Maven (serpmaven) - a real Chrome browser on a residential proxy with sticky sessions. Run it as a CLI, a Python library, a local HTTP search API (`serve`), an MCP server or a Docker image; set the proxy login, workers, pages and cost tracking. Use when the user wants Google results, rank tracking, a self-hosted SERP API, or live Google search for an AI agent.
revnu-landing-page-audit
Find out why a landing page isn't turning visitors into signups, demos or sales. Audits one page against what the ad, post or search that sends people there promised, then checks the first screen, proof, call to action, friction and mobile. Returns at most 7 prioritized fixes, plus what is fine and what could not be checked; rewrites specific lines and fixes the page in the repo when asked. Never promises a conversion lift. Works without a Revnu account. Use when the user says or asks: "audit my landing page", "why isn't this page converting", "review my homepage", "my ads get clicks but no signups", "people bounce from the pricing page", "CRO review", "improve conversion rate", "is my hero section clear", "roast my landing page", "rewrite my headline", "what's wrong with this page", "landing page feedback", "make the signup page convert better". Not for SEO or AI-search audits, page speed engineering on its own, or building a new page from scratch.
revnu-growth-context
Write down once who buys, what they're stuck on, what it costs, what proof you have and what you've already tried, so every growth task starts from facts instead of a questionnaire. Creates or updates .agents/revnu-growth.md from the repo, the live site and the user, and imports an existing product-marketing.md. Use when the user says "set up our marketing context", "who is our ideal customer", "write our ICP", "describe the product for marketing", "positioning doc", "what's our brand voice", "remember this about our customers", "log what we tried", "what have we learned from marketing", "we changed pricing, update the context", "update our growth notes", "summarize the business for the agent", "import my product-marketing.md", "start a growth doc", or before a first marketing, SEO, outreach or launch task when no context file exists. Works without a Revnu account.
revnu-get-listed
Get onto the third-party pages AI answers and search cite when buyers ask for the best tool in your category: "best X" roundups, directories, review sites, GitHub awesome lists, community threads and comparison pages. Finds which ones are cited, ranks them by fit and effort, and drafts each submission, PR or pitch by the target's own rules. Use when the user says "get us listed", "which directories should we submit to", "how do we get into best-of lists", "why does ChatGPT recommend competitors and not us", "get mentioned in AI answers", "submit to awesome lists", "get on G2", "where are our competitors listed", "pitch listicle authors", "find backlink opportunities", "launch directories", "get into roundups", "Product Hunt alternatives", "where should we be listed", "get cited by Perplexity". Never submits, pays or posts without a yes. Works without a Revnu account.
revnu-ai-readiness-audit
Audit whether your website gives ChatGPT, Perplexity, Claude, Gemini and Google's AI Overviews something worth quoting, and fix the pages that don't. Use when the user says or asks "is my site ready for AI search", "audit my site for AI answers", "AEO audit", "GEO audit", "why doesn't ChatGPT quote our pricing", "make our pages citable by AI", "do I need llms.txt", "does schema help with ChatGPT", "check our structured data", "is our content visible without JavaScript", "AI SEO audit", "optimize our homepage for AI answers", "LLM SEO check", "why does AI get our product wrong", "fix our site for AI Overviews". Checks fetchability and indexability, answers in the raw HTML, entity facts, schema (including JS-injected markup), headings, dates and llms.txt, then gives at most 10 prioritised fixes and edits the repo when asked. Works without a Revnu account.
proxy-troubleshooting
Diagnose residential proxy failures, with NodeMaven's gateway as the reference - 407 with correct credentials, 406, 410, 500, a connection that hangs, ERR_TUNNEL_CONNECTION_FAILED in a browser, Playwright or Puppeteer ignoring proxy credentials, a sticky session that changes IP, geo-targeting that is silently ignored, passwords with special characters, and unexpected traffic from headless Chrome. Use when a proxy connection fails, returns the wrong location, or costs more traffic than expected.