---
name: electronics-site-SITE
description: >-
  (Template) <Site name> (<domain>): how the site treats AI clients on each access lane (WebFetch,
  curl, pup, nb, API), the bot defense it runs, the exact failure signatures, and the task recipes.
  Copy this folder to skills/<site>/, fill every section with what you SAW, and date it.
  Trigger words: <domain>, <site> blocked, <site> datasheet, <site> product page, <site> timeout.
---

Parent skill: **electronics-sites-skillpack**

# <Site name>

**Domains:** <www.example.com, cdn.example.com>
**What it is:** <manufacturer / distributor / CAD library / aggregator; what people fetch from it>
**Bot defense:** <Akamai / Cloudflare / PerimeterX / none observed; how it presents>

## Lane matrix

| Lane | Result | What we saw (<date>) |
|---|---|---|
| WebFetch | OK / BLOCKED / PARTIAL / untested | <status code, title, timing> |
| curl | ... | <curl -sS -o /dev/null -w 'http=%{http_code} server=%header{server} cf=%header{cf-ray}'> |
| pup | ... | <title + first 100 chars of body after a 6 s settle> |
| nb | ... | <same, after a 9 s settle> |

**Use first:** `<cheapest lane that works>`.

## Failure signatures

- <exact title / body text / status / header that identifies the wall>

## Recipes

### <Task, e.g. datasheet PDF>

<URL pattern, DOM ids, the verb sequence, the wait you needed>

## API / Adom backend lane

<official API, or the adom-* backend that already wraps it; quota notes>

## Gotchas

- <the thing that cost you an hour>

## Evidence and last verified

<how you verified, date, issue links>