[DEPRECATED] Chip Fetcher → adom-chip-fetcher

← All Pull Requests

Content fix: adompkg → adom-wiki CLI, retire dead wiki host #14

Diff

--- a/README.md+++ b/README.md@@ -1,64 +1,64 @@-> # ⚠️ DEPRECATED-> **This page is deprecated. The official app is now [adom/adom-chip-fetcher](https://wiki.adom.inc/adom/adom-chip-fetcher).** Install it with `adompkg install adom/adom-chip-fetcher`. This page is no longer maintained.--# chip-fetcher--Download manufacturer-grade chip CAD bundles (STEP + KiCAD symbol + KiCAD footprint + datasheet + design-help PDFs) into a structured library by driving Chrome via [pup](https://github.com/adom-inc/adom-desktop).--The defining rule: **fetch from the manufacturer's own website first** — only fall back to Mouser, DigiKey, or Component Search Engine when the manufacturer doesn't self-host CAD, and only with explicit user approval.--## What it does--```bash-chip-fetcher fetch TPS62840            # opens the TI page → UL deep-link → drives the form → auto-pulls-chip-fetcher pull '<windows-path>'     # pulls a downloaded zip from the user's desktop-chip-fetcher import path/to/zip --mpn  # absorbs a downloaded file into library/<MPN>/-chip-fetcher list                       # shows what's in library/ vs missing per slot-chip-fetcher login <source>             # opens a vendor login page in the chip-fetcher pup profile-chip-fetcher install                    # deploys SKILL.md to ~/.claude/skills/chip-fetcher/-```--After running, each chip lands in:--```-library/<MPN>/-├── <MPN>.step          # rich manufacturer STEP, named PRODUCTs (Body, ThermalPin, PinsArrayLR, PinsArrayTB)-├── <MPN>.kicad_sym-├── <MPN>.kicad_mod-├── <MPN>.pdf           # datasheet-├── <MPN>-errata-*.pdf-├── <MPN>-appnote-*.pdf-├── <MPN>-hwguide.pdf-└── info.json           # provenance trail (mfr-direct vs mouser-fallback)-```--## Verified vendors--| Vendor | Path | Notes |-|---|---|---|-| Texas Instruments | `vendor.ultralibrarian.com/TI/embedded/...` | mfr-direct via UL |-| STMicroelectronics | `vendor.ultralibrarian.com/stmicro/embedded/...` | mfr-direct via UL |-| Analog Devices | `vendor.ultralibrarian.com/adi/embedded/...` | mfr-direct via UL |-| Microchip | `vendor.ultralibrarian.com/microchip/...` | mfr-direct via UL (iframe) |-| NXP | `nxp.com` (BXL) + `nxp.componentsearchengine.com` (STEP) | mfr-direct |-| Espressif | Mouser ECAD-Model fallback | mfr-uploaded to SamacSys |-| Lattice | Mouser ECAD-Model fallback | mfr-uploaded to SamacSys |-| Renesas | Mouser ECAD-Model fallback | mfr-uploaded to SamacSys |--See [SKILL.md](https://wiki-ufypy5dpx93o.adom.cloud/apps/chip-fetcher) for the full skill documentation, vendor URL patterns, and the failure-mode notes captured from real Adom-user feedback.--## Install--```bash-curl -fsSL https://wiki-ufypy5dpx93o.adom.cloud/static/apps/chip-fetcher/chip-fetcher \-  -o /usr/local/bin/chip-fetcher && chmod +x /usr/local/bin/chip-fetcher && chip-fetcher install-```--## Companion specs--Two adom-desktop fix-it specs live in [scripts/](scripts/):--- `adom-desktop-pullfile-speed-prompt.md` — streaming binary WS frames + HTTP fallback so 50+ MB files (NXP reference manuals) don't time out-- `adom-desktop-credential-vault-prompt.md` — DPAPI/Keychain-encrypted credential vault hooked into `puppeteer.page.authenticate()` so basic-auth popups never appear--Paste either into Claude Code on the desktop to implement.+> # ⚠️ DEPRECATED+> **This page is deprecated. The official app is now [adom/adom-chip-fetcher](https://wiki.adom.inc/adom/adom-chip-fetcher).** Install it with `adom-wiki pkg install adom/adom-chip-fetcher`. This page is no longer maintained.++# chip-fetcher++Download manufacturer-grade chip CAD bundles (STEP + KiCAD symbol + KiCAD footprint + datasheet + design-help PDFs) into a structured library by driving Chrome via [pup](https://github.com/adom-inc/adom-desktop).++The defining rule: **fetch from the manufacturer's own website first** — only fall back to Mouser, DigiKey, or Component Search Engine when the manufacturer doesn't self-host CAD, and only with explicit user approval.++## What it does++```bash+chip-fetcher fetch TPS62840            # opens the TI page → UL deep-link → drives the form → auto-pulls+chip-fetcher pull '<windows-path>'     # pulls a downloaded zip from the user's desktop+chip-fetcher import path/to/zip --mpn  # absorbs a downloaded file into library/<MPN>/+chip-fetcher list                       # shows what's in library/ vs missing per slot+chip-fetcher login <source>             # opens a vendor login page in the chip-fetcher pup profile+chip-fetcher install                    # deploys SKILL.md to ~/.claude/skills/chip-fetcher/+```++After running, each chip lands in:++```+library/<MPN>/+├── <MPN>.step          # rich manufacturer STEP, named PRODUCTs (Body, ThermalPin, PinsArrayLR, PinsArrayTB)+├── <MPN>.kicad_sym+├── <MPN>.kicad_mod+├── <MPN>.pdf           # datasheet+├── <MPN>-errata-*.pdf+├── <MPN>-appnote-*.pdf+├── <MPN>-hwguide.pdf+└── info.json           # provenance trail (mfr-direct vs mouser-fallback)+```++## Verified vendors++| Vendor | Path | Notes |+|---|---|---|+| Texas Instruments | `vendor.ultralibrarian.com/TI/embedded/...` | mfr-direct via UL |+| STMicroelectronics | `vendor.ultralibrarian.com/stmicro/embedded/...` | mfr-direct via UL |+| Analog Devices | `vendor.ultralibrarian.com/adi/embedded/...` | mfr-direct via UL |+| Microchip | `vendor.ultralibrarian.com/microchip/...` | mfr-direct via UL (iframe) |+| NXP | `nxp.com` (BXL) + `nxp.componentsearchengine.com` (STEP) | mfr-direct |+| Espressif | Mouser ECAD-Model fallback | mfr-uploaded to SamacSys |+| Lattice | Mouser ECAD-Model fallback | mfr-uploaded to SamacSys |+| Renesas | Mouser ECAD-Model fallback | mfr-uploaded to SamacSys |++See [SKILL.md](https://wiki.adom.inc/adom/chip-fetcher) for the full skill documentation, vendor URL patterns, and the failure-mode notes captured from real Adom-user feedback.++## Install++```bash+adom-wiki pkg install adom/chip-fetcher   # (deprecated — prefer adom/adom-chip-fetcher)+```++## Companion specs++Two adom-desktop fix-it specs live in [scripts/](scripts/):++- `adom-desktop-pullfile-speed-prompt.md` — streaming binary WS frames + HTTP fallback so 50+ MB files (NXP reference manuals) don't time out+- `adom-desktop-credential-vault-prompt.md` — DPAPI/Keychain-encrypted credential vault hooked into `puppeteer.page.authenticate()` so basic-auth popups never appear++Paste either into Claude Code on the desktop to implement.+--- a/skills/SKILL.md+++ b/skills/SKILL.md@@ -1,84 +1,85 @@-----name: chip-fetcher-sites-description: >--  The chip-fetcher SOURCE-SITE skill pack — one installable skill per vendor-  website that chip-fetcher crawls (SnapEDA, Mouser, DigiKey, Ultra Librarian,-  Arrow, manufacturer sites…). Each sub-skill teaches the AI how to navigate-  THAT site's CAD-download flow through pup: the URL patterns, the login/gate,-  the download button dance, and — crucially — how to get unstuck when a site-  changes its layout or blocks automation. Third parties extend the pack by-  contributing a skill for a site they've figured out. Read this before driving-  chip-fetcher against a vendor site, or when a fetch gets stuck on a site whose-  layout or anti-bot defenses changed. Trigger words: chip-fetcher site, source-  site, vendor navigation, snapeda navigation, digikey blocked, mouser cad,-  ultralibrarian, site skill, crawl site, fetch stuck, anti-bot, captcha,-  download flow, add a site skill, contribute site skill.------# chip-fetcher source-site skill pack--chip-fetcher is an **open-source Page** (source public + `adompkg install`-able)-that *also carries a skill pack in the same repo*. The app is the crawler; this-pack is the **per-site navigation knowledge** the AI uses to drive it. They ship-together so the code and the know-how version in lockstep — but the know-how is-the part the community can extend without touching Rust.--## Why per-site skills--Every vendor site has its own CAD-download choreography, and they change it-without notice. SnapEDA gates behind a login; DigiKey periodically tightens-anti-bot and **blocks pup outright**; Mouser buries the 3D model behind a tab;-manufacturer sites (TI, ST, NXP, Nordic…) each have a different "CAD / Symbols &-Footprints" path. Hard-coding all of that in the binary means a site change is a-release. Capturing it as **a skill per site** means:--- the AI reads the current site's skill before navigating, so it knows the exact-  flow instead of guessing;-- when a site changes (or blocks us), **anyone** who figures out the new flow can-  fix it by editing one skill — no fork, no Rust, no release;-- the fix is discoverable: it's published to the wiki and the next person's AI-  picks it up.--The canonical sourcing ladder (Mfr → SnapEDA → Mouser → DigiKey → Arrow → CSE/UL-→ LCSC) still lives in the binary (`chip-fetcher sources`); this pack is the-**how-to-drive-each-rung** layer on top of it.--## Layout--```-skills/-├── SKILL.md                 # this file — the pack entry point + ladder-├── CONTRIBUTING.md          # how 3rd parties add / own a site skill-└── sites/-    ├── snapeda/SKILL.md     # the canonical reference flow (login + download)-    ├── digikey/SKILL.md     # incl. the "pup is blocked" recovery playbook-    ├── mouser/SKILL.md-    ├── ultralibrarian/SKILL.md-    └── manufacturer/SKILL.md# generic manufacturer-site approach (TI/ST/NXP/Nordic…)-```--Each `sites/<vendor>/SKILL.md` is a complete, installable skill with its own-trigger words, so the AI auto-surfaces the right one when it's about to touch-that vendor — or when a fetch against it gets stuck.--## What a site skill must contain--1. **Reach** — the canonical product-search / product-page URL pattern for an MPN.-2. **Gate** — login / region / cookie wall, and how the persistent pup profile-   gets past it (which profile, what creds key in `chip-fetcher creds`).-3. **Download flow** — the exact button/tab sequence to the CAD bundle, with the-   selectors or visual cues that identify each step.-4. **Catch** — what the downloaded artifact is (zip? IntLib? per-file?), where it-   lands, and how chip-fetcher pulls it off the desktop.-5. **When it breaks** — the failure signatures (block page, captcha, moved button)-   and the recovery playbook. This is the highest-value section — it's why the-   pack exists.--See `sites/snapeda/SKILL.md` for the template filled in.--## Adding a site--Found a site chip-fetcher doesn't know, or a new way past a block? Write a skill-for it and contribute it — `CONTRIBUTING.md` covers the two paths (PR it into the-pack, or own it in your own wiki repo and link it in). Either way your AI, and-everyone else's, gets smarter the next time that site comes up.+---+name: chip-fetcher-sites+description: >-+  The chip-fetcher SOURCE-SITE skill pack — one installable skill per vendor+  website that chip-fetcher crawls (SnapEDA, Mouser, DigiKey, Ultra Librarian,+  Arrow, manufacturer sites…). Each sub-skill teaches the AI how to navigate+  THAT site's CAD-download flow through pup: the URL patterns, the login/gate,+  the download button dance, and — crucially — how to get unstuck when a site+  changes its layout or blocks automation. Third parties extend the pack by+  contributing a skill for a site they've figured out. Read this before driving+  chip-fetcher against a vendor site, or when a fetch gets stuck on a site whose+  layout or anti-bot defenses changed. Trigger words: chip-fetcher site, source+  site, vendor navigation, snapeda navigation, digikey blocked, mouser cad,+  ultralibrarian, site skill, crawl site, fetch stuck, anti-bot, captcha,+  download flow, add a site skill, contribute site skill.+---++# chip-fetcher source-site skill pack++chip-fetcher is an **open-source Page** (source public + `adom-wiki pkg install`-able)+that *also carries a skill pack in the same repo*. The app is the crawler; this+pack is the **per-site navigation knowledge** the AI uses to drive it. They ship+together so the code and the know-how version in lockstep — but the know-how is+the part the community can extend without touching Rust.++## Why per-site skills++Every vendor site has its own CAD-download choreography, and they change it+without notice. SnapEDA gates behind a login; DigiKey periodically tightens+anti-bot and **blocks pup outright**; Mouser buries the 3D model behind a tab;+manufacturer sites (TI, ST, NXP, Nordic…) each have a different "CAD / Symbols &+Footprints" path. Hard-coding all of that in the binary means a site change is a+release. Capturing it as **a skill per site** means:++- the AI reads the current site's skill before navigating, so it knows the exact+  flow instead of guessing;+- when a site changes (or blocks us), **anyone** who figures out the new flow can+  fix it by editing one skill — no fork, no Rust, no release;+- the fix is discoverable: it's published to the wiki and the next person's AI+  picks it up.++The canonical sourcing ladder (Mfr → SnapEDA → Mouser → DigiKey → Arrow → CSE/UL+→ LCSC) still lives in the binary (`chip-fetcher sources`); this pack is the+**how-to-drive-each-rung** layer on top of it.++## Layout++```+skills/+├── SKILL.md                 # this file — the pack entry point + ladder+├── CONTRIBUTING.md          # how 3rd parties add / own a site skill+└── sites/+    ├── snapeda/SKILL.md     # the canonical reference flow (login + download)+    ├── digikey/SKILL.md     # incl. the "pup is blocked" recovery playbook+    ├── mouser/SKILL.md+    ├── ultralibrarian/SKILL.md+    └── manufacturer/SKILL.md# generic manufacturer-site approach (TI/ST/NXP/Nordic…)+```++Each `sites/<vendor>/SKILL.md` is a complete, installable skill with its own+trigger words, so the AI auto-surfaces the right one when it's about to touch+that vendor — or when a fetch against it gets stuck.++## What a site skill must contain++1. **Reach** — the canonical product-search / product-page URL pattern for an MPN.+2. **Gate** — login / region / cookie wall, and how the persistent pup profile+   gets past it (which profile, what creds key in `chip-fetcher creds`).+3. **Download flow** — the exact button/tab sequence to the CAD bundle, with the+   selectors or visual cues that identify each step.+4. **Catch** — what the downloaded artifact is (zip? IntLib? per-file?), where it+   lands, and how chip-fetcher pulls it off the desktop.+5. **When it breaks** — the failure signatures (block page, captcha, moved button)+   and the recovery playbook. This is the highest-value section — it's why the+   pack exists.++See `sites/snapeda/SKILL.md` for the template filled in.++## Adding a site++Found a site chip-fetcher doesn't know, or a new way past a block? Write a skill+for it and contribute it — `CONTRIBUTING.md` covers the two paths (PR it into the+pack, or own it in your own wiki repo and link it in). Either way your AI, and+everyone else's, gets smarter the next time that site comes up.+--- a/skills/CONTRIBUTING.md+++ b/skills/CONTRIBUTING.md@@ -1,68 +1,69 @@-# Contributing a source-site skill--You figured out how to navigate a vendor's CAD-download flow — maybe a site-chip-fetcher didn't cover, maybe a new way past a block (the day DigiKey blocked-pup, someone chatted with its assistant and found a path; that knowledge belongs-here). Here's how to get it into the pack so everyone's AI benefits.--## Write the skill--Copy `sites/snapeda/SKILL.md` as a template and fill in the five sections (Reach,-Gate, Download flow, Catch, When it breaks). Keep it to **one site per skill** and-give it real trigger words (the vendor name, "blocked", "captcha", the file types)-so the AI auto-surfaces it at the right moment.--## Two ways to land it — the owner picks per contribution--The pack supports two contribution shapes. Which one is allowed for a given skill-is the **maintainer's call**, made deliberately, trading freshness against trust:--### A. Pull request INTO the pack (vetted — the default)--Open a PR adding `sites/<vendor>/SKILL.md` to this repo. The maintainer reads the-navigation steps, sanity-checks them, and merges. The skill now lives in the-chip-fetcher repo and ships with the pack.--- **Pro:** every step is reviewed before it reaches anyone's AI — the safe default.-- **Con:** updates require another PR; the maintainer is in the loop each time.-- **Use when:** the contributor is new/unknown, or the skill does anything-  sensitive (credential handling, evading a block, executing fetched content).--### B. Linked external skill (trusted — opt-in)--Publish your skill as its **own wiki repo** (you own it, you `adompkg publish`-updates whenever you like). Then PR a one-line **link** into this pack's manifest-instead of the skill body. The pack references your repo; your repo stays yours.--- **Pro:** you keep ownership and can fix your site's flow the hour it changes,-  no maintainer round-trip — exactly what a fast-moving vendor site needs.-- **Con:** the pack now trusts a repo it doesn't control; a later edit isn't-  re-reviewed. So this is **trusted-contributor only**.-- **Use when:** the maintainer knows the contributor and is comfortable letting-  their repo update live.--> The link itself still arrives by PR, so the maintainer always makes the-> conscious decision to trust a given external repo — but once linked, that repo-> self-updates. Default to (A); grant (B) to people you trust. Revoking is just-> dropping the link.--## Security & vetting--Site skills tell an AI to drive a real browser on the user's machine, sometimes-past anti-bot defenses. Treat every contribution as code review:--- No skill should exfiltrate credentials or paste them anywhere but the vendor's-  own login. Creds come from `chip-fetcher creds`, never inline.-- "Getting past a block" means *navigating the site as a human would* (right-  profile, human pacing, the path their own assistant suggested) — **not**-  defeating security controls or solving CAPTCHAs programmatically.-- A linked external skill (path B) inherits the trust you grant its repo. When in-  doubt, require path A.--## Status (for Colby / the wiki)--Path A (PR into the pack) works on the wiki today — it's a normal pull request.-Path B (a pack sub-skill that *links* an externally-owned wiki repo, which then-self-updates) is the piece that needs platform support: a manifest link type the-pack resolves at install time, plus a way for the maintainer to mark a given link-trusted. Tracked in the chip-fetcher Colby feedback.+# Contributing a source-site skill++You figured out how to navigate a vendor's CAD-download flow — maybe a site+chip-fetcher didn't cover, maybe a new way past a block (the day DigiKey blocked+pup, someone chatted with its assistant and found a path; that knowledge belongs+here). Here's how to get it into the pack so everyone's AI benefits.++## Write the skill++Copy `sites/snapeda/SKILL.md` as a template and fill in the five sections (Reach,+Gate, Download flow, Catch, When it breaks). Keep it to **one site per skill** and+give it real trigger words (the vendor name, "blocked", "captcha", the file types)+so the AI auto-surfaces it at the right moment.++## Two ways to land it — the owner picks per contribution++The pack supports two contribution shapes. Which one is allowed for a given skill+is the **maintainer's call**, made deliberately, trading freshness against trust:++### A. Pull request INTO the pack (vetted — the default)++Open a PR adding `sites/<vendor>/SKILL.md` to this repo. The maintainer reads the+navigation steps, sanity-checks them, and merges. The skill now lives in the+chip-fetcher repo and ships with the pack.++- **Pro:** every step is reviewed before it reaches anyone's AI — the safe default.+- **Con:** updates require another PR; the maintainer is in the loop each time.+- **Use when:** the contributor is new/unknown, or the skill does anything+  sensitive (credential handling, evading a block, executing fetched content).++### B. Linked external skill (trusted — opt-in)++Publish your skill as its **own wiki repo** (you own it, you `adom-wiki pkg publish`+updates whenever you like). Then PR a one-line **link** into this pack's manifest+instead of the skill body. The pack references your repo; your repo stays yours.++- **Pro:** you keep ownership and can fix your site's flow the hour it changes,+  no maintainer round-trip — exactly what a fast-moving vendor site needs.+- **Con:** the pack now trusts a repo it doesn't control; a later edit isn't+  re-reviewed. So this is **trusted-contributor only**.+- **Use when:** the maintainer knows the contributor and is comfortable letting+  their repo update live.++> The link itself still arrives by PR, so the maintainer always makes the+> conscious decision to trust a given external repo — but once linked, that repo+> self-updates. Default to (A); grant (B) to people you trust. Revoking is just+> dropping the link.++## Security & vetting++Site skills tell an AI to drive a real browser on the user's machine, sometimes+past anti-bot defenses. Treat every contribution as code review:++- No skill should exfiltrate credentials or paste them anywhere but the vendor's+  own login. Creds come from `chip-fetcher creds`, never inline.+- "Getting past a block" means *navigating the site as a human would* (right+  profile, human pacing, the path their own assistant suggested) — **not**+  defeating security controls or solving CAPTCHAs programmatically.+- A linked external skill (path B) inherits the trust you grant its repo. When in+  doubt, require path A.++## Status (for Colby / the wiki)++Path A (PR into the pack) works on the wiki today — it's a normal pull request.+Path B (a pack sub-skill that *links* an externally-owned wiki repo, which then+self-updates) is the piece that needs platform support: a manifest link type the+pack resolves at install time, plus a way for the maintainer to mark a given link+trusted. Tracked in the chip-fetcher Colby feedback.+

Comments

No comments yet.

Log in to comment.