Agent skill

Datasheets

by aklofas in aklofas/kicad-happy

Extract structured specifications from electronic component datasheet PDFs — pinouts, electrical characteristics, peripherals, topology, and features.

MITAuto-check passedDocuments & Office

Install Datasheets

skills CLI
$ npx skills add aklofas/kicad-happy --skill datasheets -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install aklofas/kicad-happy datasheets --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/aklofas/kicad-happy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/datasheets .claude/skills/datasheets && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
datasheets
GitHub stars
1.4k
Used in
1 other repo
Token cost
~2.4k tokens
SKILL.md length
846 words
Files
64 (incl. scripts, references)
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

Extract structured specifications from electronic component datasheet PDFs — pinouts, electrical characteristics, peripherals, topology, and features.

  • The user asks to extract
  • SKILL.md covers Related Skills, Purpose, Scope and Non-goals, plus 7 more sections
  • Runs Python scripts from its folder; calls python3
  • Read specs from a component datasheet

What it does

Datasheets is an agent skill from aklofas/kicad-happy. 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…

Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 66 other files, including scripts and reference files (for example `datasheet_types/__init__.py`, `datasheet_types/base_block.py` and `datasheet_types/codec.py`).

It sits in Documents & Office. The repository describes itself as: AI coding agent skills for KiCad electronics design. Works with Claude Code and OpenAI Codex. Analyze schematics, review PCB layouts, EMC pre-compliance, SPICE simulation… The licence is MIT.

When your agent uses it

  • The user asks to extract
  • Read specs from a component datasheet
  • Analyzers need verified IC knowledge (EN pin thresholds
  • USB peripheral speed)

Example prompts

  • “extract this datasheet”
  • “what are the specs for MPN X”
  • “verify datasheet extraction”
  • “/datasheets”

Requirements

  • Python 3

What it can do on your machine

Read from SKILL.md and the folder at commit 0684046. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Python, from the files we listed), which the agent can run.

    Shell commands in SKILL.md call:

    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Datasheets loads about 2.4k tokens when it runs, and up to ~21k if it reads all its reference files. Until then it costs about 190 tokens; SKILL.md has 846 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~190
When it runs · the whole SKILL.md, loaded when a task matches
~2.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~21k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from aklofas/kicad-happy at commit 0684046, republished under its MIT licence (© aklofas). 846 words, ~2,447 tokens.

Download SKILL.mdSave it as .claude/skills/datasheets/SKILL.md (or your agent's skills folder). This skill also uses 63 other files; get the full folder from GitHub.
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

SkillRelationship
digikey / mouser / lcsc / element14Producers — download the PDFs under <project>/datasheets/ that this skill extracts from
kicadPrimary 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
emcConsumer — switching-frequency, package-Rθ_JA, and operating-voltage data sharpen EMC heuristics
spiceConsumer — SPICE model presence + IBIS data feed simulation-readiness checks
thermalConsumer — package Rθ_JA + junction temperature limits drive Tj estimates (TS-001..TJ-001)
bomIndirect — 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.
  • PDF page selection — heuristics to pick pages most likely to contain pinouts, e-chars, applications, SPICE models.
  • Quality scoring — v1.4 uses a three-dimension rubric (pinout completeness, base completeness, category-extension completeness, 0–100 scale). v1.3 5-dimension weighted rubric still applies to legacy caches.
  • Consumer APIs — 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.
  • Verification — 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).

Non-goals

  • No PDF downloading. That is owned by distributor skills (digikey, mouser, lcsc, element14).
  • No global library. Each project's extractions live in <project>/datasheets/extracted/. There is no shared cross-project cache.

Cache location

<project>/
  design.kicad_sch
  datasheets/
    TPS61023DRLR.pdf        # downloaded by distributor skills
    extracted/
      manifest.json         # extraction manifest (legacy name: index.json)
      TPS61023DRLR.json     # structured extraction (this skill's output)

Reference guides

  • references/extraction-schema.md — canonical schema, every field defined
  • references/field-extraction-guide.md — how to find each field in datasheets from common vendors (TI, ST, NXP, Espressif, Microchip)
  • references/quality-scoring.md — rubric details, score thresholds
  • references/consumer-api.md — how kicad/emc/spice/thermal consume extractions
  • references/cache-layout.md — v1.4 cache directory convention (per-MPN files, _families/ reservation, staleness rules)

Entry-point scripts

  • scripts/datasheet_extract_cache.py — v1.3 cache manager, resolver, indexer
  • scripts/datasheet_page_selector.py — page selection heuristics (used by both v1.3 and v1.4 pipelines)
  • scripts/datasheet_score.py — v1.3 extraction quality scoring
  • scripts/datasheet_verify.py — cross-check extraction vs schematic usage (v1.3 + v1.4 verify_v14_extraction mode)
  • scripts/datasheet_lookup.py — v1.4 typed lookup(mpn) → DatasheetFacts facade with staleness detection
  • scripts/datasheet_features.py — v1.3 consumer helper API (dual-reads v1.4 caches via _derive_*_v14 translators)
  • scripts/plan_extraction.py — v1.4 orchestration plan generator (Phase 3 extraction pipeline)
  • scripts/merge_results.py — v1.4 per-task result validator + merger
  • datasheet_types/ — v1.4 typed access layer package (DatasheetFacts, SpecValue, Pin, Pinout, lookup, best, trusted, has_data)
Show full SKILL.md (317 more words)Show less

Extraction workflow

Run python3 skills/datasheets/scripts/plan_extraction.py <project> to generate an orchestration plan, then merge_results.py to validate and merge per-task outputs. Full scout→plan→dispatch→merge procedure: references/extraction-pipeline.md.

Consuming extractions (v1.4 typed API)

The recommended consumer surface is the typed lookup(mpn, cache_dir=...) facade plus the trust-gating helpers from datasheet_types. Import like:

python
import sys, pathlib
sys.path.insert(0, str(pathlib.Path(__file__).parent.parent / "datasheets"))
from datasheet_types import lookup, has_data, best, trusted

# Returns Optional[DatasheetFacts]. None on cache miss / stale PDF / low quality.
facts = lookup("TPS61023DRLR", cache_dir=pathlib.Path("datasheets/extracted"))
if facts is None:
    return  # heuristic-only path; no datasheet evidence available

# Field-level trust gating — every SpecValue list runs through has_data() / best() / trusted().
pu_range = facts.base.recommended_pullup_range  # Optional[list[SpecValue]]
if has_data(pu_range):
    # Most-trusted single value (first SpecValue meeting threshold, preserves extractor order).
    rec = best(pu_range, min_confidence="medium")  # Optional[SpecValue]
    if rec is not None and rec.min is not None:
        ...  # use rec.min, rec.max, rec.typ, rec.unit, rec.evidence.{page,section,confidence}

# All SpecValues at threshold (for multi-value fields like absolute_max).
hi_conf = trusted(facts.base.absolute_max.get("VDD", []), min_confidence="high")

Defensive patterns (mirrors kicad/SKILL.md § "Probing Analyzer JSON"):

  • lookup() returns None on cache miss, stale PDF (PDF newer than extraction), or quality score below the configured floor. Always guard with if facts is None: return.
  • Category extensions are optional on DatasheetFacts. facts.regulator is None when the part isn't in the regulator category — check before dereferencing.
  • SpecValue lists can be None (field not extracted), [] (extracted but empty), or list[SpecValue]. has_data() collapses the first two to False; pair with best() / trusted() for confidence gating.
  • SpecValue.min / .max / .typ are each Optional[float]. A SpecValue carrying only typ (no range) makes > / < comparisons against .min / .max raise TypeError — guard with explicit is not None chains on every numeric access.
  • confidence is one of "low" / "medium" / "high". Calling best() / trusted() with any other string raises ValueError.

v1.3 compat shim

Legacy detectors still call get_regulator_features(mpn) / get_mcu_features(mpn) / get_pin_function(mpn, pin) from scripts/datasheet_features.py. These dual-read v1.4 caches and translate to the v1.3 dict shape. Sunset planned for v1.6 — new code should use lookup() directly.

When to trigger this skill

  • Immediately after downloading datasheets via sync_datasheets_digikey.py, sync_datasheets_lcsc.py, or equivalent. Without extraction, IC-aware checks (VM-001 rail voltage, PS-001 power-good, PR-004 USB, DP-002 USB speed classification) fall back to heuristics on unknown ICs.
  • Before running analyzers on a new project where datasheets are present but datasheets/extracted/ is empty — the analyzers won't produce the extractions themselves.
  • When a review flags low trust level due to missing manufacturer evidence: extracting the ICs referenced by power regulators, MCUs, and high-speed peripherals typically flips trust_level: low → mixed or high.
  • When a user asks for pin verification ("verify U1 pin names match datasheet") — this skill's cached extraction is the authoritative source.

© aklofas, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 63 other files (scripts, references) in skills/datasheets of aklofas/kicad-happy.

  • SKILL.md
  • datasheet_types/__init__.py
  • datasheet_types/base_block.py
  • datasheet_types/codec.py
  • datasheet_types/extraction.py
  • datasheet_types/pinout.py
  • datasheet_types/regulator.py
  • datasheet_types/spec_value.py
  • datasheet_types/trust_gating.py
  • examples/abm8g-106-12.000mhz-t.json
  • examples/irlml6344.json
  • examples/lm2596-adj.json
  • examples/lm358.json
  • examples/mbrs540t3g.json
  • examples/stm32f103c8t6.json
  • prompts/base.md
  • prompts/crystal.md
  • prompts/diode.md
  • … and 46 more

Open the folder on GitHubat commit 0684046

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in aklofas/kicad-happy, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Datasheets next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Datasheets compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Datasheets this skillaklofas/kicad-happy1.4k1 repos~2.4kAutomated safety check: PassMIT
Markdown Article FormatterJimLiu/baoyu-skills26k7 repos~3.5kAutomated safety check: PassMIT
MarkitdownImCa0/just-laws78114 repos~3.2kAutomated safety check: NotesMIT
Obsidian MarkdownAtmosphere/atmosphere3.8k20 repos~1.3kAutomated safety check: PassApache-2.0
DOCXrvdbreemen/OTGW-firmware20733 repos~4.3kAutomated safety check: PassProprietary
Gzh Designisjiamu/gzh-design-skill3.9k1 repos~2.2kAutomated safety check: PassAGPL-3.0

Similar skills

  • Markdown Article Formatter

    JimLiu/baoyu-skills

    Reformats plain text or Markdown articles with frontmatter, a title, a summary, headings, bold, lists and code blocks, and saves a separate formatted copy.

    26k GitHub starsUsed in 7 repos~3.5k tokens
    Documents & OfficeAuto-check passed
  • Markitdown

    ImCa0/just-laws

    Convert files and office documents to Markdown. An agent skill from ImCa0/just-laws.

    781 GitHub starsUsed in 14 repos~3.2k tokens
    Documents & OfficeAuto-check: notes
  • Obsidian Markdown

    Atmosphere/atmosphere

    Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax.

    3.8k GitHub starsUsed in 20 repos~1.3k tokens
    Documents & OfficeAuto-check passed
  • DOCX

    rvdbreemen/OTGW-firmware

    A skill your agent uses whenever the user wants to create, read, edit, or manipulate Word documents (.docx files).

    207 GitHub starsUsed in 33 repos~4.3k tokens
    Documents & OfficeAuto-check passed
  • Gzh Design

    isjiamu/gzh-design-skill

    微信公众号文章排版引擎,将 Markdown 转换为可直接粘贴到公众号编辑器的 HTML。主题风格从 references/theme-index.md 注册的自定义主题库中选取,自动章节编号、关键词下划线标记、引言卡片、目录导航、代码块、图片/GIF、作者签名。支持 Markdown / Word(.docx) / PDF / 纯文本输入(非 Markdown…

    3.9k GitHub starsUsed in 1 repo~2.2k tokens
    Documents & OfficeAuto-check passed
  • Reads, creates and edits Word .docx files with python-docx, and drops to raw OOXML for tracked changes, comments and byte-exact edits.

    41k GitHub stars~2.5k tokensUpdated today
    Documents & OfficeAuto-check passed

More from aklofas/kicad-happy

All 11 skills in this repo
  • Emc

    aklofas/kicad-happy

    EMC pre-compliance risk analysis for KiCad PCB designs — 18 check categories, 44 rule IDs covering ground planes, decoupling, I/O filtering, switching harmonics, clock routing, differential pair…

    1.4k GitHub starsUsed in 1 repo~2.8k tokens
    Auto-check passed
  • Bom

    aklofas/kicad-happy

    BOM (Bill of Materials) management for electronics projects — the workflow skill that coordinates DigiKey, Mouser, LCSC, element14, JLCPCB, PCBWay, and KiCad skills around a unified BOM lifecycle.

    1.4k GitHub starsUsed in 1 repo~5.5k tokens
    Auto-check passed
  • Digikey

    aklofas/kicad-happy

    Search DigiKey for electronic components and download datasheets — primary source for prototype orders and the preferred API method for fetching datasheets.

    1.4k GitHub starsUsed in 1 repo~4.5k tokens
    Auto-check passed
  • Element14

    aklofas/kicad-happy

    Search Newark, Farnell, and element14 for electronic components — find parts by MPN or distributor part number, check pricing/stock, download datasheets, analyze specifications.

    1.4k GitHub starsUsed in 1 repo~2.7k tokens
    Auto-check passed
  • Kicad

    aklofas/kicad-happy

    Analyze KiCad projects and PDF schematics: schematics, PCB layouts, Gerbers, footprints, symbols, netlists, and design rules.

    1.4k GitHub starsUsed in 1 repo~20k tokens
    Auto-check passed
  • Lcsc

    aklofas/kicad-happy

    Search LCSC Electronics for electronic components — find parts by LCSC number (Cxxxxx) or MPN, check stock/pricing, download datasheets, analyze specifications.

    1.4k GitHub starsUsed in 1 repo~3k tokens
    Auto-check passed

Questions about Datasheets

What does Datasheets do?

Extract structured specifications from electronic component datasheet PDFs — pinouts, electrical characteristics, peripherals, topology, and features. Datasheets is an agent skill from aklofas/kicad-happy. Extract structured specifications from electronic component datasheet PDFs — pinouts, electrical characteristics, peripherals, topology, and features.

When should I use Datasheets?

Datasheets fits situations like: the user asks to extract; read specs from a component datasheet; analyzers need verified IC knowledge (EN pin thresholds; USB peripheral speed).

How do I install Datasheets in Claude Code?

Run `npx skills add aklofas/kicad-happy --skill datasheets -a claude-code`. Or copy the skill folder (skills/datasheets in aklofas/kicad-happy) into .claude/skills/datasheets in your project. Claude Code loads it when a task matches its description.

How do I install Datasheets in Codex?

Run `npx skills add aklofas/kicad-happy --skill datasheets -a codex`. Or copy the skill folder (skills/datasheets in aklofas/kicad-happy) into .agents/skills/datasheets in your project. Codex loads it when a task matches its description.

Can I use Datasheets in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aklofas/kicad-happy --skill datasheets -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/datasheets, .gemini/skills/datasheets, .github/skills/datasheets and .opencode/skills/datasheets in your project.

What does Datasheets need to run?

Going by SKILL.md and its folder, Datasheets needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.

Does Datasheets access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Datasheets safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Datasheets use?

Datasheets is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Datasheets use?

About 2.4k tokens (SKILL.md is roughly 9.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 19k tokens, read only when the agent opens those files.

What are the alternatives to Datasheets?

Skills that share tags, products or a category with Datasheets: Markdown Article Formatter (JimLiu/baoyu-skills, 26k stars), Markitdown (ImCa0/just-laws, 781 stars), Obsidian Markdown (Atmosphere/atmosphere, 3.8k stars) and DOCX (rvdbreemen/OTGW-firmware, 207 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Datasheets?

aklofas (a GitHub user) maintains it in aklofas/kicad-happy, which has 1,350 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 6, 2026.

Source: aklofas/kicad-happy on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.