akcli-datasheet-facts
/akcli-datasheet-facts
Wyciąga z kart katalogowych sprawdzone fakty o komponentach (Vref, kondensatory kwarcu, wartości graniczne, termika) do magazynu akcli, by ustalenia przeglądu miały oparcie w dokumentacji.
- Autor
- tipoli5890 ↗
- Repozytorium
- akcli ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 25.08.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 25.08.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Wyciąga z kart katalogowych sprawdzone fakty o komponentach (Vref, kondensatory kwarcu, wartości graniczne, termika) do magazynu akcli, by ustalenia przeglądu miały oparcie w dokumentacji.
Wyzwalacze z opisu
Oryginalny opis (EN)
Extract audited, PDF-pinned component facts into the akcli datasheet facts store (`akcli review facts`) so review findings upgrade from heuristic to datasheet_backed. Use this skill whenever the task involves: reading a component datasheet to record its Vref / crystal load capacitance / absolute maximum / thermal numbers; building or verifying `datasheets/extracted/` facts files; upgrading `akcli review analyze` findings to datasheet_backed; or checking why a finding says "verify against the datasheet". Triggers on: datasheet facts, facts store, extract datasheet, Vref, load capacitance, absol
Jak działa
- Extraction doctrine (non-negotiable)
- Workflow
- Failure modes to refuse
- When NOT to use this skill
Podgląd SKILL.md
---
name: akcli-datasheet-facts
description: >-
Extract audited, PDF-pinned component facts into the akcli datasheet facts
store (`akcli review facts`) so review findings upgrade from heuristic to
datasheet_backed. Use this skill whenever the task involves: reading a
component datasheet to record its Vref / crystal load capacitance / absolute
maximum / thermal numbers; building or verifying `datasheets/extracted/`
facts files; upgrading `akcli review analyze` findings to datasheet_backed;
or checking why a finding says "verify against the datasheet". Triggers on:
datasheet facts, facts store, extract datasheet, Vref, load capacitance,
absolute maximum, theta_ja, 資料表, 元件參數擷取, datasheet_backed,
review facts.
---
# akcli-datasheet-facts — audited facts extraction, the agent half of the loop
You (the agent) are the extractor: you can read PDFs natively, and the facts
store is designed around that. akcli owns the *discipline* — every fact is
pinned to its source PDF by sha256 + page (+ verbatim quote), and
`review facts verify` audits what you wrote. Your job is to fill the store
honestly; akcli's job is to catch you if you don't.
**The prize:** a heuristic finding ("verify Vref against the datasheet")
becomes a `datasheet_backed` judgement with the exact page as evidence — and
`review propose` can then emit an auto-applicable fix. No fact, no claim.
## Extraction doctrine (non-negotiable)
- **Read the actual PDF.** Never fill a fact from memory, a search snippet, or
a "typical value" you believe. If you cannot open the PDF, stop and say so.
- **Page-accurate, quote-verbatim.** The `page` is where the number IS, not
where the section starts. A `quote` is copied character-for-character from
that page — `verify` runs a text match against the PDF (when `pdftotext` is
installed) and a mismatch is a WARNING with your name on it.
- **min/typ/max as printed.** Record the row as the table gives it; do not
average, do not pick a bound and call it `value`. Conditions
(temperature, load) go in `conditions`.
- **Absence is honest.** A part whose datasheet does not state a number gets
NO fact for it. Detectors fall back to their heuristics — never to a guess.
- **One MPN, one file.** Facts are keyed by the exact MPN; a variant with
different numbers (voltage options, grades) is its own facts file. The
schematic component must carry that MPN (a parameter, or the exact Value) or
the facts never bind: `review analyze` reports `REVIEW_FACTS_UNMATCHED` (NOTE,
plus a `facts_unmatched` list in the metadata) for every facts file that
matched no component. Treat that as a failed extraction, not a clean run —
the findings you meant to harden are still heuristic.
## Workflow
### Step 1 — Get the PDF (hash included)
```bash
akcli jlc datasheet board.kicad_sch --fetch --out datasheets # whole-BOM batch into ./datasheets/
akcli jlc datasheet C2984661 --fetch --out datasheets # or one LCSC part
```
PDFs land under `--out` (default: `AKCLI_DATASHEET_DIR` or
`~/.cache/akcli/datasheets` — a personal cache). The facts store itself is
project-local by design (`review facts` defaults to `./datasheets`): facts
are a committed team asset that survives handoff, so pass `--out datasheets`
(as above) to co-locate the PDFs with the store, or leave PDFs in the cache
and only commit `datasheets/extracted/`. PDFs are named
`C<lcsc>_<MPN>.pdf`. Without `--fetch`, the command only resolves datasheet
URLs and does not download anything. A vendor PDF you were given by the user
works too — put it in `datasheets/` yourself.
### Step 2 — Read the PDF and extract
Open the PDF with your Read tool. Find the electrical-characteristics /
recommended-operating tables. Extract the fact keys the detectors consume:
| key | what | unit | upgrades |
|---|---|---|---|
| `vref` | regulator feedback reference | V | FB-divider review → `REVIEW_FB_DIVIDER_VREF_MISMATCH` + auto retune proposal |
| `load_capacitance` | crystal CL | F | crystal review → `REVIEW_XTAL_LOAD_MISMATCH` + cap-value proposal |
| `abs_max_io` | pin absolute maximum | V | voltage-domain review → verified-tolerant / confirmed-violation |
| `theta_ja` | junction-ambient thermal resistance | K/W | junction-temperature estimate |
| `power_dissipation` | design dissipation (from the review context) | W | junction-temperature estimate |
| `t_j_max` | junction limit | °C | junction-temperature limit |
Any other `lower_snake_case` key is schema-legal — record what the design
needs; detectors ignore what they don't consume yet.
### Step 3 — Record, with the page
```bash
akcli review facts add TPS61023DRLR --pdf datasheets/C123456_TPS61023DRLR.pdf --set vref=0.6V@5
akcli review facts add ABM8-8.000MHZ --pdf datasheets/C123_ABM8.pdf --set load_capacitance=10pF@3 --method llm
```
`--set KEY=VALUE[UNIT]@PAGE` handles engineering notation (`0.6V`, `12pF`,
`3mA`). **Always pass `--method llm` when you extracted the numbers** — the
store records HOW numbers arrived, and lying about it defeats the audit.
For min/typ/max rows and quotes, edit the JSON directly
(`datasheets/extracted/<MPN>.json` — fields `min`/`typ`/`max`/`quote`/
`conditions` per fact), then verify.
### Step 4 — Verify (the honesty gate)
```bash
akcli review facts verify
akcli review facts lookup TPS61023DRLR vref
```
`verify` audits: schema shape, the PDF exists, **sha256 staleness** (the PDF
changed since extraction → ERROR: re-verify every fact), page bounds, and
quote presence via the optional `pdftotext` driver. `FACTS_QUOTE_UNVERIFIED`
(NOTE) means the tool is absent — the check did not run; say so in your
report rather than claiming verification.
### Step 5 — Re-analyze and watch findings upgrade
```bash
akcli review analyze board.kicad_sch --facts datasheets --json
```
(`--facts` is auto-discovered when `datasheets/extracted/` sits next to the
schematic.) Compare confidence fields before/after: `heuristic` findings that
consumed your facts now read `datasheet_backed`, carry
`evidence.datasheet.{sha256,page,quote}`, and — for value fixes — produce
auto-applicable `review propose` drafts whose contract fragments cite the
same page. That is the sedimentation chain: PDF → fact → finding → proposal
→ contract evidence.
## Failure modes to refuse
- Filling `vref=1.25V` "because most shunt references are" — that is a guess
wearing a fact's clothes; the whole store exists to prevent it.
- Quoting a *search result* or another part's datasheet.
- Bumping a stale sha256 by re-running `facts add` without re-checking every
recorded number against the NEW pdf revision.
- Marking `--method manual` for numbers you extracted (audit trail lies).
## When NOT to use this skill
- Sourcing/purchasability questions → akcli-parts-sourcing.
- Producing LLM *review findings* (not facts) → akcli-deep-review; facts feed
it, but candidates go through `review validate`, not the facts store.
- Running the review itself → akcli-schematic-review.
Wersje
W bazie nie ma innych skilli o nazwie akcli-datasheet-facts.
Migawka bazy z 13.11.2026 · wersja paczki 1a9968765f27 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100akcli-deep-review
Generuje kandydackie uwagi do przeglądu projektu elektroniki przez LLM i przepuszcza je przez akcli review validate, rozdzielając uwagi przyjęte od wstrzymanych. - 100akcli-parts-sourcing
Dobiera zamawialne części do schematu przez akcli jlc: przeszukuje katalog JLCPCB i LCSC, sprawdza stany i ceny, konwertuje części do bibliotek KiCad i pobiera karty katalogowe. - 100datasheets
Wyciąga z PDF-ów z kartami katalogowymi komponentów elektronicznych piny, parametry elektryczne i peryferia, a wyniki zapisuje per projekt dla analizatorów KiCad, EMC, SPICE i thermal. - 100datasheet-interpreter
Wyciąga kluczowe parametry z not katalogowych komponentów w PDF dla projektów makerskich: przypisanie pinów, adresy I2C, wymagania czasowe i mapy rejestrów. - 100ee-datasheet-master
Wyszukuje parametry układów w kartach katalogowych: rozkład wyprowadzeń, napięcia, adres I2C, czasy, mapę rejestrów i charakterystyki elektryczne dla wszystkich typów IC. - 100nex-datasheet-extractor
Wyciąga z kart katalogowych PDF parametry elektryczne, dane obudowy i status zgodności do formatu JSON lub CSV.