CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

62%

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-component-library-formatter/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

21%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 an operational skill: it markets capabilities and answers sales FAQs but gives Claude no commands, schema, or steps to execute, and its one referenced script is missing from the bundle. Only the section headings and the capability bullet list provide any operational signal.

Suggestions

Replace the capability bullets and marketing prose with executable guidance: the exact command to run scripts/validate_library.py (arguments, expected output), and inline or reference the canonical schema definition the script enforces.

Delete the FAQ, "Why this beats prompting it yourself", "The problem", and footer promo sections — they duplicate the description and burn context tokens without adding anything Claude can act on.

Add a numbered workflow with a validation checkpoint (run validation → review gap report → apply fixes → re-validate → export cleaned CSV) before any file is written, since this is a batch operation over user data.

DimensionReasoningScore

Conciseness

A large share of the ~75-line body is promotional padding Claude cannot act on: "The problem" explains facts Claude already knows (inconsistent naming is "tedious and prone to human error"), "Why this beats prompting it yourself" is a marketing pitch with the over-claim "100% compliance", and the ~20-line "Questions" FAQ repeats earlier sections plus purchase details ("What exactly is included in the purchase"). Not a 1 because the "What it does" bullets and "Known limitations" are at least information-dense rather than tutorial-style over-explanation.

2 / 5

Actionability

The body only describes rather than instructs — bullets like "Normalizes component metadata into a canonical schema" and "Automatically trims whitespace, title-cases manufacturer names" state capabilities, but there is no code, no command, no schema definition, and no invocation instructions anywhere. Even the one concrete artifact named ("scripts/validate_library.py") is never shown how to be run and does not exist in the bundle, matching the 1 anchor ("only describes rather than instructs").

1 / 5

Workflow Clarity

A rough pipeline order is implied by the "What it does" bullets (normalize → trim/title-case → validate → report → export) and the request/result example, but no executable steps, arguments, or validation checkpoints are given for a batch operation that rewrites CSV files. This sits at the 2 anchor (rough sequence, many gaps, validation absent) rather than 1 because an implied input→fix→report→output flow is discernible; the batch-operation cap of 3 is not reached anyway.

2 / 5

Progressive Disclosure

Sections are clearly headed (## headers in a logical order), but the structure is undercut by two issues: the sole referenced path ("scripts/validate_library.py") does not exist in the bundle — the body even admits "Scripts, extension source, and templates from the original package are not in this folder" — and marketing/FAQ content that belongs outside SKILL.md is inlined. Fits the 3 anchor (some structure, references present but the organization is off) better than 4, whose "most content is appropriately placed" is not true here.

3 / 5

Total

8

/

20

Passed

Description

87%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: it states concrete, domain-specific actions, includes an explicit "Use when:" clause with three realistic trigger scenarios, and occupies a clear niche with minimal conflict risk. The only weaknesses are minor missing trigger synonyms (.csv, BOM, tool names) and slight under-coverage of the reporting/export capabilities the body advertises.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Normalize and validate electronics component library metadata against a strict canonical schema", "Standardize manufacturer and lifecycle strings across large component CSVs", "Identify missing required fields like footprints or MPNs", "Enforce character limits on component descriptions" — each anchored to a specific domain object. It falls just short of the 5 anchor because gap-report generation and cleaned-CSV export (covered in the body) are absent, leaving minor coverage gaps.

4 / 5

Completeness

It explicitly answers both questions: a clear "what" ("Normalize and validate electronics component library metadata against a strict canonical schema") followed by an explicit "Use when:" clause with three concrete trigger scenarios (standardizing strings in large CSVs, identifying missing fields, enforcing character limits). This matches the top anchor's pattern of what + when with concrete trigger phrases, so the missing-"Use when" cap of 3 does not apply.

5 / 5

Trigger Term Quality

Natural domain keywords are well covered: "component library", "CSVs", "manufacturer", "lifecycle strings", "footprints", "MPNs", "part libraries", and "EDA" are phrases an electronics engineer would actually say. Not a 5 because common variations are missing — no ".csv" file extension, no "BOM", and no specific EDA tool names (Altium, KiCad) that users would naturally mention.

4 / 5

Distinctiveness Conflict Risk

The niche is unmistakable — electronics component library metadata with footprints, MPNs, and EDA compatibility — and the triggers are domain-distinct, so it is unlikely to fire for unrelated skills. Adjacent-anchor check: no overlap risk with generic CSV or document skills is evident, so it fits the 5 anchor (clear niche, minimal conflict) rather than the 4 anchor's "minor overlap risk".

5 / 5

Total

18

/

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-component-library-formatter/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.