CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nex-bom-normalizer

Standardize, deduplicate, and clean messy Bill of Materials (BOM) files into procurement-ready CSVs. Use when: Deduplicate component lists by merging matching MPNs and Manufacturers; Convert messy EDA exports into a canonical column format for procurement; Automatically fix and uppercase inconsistent reference designators.

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/nex-bom-normalizer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

25%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body reads as a product landing page rather than skill instructions: it is dominated by marketing framing, an FAQ, and purchase links, while providing no invocation command and referencing a script that is absent from the folder. What capability information exists (canonical columns, dedupe keys, flagged-row output) is real but unusable without the missing script or a usage example.

Suggestions

Replace the marketing sections ("The problem", "Why this beats prompting it yourself", "## Questions" FAQ, footer links) with a concrete usage section showing how to run the tool, e.g. `python scripts/normalize.py source_bom.xlsx --output source_bom_normalized.csv` with its arguments and outputs.

Include the actual scripts/normalize.py (and example input/output files) in the bundle, since the body's only actionable reference points to a file that does not exist in this folder.

Add an explicit workflow with a validation checkpoint for this batch operation — e.g. after normalization, verify total quantity against the source rows and require review of the flagged CSV before the output is declared procurement-ready.

DimensionReasoningScore

Conciseness

Much of the body is padding that adds nothing Claude doesn't know: "The problem" narrates why messy BOMs are bad, "Why this beats prompting it yourself" is marketing copy, and the six-question FAQ ("## Questions") restates capabilities already covered — plus footer purchase links. Not 1: it doesn't explain basic technical concepts at length; the waste is promotional repetition rather than tutorial-style padding, and a few sections (What it does, Known limitations, Example) do carry real signal.

2 / 5

Actionability

The body names "scripts/normalize.py" and the supported formats (CSV and XLSX) but never shows how to invoke it — no command, no arguments, no options, and the referenced script isn't even present in the folder. The "Example" is a natural-language request/response, not executable guidance. Not 1: there are concrete specifics (script path, input formats, output file naming like `source_bom_normalized.csv` and `source_bom_flagged.csv`); not 3: no command or code of any kind appears, so nothing is directly executable.

2 / 5

Workflow Clarity

No steps are ever listed; the only sequence is implied by the Example (give it a file → receive a normalized CSV plus a flagged CSV), with many gaps and no invocation step. This is a batch operation on data files, and the rubric caps such skills without validation at 3 — this content is below the cap anyway. Not 1: the input/output flow is discernible from the Example and "What it does" bullets; not 3: even a rough numbered sequence is absent.

2 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/ directories), yet the body's one reference — "Python-based CLI tool (scripts/normalize.py)" — points to a file that is not in this folder, so the skill's core artifact is unreachable. Marketing and FAQ content that belongs in a store listing is inlined in SKILL.md instead. Not 1: the body has clear section headers and is short, so it is navigable rather than a monolithic wall.

2 / 5

Total

8

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete third-person capabilities, an explicit "Use when:" clause with three trigger scenarios, and a well-defined niche with low conflict risk. The only gap is keyword breadth — natural synonyms like "parts list", EDA tool names, and file extensions (.csv/.xlsx) are absent from the trigger terms.

DimensionReasoningScore

Specificity

The description lists multiple concrete, third-person actions — "Standardize, deduplicate, and clean messy Bill of Materials (BOM) files into procurement-ready CSVs", "merging matching MPNs and Manufacturers", "fix and uppercase inconsistent reference designators" — with comprehensive coverage of the skill's behaviors. Not 4: coverage is complete across the skill's core operations (standardize columns, dedupe by MPN/Manufacturer, normalize RefDes) rather than having minor gaps.

5 / 5

Completeness

Both halves are explicit: the "what" is the opening capability statement ("Standardize, deduplicate, and clean messy Bill of Materials (BOM) files into procurement-ready CSVs") and the "when" is a literal "Use when:" clause with three concrete trigger scenarios. Not 4: the "when" is fully explicit with multiple concrete triggers, not merely present-but-imprecise.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "Bill of Materials (BOM)", "MPN", "Manufacturer", "EDA exports", "reference designators", "procurement", "CSV" — terms a hardware engineer would actually say. Not 5: misses common synonyms and extensions users would mention, e.g. "parts list", "Altium/KiCad", ".csv"/".xlsx" (the tool supports XLSX but the description never says so). Not 3: the terms present go well beyond a single generic keyword and include domain-specific natural phrasing.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — BOM normalization for procurement — with distinct triggers (MPN, Manufacturer, EDA exports, reference designators) that no generic CSV or data-cleaning skill would claim. Conflict risk with other skills is minimal. Not 4: the trigger vocabulary is domain-specific enough that overlap with even closely related skills (e.g. generic CSV cleaners) is negligible.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

NexaiGuy/nex-ai-skills

Path

skills/nex-bom-normalizer/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.