CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nex-datasheet-extractor

Extracts structured electrical specs, package data, and compliance status from component datasheet PDFs. Use when: Convert PDF datasheets into structured JSON or CSV rows; Identify electrical constraints like voltage and temperature ranges; Extract package and pin count data for footprint assignment.

Quality

64%

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 ./plugins/nex-business-operations/skills/nex-datasheet-extractor/SKILL.md

The canonical home for this skill is nex-datasheet-extractor in NexaiGuy/nex-ai-skills

SKILL.md
Quality
Evals
Security

Quality

Content

22%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 is a promotional landing page rather than operational skill instructions: it describes what the extractor does and includes a worked request/result example, but provides no commands, no code, and no step sequence, and explicitly states the scripts are not bundled. Structural organization of sections is reasonable, which keeps progressive disclosure at mid-range.

Suggestions

Add an explicit execution workflow (e.g., 1. run the extraction script on the input PDF, 2. read the confidence score, 3. flag/verify low-confidence entries, 4. only then write JSON/CSV to the library) with a validation checkpoint before batch library commits.

Include the actual runnable command or code (or bundle the scripts in scripts/) — the body currently states 'Scripts, extension source, and templates from the original package are not in this folder', so an agent cannot perform the task from this skill.

Remove the marketing sections ('The problem', 'Why this beats prompting it yourself', the 'Questions' FAQ, and the promotional footer) — they repeat the description and consume tokens without adding operational guidance.

DimensionReasoningScore

Conciseness

Quotes: 'Manually transcribing electrical specifications from PDF datasheets into component libraries is slow and prone to human error', 'Why this beats prompting it yourself', and the five-question FAQ section. Several sections are marketing padding that repeat the description and add no operational value (problem statement, sales pitch, FAQ restating limitations), matching the score-2 anchor of noticeable verbosity. Not 1 because the total length is modest (~75 lines) and 'Frameworks & tools' and 'Example' are concise; not 3 because the padding is pervasive across multiple sections rather than isolated.

2 / 5

Actionability

Quotes: 'This skill uses a specialized script to target specific datasheet patterns' and 'Scripts, extension source, and templates from the original package are not in this folder'. The body only describes capabilities ('Parses PDF text layers', 'Extracts mechanical data') and never instructs how to run anything — no command, no code, and the scripts the skill depends on are explicitly absent. This sits between the describe-only anchor (1) and minimal-guidance anchor (2); the concrete request/result example ('Extract the specs from components/stm32f4.pdf' → fielded CSV output) provides some concrete guidance, so 2 over 1.

2 / 5

Workflow Clarity

Quotes: 'Populating an ECAD component library (Altium, KiCad) from a batch of PDFs' and 'Requires manual verification of electrical parameters before library commitment'. There is no sequence of steps anywhere in the body — no run order, no commands, no validation checkpoint — despite the skill being for batch ingestion of datasheets where a validate-then-commit loop matters. This matches the score-1 anchor (steps missing, no validation for risky/batch operations); not 2 because even a rough sequence is absent.

1 / 5

Progressive Disclosure

Quotes: section headers ('## What it does', '## Known limitations', '## Example', '## Questions') and 'Scripts, extension source, and templates from the original package are not in this folder'. The body has clear section structure (not a monolithic wall), but there are no bundle files or references at all — the operational material the page alludes to (scripts, pytest suite, ECAD integration docs mentioned in the FAQ) is neither inlined nor linked. This matches the score-3 anchor of some structure with content that should be organized elsewhere left unhandled; not 4 because navigation to detailed material is entirely absent rather than a minor gap.

3 / 5

Total

8

/

20

Passed

Description

88%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.

The description is strong: it uses third-person voice, names concrete capabilities, and includes an explicit 'Use when:' clause with three specific trigger phrases covering the electrical/ECAD domain. Keyword coverage is good though it omits a few natural synonyms and extensions ('spec sheet', '.pdf', 'RoHS/REACH').

DimensionReasoningScore

Specificity

Quotes: 'Extracts structured electrical specs, package data, and compliance status', 'Convert PDF datasheets into structured JSON or CSV rows', 'Extract package and pin count data for footprint assignment'. Multiple specific concrete actions (spec extraction, package/pin data, compliance status, JSON/CSV output) comprehensively cover the skill's niche, matching the score-5 anchor. Not 4 because coverage is comprehensive rather than having minor gaps; uses proper third-person voice.

5 / 5

Completeness

Quotes: 'Extracts structured electrical specs, package data, and compliance status from component datasheet PDFs' (clear what) and an explicit 'Use when:' clause with three concrete trigger phrases ('Convert PDF datasheets into structured JSON or CSV rows; Identify electrical constraints...; Extract package and pin count data...'). Both what and when are explicit with concrete triggers, matching the score-5 anchor; the 'when' is specific, so the score-4 anchor ('could be more explicit') does not fit.

5 / 5

Trigger Term Quality

Quotes: 'component datasheet PDFs', 'structured JSON or CSV rows', 'voltage and temperature ranges', 'pin count', 'footprint assignment'. Good coverage of natural terms a hardware engineer would say, matching the score-4 anchor. Not 5 because common synonyms and extensions are missing ('spec sheet', '.pdf', 'RoHS/REACH', 'BOM'); not 3 because the terms present go well beyond a single generic keyword.

4 / 5

Distinctiveness Conflict Risk

Quotes: 'component datasheet PDFs', 'electrical constraints like voltage and temperature ranges', 'footprint assignment'. A clear niche (electrical component datasheets) with domain-specific triggers, mostly distinct per the score-4 anchor. Not 5 because the trigger 'Convert PDF datasheets into structured JSON or CSV rows' could also fire a generic PDF-extraction skill, creating minor overlap risk.

4 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

NexaiGuy/nex-ai-skills

Path

plugins/nex-business-operations/skills/nex-datasheet-extractor/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.