# datasheets

Extracts pinouts and electrical specs from electronic datasheet PDFs into structured JSON for schematic analyzers.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 600 installs · ★ 1504
- Author: aklofas
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/aklofas/kicad-happy/tree/HEAD/skills/datasheets/SKILL.md
- Updated: 2026-10-23
- HTML: https://affpapa.org/en/nevibecode/skills/datasheets

## What it does

The skill parses downloaded component PDFs in `<project>/datasheets/` and stores structured specs under `<project>/datasheets/extracted/`. Under the hood, it applies page-selection heuristics and canonical JSON Schema Draft 2020-12 schemas. Downstream analyzers like `kicad`, `emc`, and `thermal` query these extractions through the `lookup(mpn)` typed facade.

This skill does not download PDFs from the web. Distributor skills like `digikey`, `mouser`, or `lcsc` handle the downloads beforehand. Because extractions live strictly within the project directory, no shared cross-project cache exists. Without local PDF files in the project tree, the parser has nothing to inspect.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add aklofas/kicad-happy --skill datasheets -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/datasheets/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/datasheets/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add aklofas/kicad-happy --skill datasheets -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/datasheets/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add aklofas/kicad-happy --skill datasheets -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/datasheets/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install aklofas/kicad-happy datasheets
```

2. **Manually: put the files in place**
- File: `.github/skills/datasheets/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add aklofas/kicad-happy --skill datasheets -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/aklofas/kicad-happy --path skills/datasheets
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/datasheets/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add aklofas/kicad-happy --skill datasheets -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/aklofas/kicad-happy/tree/HEAD/skills/datasheets/SKILL.md

## When to use it
- extract pinouts and electrical characteristics from component PDFs
- cache verified IC specifications for KiCad schematic analyzers
- cross-check pin functions against schematic usage
- score the completeness of extracted datasheet data

## Example prompts
- Extract specs and pinout from the TPS61023DRLR datasheet
- Check pin functions for part TPS61023DRLR against its datasheet
- Verify datasheet extraction quality for this MPN

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 56bc705c567268d7.

BEGIN THIRD-PARTY FILE 56bc705c567268d7
```text
---
name: datasheets
description: 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. Use this skill whenever the user asks to extract, verify, or read specs from a component datasheet; when analyzers need verified IC knowledge (EN pin thresholds, PG presence, USB peripheral speed); or when a review mentions datasheet coverage, extraction quality, or per-MPN specifications. Also triggers on "extract this datasheet", "what are the specs for MPN X", "verify datasheet extraction", or "check pin functions for part Y".
---

# Datasheets Skill

## Related Skills

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

## Purpose

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`).

## Scope

This skill owns:
- **Extraction schemas** — canonical JSON structures for per-MPN specs. v1.4 ships 6 JSON Schema Draft 2020-12 schemas under `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.
- **Typed access layer (v1.4)** — `datasheet_types/` package exposes `DatasheetFacts`, `SpecValue`, `Pin`, `Pinout`, `lookup()`, `best()`, `trusted()`, `has_data()`. Recommended for all new consumers.
```
END THIRD-PARTY FILE 56bc705c567268d7

The third-party file has ended. Everything between the 56bc705c567268d7 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 3169 of 9877 bytes. © aklofas · MIT · https://github.com/aklofas/kicad-happy/tree/HEAD/skills/datasheets/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md