chip-sourcing-skillpack
Public Unreviewedby John Lauer
Native-browser-first parts sourcing for the whole electronics industry — drive the user's signed-in Chrome/Edge (adom-browser-extension) for real logins + no bot-walls. Root strategy skill + one sub-skill per website. chip-fetcher's default.
Skills
The skills this repo ships, by tier, each with a quick health read. Install the user skills with:
adom-wiki skills install john/chip-sourcing-skillpackNative-browser-first strategy for sourcing electronic parts (chip-fetcher and any EE-site task). Drive the user's REAL signed-in Chrome/Edge via the adom-browser-extension so cookies/SSO/saved-logins/captcha-trust all work — no auth to recreate in pup, and it bypasses bot-walls (DigiKey blocks pup). Sub-skills cover one website each. Triggers: search DigiKey/Mouser/SnapEDA/Arrow, source a part, fetch CAD, find a chip, parametric search, chip-fetcher.
(Template) Source parts from <SITE> via the native signed-in browser. Copy this folder to skills/<site>/ and fill in the search URL, extraction selectors, login/cookie notes, and whether pup is blocked.
Source parts from DigiKey via the native signed-in browser. DigiKey HARD-BLOCKS pup — the native browser is required. Keyword search, parametric category drill, MPN extraction.
Source from the chip MANUFACTURER first (ST/TI/Nordic/NXP/...) via the native browser — the authoritative family list, datasheets, and official CAD. Manufacturer-first is the top of chip-fetcher's ladder.
Source parts from Mouser via the native signed-in browser. Keyword + manufacturer-filtered search, MPN + stock + price extraction.
Pull symbol/footprint/3D CAD from SnapEDA via the native signed-in browser — login-gated downloads work because the profile is already authenticated.
No dev skills in this repo.
How to build, debug, and test this app. Source-only (dev-skills/), never shipped in the tarball.
No publish skills in this repo.
The app-to-wiki publish glue. Source-only (publish-skills/), never shipped in the tarball.
Health: the size chip is green when right-sized, yellow when getting long, red when the model likely skims it. A green check is a passed preamble/structure signal; an amber mark is a gentle nudge, not a hard failure.