Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →aklofas/datasheets
Extract structured specifications from electronic component datasheet PDFs — pinouts, electrical characteristics, peripherals, topology, and features. Cache extractions per project for consumption by schematic and PCB analyzers. Primary consumer infrastructure for `kicad`, `emc`, `spice`, and `thermal` analyzers.
Passed 15 of 20 test cases with the skill, and 4 of 20 without it.
and 15 more in the full report
13 fixed4 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
Where are extracted JSON files stored relative to the project directory, and what is the manifest file name in v1.4?
| Checked | Without skill | With skill |
|---|---|---|
| Output specifies storing JSON extractions under datasheets/extracted/ relative to the project root | Missed | Passed |
| Output names manifest.json as the extraction manifest file | Passed | Passed |
The instructions your model reads when the skill loads.
| Skill | Relationship |
|---|---|
digikey / mouser / lcsc / element14 | Producers — download the PDFs under <project>/datasheets/ that this skill extracts from |
kicad | Primary consumer — VM-001/PU-001/FS-001/PP-001/LR-001/XT-001 + Phase 4b lookup detectors (AM-001/OV-001/TJ-001/FT-001/EX-001) query extractions via lookup(mpn) for verified-IC knowledge |
emc | Consumer — switching-frequency, package-Rθ_JA, and operating-voltage data sharpen EMC heuristics |
spice | Consumer — SPICE model presence + IBIS data feed simulation-readiness checks |
thermal | Consumer — package Rθ_JA + junction temperature limits drive Tj estimates (TS-001..TJ-001) |
bom | Indirect — coverage of structured extractions affects BOM verification confidence |
Handoff guidance: This skill is consumer infrastructure. The typical flow is distributor skill downloads PDF → datasheets skill extracts → analyzer skill queries. Use this skill directly when (a) the user asks to extract or verify a specific MPN, (b) an analyzer reports trust_level: low and the gap is per-MPN extraction quality, or (c) a new MPN was added to the BOM and downstream detectors should pick up its verified specs. Don't run this skill in isolation if the user just wants a design review — call it from the kicad workflow at the "Sync datasheets" step instead.
Extract structured, machine-readable specifications from component datasheet PDFs and make them available to analyzer skills. Works on whatever PDFs are downloaded under <project>/datasheets/ (downloads are owned by distributor skills like digikey, mouser, lcsc, element14).
This skill owns:
schemas/ (base, pinout, spec_value, regulator, extraction, manifest) plus 5 v1.4 category extensions (diode, transistor, opamp, mcu, crystal). v1.3 cache format (EXTRACTION_VERSION in scripts/datasheet_extract_cache.py) is still read for compat.datasheet_types/ package exposes DatasheetFacts, SpecValue, Pin, Pinout, lookup(), best(), trusted(), has_data(). Recommended for all new consumers.scripts/datasheet_lookup.py for v1.4 typed access; scripts/datasheet_features.py for the v1.3 dict-shaped helpers (get_regulator_features, get_mcu_features, get_pin_function) — the v1.3 helpers dual-read v1.4 caches and translate to v1.3 dict shape for legacy detector code. Sunset planned for v1.6.datasheet_verify.py (v1.3, schema-vs-usage cross-check) plus datasheet_verify_v14_extraction (v1.4, power_domain references resolve, recommended ≤ absolute, regulator pin references exist).digikey, mouser, lcsc, element14).<project>/datasheets/extracted/. There is no shared cross-project cache.<project>/
design.kicad_sch
datasheets/
test cases passed, vs 4 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.