component-spec-extractor

Generate JSON extraction plans for electronic component datasheets.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/lgili/skillex --skill component-spec-extractor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: component-spec-extractor
Source: https://github.com/lgili/skillex/tree/main/skills/component-spec-extractor
Command: npx skills add https://github.com/lgili/skillex --skill component-spec-extractor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Component-spec-extractor addresses the need to plan and standardize datasheet data extraction for electronic parts, turning datasheets into machine-readable extraction plans.

Core Features & Use Cases

  • Identify the component class from the datasheet cover or part number
  • Load the appropriate profile from references and emit a JSON extraction plan
  • Validate, document gaps, and hand off data to downstream skills like datasheet-intelligence

Quick Start

Provide a part number and manufacturer to generate a canonical extraction plan for that device.

Frequently Asked Questions about component-spec-extractor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan datasheet extraction for electronic parts into a structured format?

To plan datasheet extraction, you provide a part number and manufacturer to generate a canonical plan. The skill identifies the component class and outlines must-have parameters and curves as a structured JSON output ready for downstream modeling.

What is a canonical extraction plan for electronic component datasheets?

A canonical extraction plan is a structured JSON outline of must-have parameters, test conditions, and curves for a specific component class. It standardizes datasheet data to ensure consistent machine-readable outputs for downstream usage.

How do I extract must-have parameters and test conditions from electronic datasheets?

You extract must-have parameters by loading the appropriate component profile from references based on the part number. The skill outlines required test conditions and downstream usage, emitting a JSON extraction plan for validation.

Can I use this to generate a JSON extraction plan for downstream modeling?

Yes, you can generate a JSON extraction plan for downstream modeling. The output is structured specifically to hand off data to downstream skills like datasheet-intelligence for further processing and validation.

Does the datasheet extraction planning tool work with any electronics part number?

The tool works with any electronics part number that matches a component profile loaded from its references. It identifies the component class from the part number or datasheet cover to build the extraction plan.

What are the limitations of automating datasheet data extraction for electronic parts?

The main limitation is that extraction planning requires a matching component profile in the references. While it documents gaps and validates data, unlisted or highly novel electronic parts may lack a canonical profile to load.