Skip to content

hashgraph-online/awesome-codex-plugins / plugins/aklofas/kicad-happy/skills/datasheets

datasheets

Verified

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

FileKindSize
SKILL.mdskill md11.2 KB
datasheet_types/__init__.pyscript1.9 KB
datasheet_types/base_block.pyscript6.5 KB
datasheet_types/cache_reader.pyscript12.3 KB
datasheet_types/codec.pyscript6.3 KB
datasheet_types/extraction.pyscript8.0 KB
datasheet_types/pinout.pyscript5.2 KB
datasheet_types/regulator.pyscript5.3 KB
datasheet_types/spec_value.pyscript2.4 KB
datasheet_types/trust_gating.pyscript5.0 KB
distributor_core/__init__.pyscript0 B
distributor_core/cli.pyscript2.9 KB
distributor_core/download.pyscript36.7 KB
distributor_core/inputs.pyscript9.0 KB
distributor_core/manifest.pyscript5.7 KB
distributor_core/sync.pyscript21.0 KB
distributor_core/verify.pyscript12.1 KB
examples/abm8g-106-12.000mhz-t.jsonconfig9.4 KB
examples/irlml6344.jsonconfig16.0 KB
examples/lm2596-adj.jsonconfig14.3 KB
examples/lm358.jsonconfig15.6 KB
examples/mbrs540t3g.jsonconfig12.3 KB
examples/stm32f103c8t6.jsonconfig51.1 KB
prompts/base.mdmarkdown4.5 KB
prompts/crystal.mdmarkdown8.8 KB
prompts/diode.mdmarkdown8.3 KB
prompts/mcu.mdmarkdown9.6 KB
prompts/opamp.mdmarkdown10.7 KB
prompts/pinout.mdmarkdown4.7 KB
prompts/regulator.mdmarkdown4.4 KB
prompts/scout.mdmarkdown3.5 KB
prompts/transistor.mdmarkdown12.5 KB
references/cache-layout.mdmarkdown8.4 KB
references/consumer-api.mdmarkdown10.8 KB
references/dispatch-claude-code.mdmarkdown9.4 KB
references/dispatcher-contract.mdmarkdown8.2 KB
references/extraction-pipeline.mdmarkdown1.7 KB
references/extraction-schema.mdmarkdown18.0 KB
references/field-extraction-guide.mdmarkdown14.9 KB
references/quality-scoring.mdmarkdown8.4 KB
schemas/CHANGELOG.mdmarkdown16.0 KB
schemas/base.schema.jsonconfig9.3 KB
schemas/crystal.schema.jsonconfig7.2 KB
schemas/diode.schema.jsonconfig7.9 KB
schemas/extraction.schema.jsonconfig3.7 KB
schemas/fixtures/lm2596-adj.example.jsonconfig14.3 KB
schemas/fixtures/manifest.example.jsonconfig1000 B
schemas/fixtures/minimal.example.jsonconfig2.1 KB
schemas/manifest.schema.jsonconfig3.0 KB
schemas/mcu.schema.jsonconfig12.4 KB
schemas/opamp.schema.jsonconfig9.2 KB
schemas/pinout.schema.jsonconfig5.9 KB
schemas/plan.schema.jsonconfig4.6 KB
schemas/regulator.schema.jsonconfig8.4 KB
schemas/scout.schema.jsonconfig2.9 KB
schemas/spec_value.schema.jsonconfig3.0 KB
schemas/transistor.schema.jsonconfig12.0 KB
scripts/_smoke_v14_roundtrip.pyscript8.9 KB
scripts/datasheet_extract_cache.pyscript21.2 KB
scripts/datasheet_features.pyscript17.1 KB
scripts/datasheet_page_selector.pyscript16.7 KB
scripts/datasheet_score.pyscript15.5 KB
scripts/datasheet_verify.pyscript45.6 KB
scripts/extraction_schema.pyscript1.8 KB
scripts/merge_results.pyscript13.0 KB
scripts/plan_extraction.pyscript9.5 KB
scripts/validate_extraction_result.pyscript4.0 KB
scripts/validate_sanity_vector.pyscript6.4 KB

prompts/pinout.md

View on GitHub
# Datasheet Pinout Extractor Subagent

You are extracting the **pinout** (per-pin description table) from an electronics component datasheet PDF.

## Task

Read `{{PDF_PATH}}` (focus pages: `{{PAGES}}`). Target MPN: **`{{MPN}}`**.

Produce a single JSON **array** of pin objects matching this schema: `{{SCHEMA_PATH}}`.

## Field guide (per pin object)

- `numbers`: array of strings — pin numbers/letters as printed (e.g. `["1"]` or `["A1", "B1"]` for pins exposed on multiple package locations). For BGA, use the alphanumeric grid identifier.
- `name`: pin name as printed (e.g. `VIN`, `OUT`, `GND`, `EN`, `FB`, `PA0/USART2_CTS`).
- `type`: exactly one of `input`, `output`, `bidirectional`, `tri_state`, `passive`, `open_collector`, `open_emitter`, `power_in`, `power_out`, `not_connected`, `unspecified` (the KiCad ERC pin types; the schema rejects anything else). Choose the closest match: supplies and grounds are `power_in` (a regulator's output rail is `power_out`), analog inputs/outputs are `input`/`output` with `subtype: "analog"`, open-drain and open-collector outputs are `open_collector`, open-emitter outputs `open_emitter`, three-state outputs `tri_state`, a no-connect is `not_connected`, an exposed thermal pad is `passive` with `subtype: "thermal_pad"`, reset/boot/clock/oscillator/debug/data pins take their direction (`input`, `output`, `bidirectional`) with the role in `subtype`.
- `subtype`: optional free-form refinement (e.g. `switching` for a switcher's OUT pin, `analog`, `open_drain`, `thermal_pad`, `reset`, `clock`, `usb`, `i2c`, `spi`, `pwm`); null when none.
- `description`: pin's functional description from the datasheet.
- `power_domain`: name of the supply rail the pin is referenced to (e.g. `VIN`, `VDD`, `VDDIO`, `VBAT`). Must be a key in `base.recommended_operating` when populated. Null for ground or signal pins not domain-tagged. A supply pin is range-checked against that entry only when its `type` is `power_in` and it has a `power_domain`; a signal pin's `power_domain` is not range-checked.
- `alt_functions`: array of objects `{name, peripheral, role, af_code}` — alternate functions multiplexed onto this pin (MCU pins often have many). E.g. `{"name": "USART1_TX", "peripheral": "USART1", "role": "TX", "af_code": "AF7"}`; `role` and `af_code` may be null. Never plain strings.
- `is_5v_tolerant`: bool or null (signal pins on MCUs).
- `absolute_max`: SpecValue list (per-pin abs max if pin-specific, e.g. CMOS input vs. high-V tolerant input). Null if covered by base block.
- `recommended`: SpecValue list (per-pin recommended levels).
- `drive_strength`: SpecValue list for output pins (mA capability).
- `notes`: free-form caveats.
- `evidence`: required `{page, section, confidence, method}`.

## Hard rules

1. **Each pin number gets exactly one entry.** If two pins share a function and number range (e.g. `GND` on pins 7-12), emit one entry with `numbers: ["7","8","9","10","11","12"]`.
2. **The pin count must match `base.package.pin_count`** when known. For thermal pads, emit a separate entry with `type: "passive"` and `subtype: "thermal_pad"` if numbered.
3. **Power-domain references** must use the same identifier as the `base.recommended_operating` keys. If `recommended_operating` has `VIN`, the pinout must say `power_domain: "VIN"` — not `"V_IN"` or `"vin"`. The verifier flags mismatches as warnings.
4. **No invention.** If the datasheet doesn't list alt functions, use `[]`. If 5V-tolerance is unspecified, use `null`, not `false`.
5. **Family PDFs**: emit the pinout for the package referenced by `{{MPN}}`. For LM2596-ADJ, that is the TO-220 NDZ or TO-263 NDH (5-pin). If the variant has multiple package options, pick the one the family-PDF cover lists for the MPN; record the choice in `notes` of pin 1.

## Output format

Return a JSON array. No prose, no Markdown fences. Output must validate against `{{SCHEMA_PATH}}`.

Example (LM2596-ADJ, TO-263 NDH; an excerpt showing pins 1 and 2 of the five-pin part):

```json
[
  {"numbers": ["1"], "name": "VIN", "type": "power_in", "subtype": null,
   "description": "Input voltage", "power_domain": "VIN",
   "alt_functions": [], "is_5v_tolerant": null, "absolute_max": null,
   "recommended": null, "drive_strength": null, "notes": null,
   "evidence": {"page": 3, "section": "Pin Configuration and Functions", "confidence": "high", "method": "table"}},
  {"numbers": ["2"], "name": "OUT", "type": "output", "subtype": "switching",
   "description": "Switching output (inductor connects here)", "power_domain": null,
   "alt_functions": [], "is_5v_tolerant": null, "absolute_max": null,
   "recommended": null, "drive_strength": null, "notes": null,
   "evidence": {"page": 3, "section": "Pin Configuration and Functions", "confidence": "high", "method": "table"}}
]
```
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall