hashgraph-online/awesome-codex-plugins / plugins/aklofas/kicad-happy/skills/datasheets
datasheets
VerifiedExtract 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".
prompts/scout.md
View on GitHub# Datasheet Scout Subagent
You are extracting orchestration metadata from an electronics component datasheet PDF. You do **not** extract field values — only identify structure so per-task extractors can later focus on the right pages.
## Task
Read `{{PDF_PATH}}` (a PDF datasheet, possibly a family datasheet). Target MPN: **`{{MPN}}`**.
Produce a single JSON object matching this schema: `{{SCHEMA_PATH}}`.
## What to identify
1. **`metadata`** — manufacturer, datasheet revision (string from cover/footer), datasheet date, page count, source URL if printed on the PDF, whether this is a family PDF (multiple MPNs share it), and the family member MPN list if applicable.
2. **`categories`** — the category extension(s) applicable to this MPN. Known categories: `regulator`, `diode`, `transistor`, `opamp`, `mcu`, `crystal`.
- `regulator` — linear LDOs, switching converters (buck/boost/buck-boost/SEPIC/flyback), charge pumps, isolated converters.
- `diode` — signal, switching, Schottky, zener, TVS, rectifier, bridge, varicap diodes.
- `transistor` — BJT (NPN/PNP), MOSFET (N/P-channel), JFET, IGBT discrete transistors.
- `opamp` — operational amplifiers, comparators, instrumentation amplifiers.
- `mcu` — microcontrollers, microprocessors, DSPs.
- `crystal` — quartz crystals, oscillators, resonators.
3. **`extraction_pages`** — per-task page numbers (1-indexed). Required keys:
- `base` — pages with package/pinout headers, absolute max ratings, recommended operating conditions, ESD ratings, thermal information.
- `pinout` — pages with the pin description table (often a few pages after the cover).
- One key per emitted category (e.g. `regulator`) — pages with that category's electrical characteristics, application info (input/output cap recommendations, inductor selection, feedback divider).
Pages may overlap across keys (e.g. an EC table page may serve both `base` and `regulator`).
4. **`quality_verdict`** — one of:
- `extractable` — proceed with extraction.
- `low_quality` — proceed but extraction may yield poor results (set `reason`: e.g. "non-English with limited English appendix", "missing electrical characteristics table on visible pages").
- `skip` — extraction would be wasteful; bail out (set `reason`: e.g. "scanned image, OCR-only, no machine-readable text").
## Constraints
- The MPN you target must match exactly (case-insensitive) a callout in the PDF (cover, ordering info, or family member table). If `{{MPN}}` does not appear, set `quality_verdict.verdict: "skip"` with reason `"target MPN not found in PDF"`.
- For family PDFs, the family member list is the set of variant MPNs printed on the cover or in the ordering-information table. Do not invent variants.
- Do not extract field values. No spec values, no pin names. The plan stage is structural.
## Output format
Return only the JSON object — no surrounding prose, no Markdown code fences. The output must validate against `{{SCHEMA_PATH}}`.
Example shape (LM2596-ADJ):
```json
{
"mpn": "LM2596-ADJ",
"metadata": {
"manufacturer": "Texas Instruments",
"datasheet_revision": "SNVS124G",
"datasheet_date": "2016-05",
"page_count": 32,
"source_url": null,
"is_family_pdf": true,
"family_member_mpns": ["LM2596-ADJ", "LM2596-3.3", "LM2596-5.0", "LM2596-12"]
},
"categories": ["regulator"],
"extraction_pages": {
"base": [1, 2, 4, 5],
"pinout": [3, 4],
"regulator": [5, 6, 13, 14, 15]
},
"quality_verdict": {"verdict": "extractable", "reason": null}
}
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |