nex-bom-normalizer
Standardize Electronics BOM Cleanup
Inconsistent BOM exports create duplicate orders and incomplete procurement records. This guide defines cleanup rules for column mapping, matching-part merges, reference formatting, and missing-data review.
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
Review the Skillstore skill "nex-bom-normalizer" from https://skillstore.io/skills/nexaiguy-nex-bom-normalizer.md and its manifest at https://skillstore.io/api/skills/nexaiguy-nex-bom-normalizer/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「nex-bom-normalizer」を使用しています。 Two rows share MPN ABC-10 and manufacturer ExampleCo. Quantities are 2 and 1; references are r1, r2, and r3.
期待される結果:
- Proposed merged part: ABC-10 from ExampleCo.
- Total quantity: 3.
- Normalized references: R1, R2, R3.
「nex-bom-normalizer」を使用しています。 A BOM row lists reference c5 and quantity 1, but leaves MPN and Manufacturer blank.
期待される結果:
- Normalized reference: C5.
- Review required: MPN and Manufacturer are missing.
- Keep this row separate for manual completion; do not invent part details.
「nex-bom-normalizer」を使用しています。 Two rows have MPN X100 and quantity 1 each, but their manufacturers are Alpha Components and Beta Components.
期待される結果:
- Keep both rows separate.
- The manufacturer values differ, so the documented merge criteria are not met.
セキュリティ監査
安全All three static findings are false positives: the URLs are attribution and catalog links, and the footer contains no system reconnaissance instructions. No evidence found of prompt injection, data exfiltration, or malicious execution in the supplied guide. Referenced automation scripts are absent, so their behavior cannot be assessed.
リスク要因
🌐 ネットワークアクセス (2)
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/nexaiguy-nex-bom-normalizer/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/nexaiguy-nex-bom-normalizer?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/nexaiguy-nex-bom-normalizer?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/nexaiguy-nex-bom-normalizer/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/nexaiguy-nex-bom-normalizer.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>学術引用 (APA · BibTeX · CFF)
APA形式の引用
nexaiguy. (2026). nex-bom-normalizer security audit report (audit version 1) [Author version 1.0]. Skillstore. https://skillstore.io/skills/nexaiguy-nex-bom-normalizer/audits/1BibTeX形式の引用
@techreport{nexaiguy-nexaiguy-nex-bom-normalizer-2026,
author = {nexaiguy},
title = {nex-bom-normalizer security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/nexaiguy-nex-bom-normalizer/audits/1},
note = {Author version 1.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "nex-bom-normalizer security audit report (audit version 1)"
version: "1.0"
type: report
authors:
- name: "nexaiguy"
date-released: "2026-11-02"
url: "https://skillstore.io/skills/nexaiguy-nex-bom-normalizer/audits/1"
identifiers:
- type: other
value: "skillstore:nexaiguy-nex-bom-normalizer:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中作成できるもの
Review EDA Export Cleanup
Use the documented column and reference rules to review inconsistent Altium, KiCad, or Eagle exports before assembly handoff.
Consolidate Procurement Lists
Apply the documented matching criteria when reviewing partial BOMs for consolidation, keeping different manufacturers separate.
Identify Incomplete Quote Data
Review required BOM fields and separate incomplete records before requesting a manufacturing quote.
これらのプロンプトを試す
Using the guide, map these BOM headers to RefDes, Qty, MPN, and Manufacturer: [headers]. Flag ambiguous mappings without guessing.
Normalize reference designators in these pasted BOM rows to uppercase, comma-separated values: [rows]. Preserve part identifiers and report uncertain entries.
Review these BOM rows: [rows]. Merge only matching MPN and Manufacturer pairs, sum quantities, and list unresolved conflicts separately.
Review [BOM data] against the guide. Propose column mappings, duplicate merges, quantity checks, and missing-field reports. Identify ambiguities and unavailable automation before changes.
ベストプラクティス
- Preserve the original BOM and review proposed column mappings before applying changes.
- Confirm both MPN and Manufacturer match before merging, then reconcile quantities and reference designators.
- Resolve flagged missing fields manually and validate any separately obtained implementation before processing production files.
回避
- Assuming the public guide includes the referenced executable or guarantees deterministic results.
- Merging rows solely by similar descriptions or matching MPNs while ignoring manufacturers.
- Inventing missing part numbers, quantities, or manufacturer names to complete a BOM.