nex-component-library-formatter
Standardize Electronics Component CSV Metadata
Inconsistent component metadata makes library migration and procurement checks harder. This guide outlines CSV normalization and gap reporting, while automated enforcement requires separately supplied tools.
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
Review the Skillstore skill "nex-component-library-formatter" from https://skillstore.io/skills/nexaiguy-nex-component-library-formatter.md and its manifest at https://skillstore.io/api/skills/nexaiguy-nex-component-library-formatter/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「nex-component-library-formatter」を使用しています。 Review a sample containing manufacturer ' acme ', lifecycle 'active', and an empty manufacturer part number.
期待される結果:
- Proposed manufacturer: Acme, using whitespace trimming and the guide's title-case convention.
- Proposed lifecycle: Active, subject to the team's allowed lifecycle values.
- Missing manufacturer part number: flagged for review; no replacement value inferred.
「nex-component-library-formatter」を使用しています。 Prepare a validation plan for a component CSV requiring symbols, footprints, and manufacturer part numbers.
期待される結果:
- Check each row for missing symbols, footprints, and manufacturer part numbers.
- Report the row and field for each missing value.
- Confirm the description length limit and lifecycle vocabulary before normalization.
- Automated processing requires a separately supplied validator and schema; no file processing is claimed.
セキュリティ監査
安全All three static findings are false positives: the URLs provide attribution and catalog references, and the footer contains no system reconnaissance instructions. No evidence found of prompt injection, data exfiltration, or malicious execution in SKILL.md. The package contains guidance only, not the advertised validation engine.
リスク要因
🌐 ネットワークアクセス (2)
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/nexaiguy-nex-component-library-formatter/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/nexaiguy-nex-component-library-formatter?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/nexaiguy-nex-component-library-formatter?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/nexaiguy-nex-component-library-formatter/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/nexaiguy-nex-component-library-formatter.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-component-library-formatter security audit report (audit version 1) [Author version 1.0]. Skillstore. https://skillstore.io/skills/nexaiguy-nex-component-library-formatter/audits/1BibTeX形式の引用
@techreport{nexaiguy-nexaiguy-nex-component-library-formatter-2026,
author = {nexaiguy},
title = {nex-component-library-formatter security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/nexaiguy-nex-component-library-formatter/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-component-library-formatter 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-component-library-formatter/audits/1"
identifiers:
- type: other
value: "skillstore:nexaiguy-nex-component-library-formatter:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中作成できるもの
Prepare a Legacy Library Migration
Use the documented cleanup checklist to define field mappings, normalization rules, and missing-field checks before migrating component CSVs.
Review Supplier Component Metadata
Plan checks for missing part numbers, inconsistent manufacturer strings, and lifecycle labels in supplier CSV deliveries.
Define Shared Library Standards
Translate the guide into explicit naming rules and validation requirements for a separately maintained CSV processing workflow.
これらのプロンプトを試す
Using this guide, list the checks for my component CSV. Identify required inputs and distinguish available guidance from missing automation.
Review this component CSV sample: [paste sample]. Suggest whitespace, manufacturer, and lifecycle normalization. Flag missing fields without inventing part numbers.
Using these columns and requirements: [insert details], propose CSV validation rules and a row-level gap report format. Mark unspecified limits as unresolved.
Review my supplied validator, schema, and sample CSV. Propose a cleanup plan and tests. Preserve originals and distinguish verified results from planned actions.
ベストプラクティス
- Supply explicit required columns, lifecycle values, naming conventions, and description limits before requesting validation.
- Preserve the original CSV and review proposed changes on a small sample before applying them broadly.
- Verify separately supplied scripts and tests before relying on automated results or importing cleaned data into EDA tools.
回避
- Assuming this documentation package includes the advertised Python validator, schema, or test suite.
- Inventing missing manufacturer part numbers, footprints, or lifecycle values to make validation appear complete.
- Treating formatted CSV output as proof of component authenticity or compatibility with every EDA import configuration.