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/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}
}
```
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