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/regulator.md

View on GitHub
# Datasheet Regulator Extractor Subagent

You are extracting the **regulator category extension** (topology, voltages, currents, frequencies, application capacitor/inductor recommendations, stability conditions) from an electronics component datasheet PDF.

## Task

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

Produce a single JSON object matching this schema: `{{SCHEMA_PATH}}`.

## Field guide

- `topology`: enum. Choose the single closest match: `ldo` (linear), `buck` (step-down switcher), `boost` (step-up), `buck_boost`, `sepic`, `flyback`, `charge_pump`, `isolated`. The cover/Features section usually announces the topology.
- `vin_range`, `vout_range`: SpecValue lists (`min`, `max`, `unit: "V"`).
- `iout_max`: SpecValue list (`max`, `unit: "A"`, `condition` may carry temp/heatsinking note).
- `reference_voltage`: SpecValue list (adjustable parts only — e.g. LM2596-ADJ has 1.23V typ; fixed parts use null).
- `feedback_pin`, `compensation_pin`, `enable_pin`, `power_good_pin`: pin number strings matching `base.pinout[].numbers` exactly. Null when N/A.
- `cin_min`, `cout_min`: SpecValue list (`min`, `unit: "F"` — capacitance in Farads, NOT µF). The application section recommends these.
- `inductor_range`: SpecValue list (`min`, `max`, `unit: "H"`) for switchers.
- `switching_freq`: SpecValue list (`typ`, `unit: "Hz"`) for switchers; null for LDOs/charge pumps that aren't fixed-frequency.
- `dropout`: SpecValue list (`typ`, `max`, `unit: "V"`) for LDOs only; null for switchers.
- `psrr`, `line_regulation`, `load_regulation`: SpecValue lists; populate when called out.
- `stability_conditions`: object with `cap_types_allowed` (array of strings from `ceramic` (the datasheet says ceramic without a dielectric), `ceramic_c0g`, `ceramic_x5r`, `ceramic_x7r`, `ceramic_x7s`, `tantalum`, `polymer`, `electrolytic`, `film`), `esr_range` (SpecValue list, `unit: "Ω"`), `notes`, `evidence`. Null when datasheet does not specify.
- `sequencing`: pre-defined sequencing requirements (multi-rail PMICs); null for single-output regulators.

## Hard rules

1. **Canonical SI units.** Capacitance in F (NOT µF — store 470µF as `4.7e-4` with `unit: "F"`). Inductance in H. Frequency in Hz. Voltage in V. Current in A. Resistance in Ω. The verifier rejects µF/nF/pF strings.
2. **Pin references must use exact pin numbers from the pinout extraction.** When the regulator extractor runs in parallel with pinout, infer pin numbers from the datasheet's pin description block (which is on the same pages you have access to). If a referenced pin isn't on your pages, use the pin name in `notes` and leave the pin field null.
3. **Family PDF disambiguation.** For LM2596-ADJ specifically: most fields are family-wide. The `vout_range` is variant-specific (-ADJ has wide adjustable range; fixed variants have a single nominal Vout). Use the -ADJ row in the ordering info table.
4. **Every SpecValue requires `evidence`** with `page`, `section`, `confidence`, `method`.
5. **OMIT fields you cannot find** with null. Do not guess. A missing `inductor_range` is much better than a hallucinated one.

## Output format

Return only the JSON object. No prose, no fences. Output must validate against `{{SCHEMA_PATH}}`.

Example (LM2596-ADJ):

```json
{
  "topology": "buck",
  "vin_range": [{"min": 4.5, "max": 40, "unit": "V", "typ": null, "condition": null, "notes": null,
                 "evidence": {"page": 5, "section": "Recommended Operating Conditions", "confidence": "high", "method": "table"}}],
  "vout_range": [{"min": 1.23, "max": 37, "unit": "V", "typ": null, "condition": null, "notes": "Adjustable via FB divider",
                  "evidence": {"page": 1, "section": "Features", "confidence": "medium", "method": "prose"}}],
  "iout_max": [{"max": 3, "unit": "A", "min": null, "typ": null, "condition": "with adequate heatsinking", "notes": null,
                "evidence": {"page": 1, "section": "Features", "confidence": "medium", "method": "prose"}}],
  "reference_voltage": [{"min": 1.18, "typ": 1.23, "max": 1.28, "unit": "V", "condition": null, "notes": null,
                         "evidence": {"page": 5, "section": "Electrical Characteristics", "confidence": "high", "method": "table"}}],
  "switching_freq": [{"typ": 150000, "unit": "Hz", "min": null, "max": null, "condition": null, "notes": null,
                      "evidence": {"page": 5, "section": "Electrical Characteristics", "confidence": "high", "method": "table"}}],
  "feedback_pin": "4",
  "enable_pin": "5"
}
```
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