skills/mouser/SKILL.md
Search Mouser Electronics for electronic components — secondary source for prototype orders. Find parts, check pricing/stock, download datasheets, analyze specifications. Use with KiCad for BOM creation and part selection. Use this skill when the user specifically mentions Mouser, when DigiKey is out of stock or has worse pricing, when comparing prices across distributors, or when searching for parts that DigiKey doesn't carry. For package cross-reference tables and BOM workflow, see the `bom` skill.
npx skillsauth add aklofas/kicad-happy mouserInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
| Skill | Purpose |
|-------|---------|
| kicad | Schematic analysis — extracts MPNs for part lookup |
| bom | BOM management — orchestrates sourcing across distributors |
| digikey | Primary prototype source (prefer for datasheets — direct PDF links) |
| spice | Uses Mouser parametric data for behavioral SPICE models |
Mouser is the secondary source for prototype orders — use when DigiKey is out of stock or has worse pricing. For production orders, see lcsc/jlcpcb. For BOM management and export workflows, see bom. For datasheets, prefer DigiKey's API (direct PDF links) — Mouser blocks automated PDF downloads.
Mouser uses simple API key authentication — no OAuth, no tokens, no callback URLs. The Search API key is a UUID passed as a query parameter.
Set the environment variable before running the scripts:
export MOUSER_SEARCH_API_KEY=your-search-api-key-uuid
If credentials are stored in a central secrets file (e.g., ~/.config/secrets.env), load them first:
export $(grep -v '^#' ~/.config/secrets.env | grep -v '^$' | xargs)
All search endpoints use the Search API key as a query parameter: ?apiKey=<key>. Content-Type is application/json for all POST requests.
POST /api/v1/search/keyword?apiKey=<key>
{
"SearchByKeywordRequest": {
"keyword": "100nF 0402 ceramic capacitor",
"records": 50,
"startingRecord": 0,
"searchOptions": "InStock"
}
}
searchOptions: "None" | "Rohs" | "InStock" | "RohsAndInStock"records: max 50 per requeststartingRecord: offset for paginationPOST /api/v1/search/partnumber?apiKey=<key>
{
"SearchByPartRequest": {
"mouserPartNumber": "GRM155R71C104KA88D|RC0402FR-0710KL",
"partSearchOptions": "Exact"
}
}
|)partSearchOptions: "Exact" | "BeginsWith" | "Contains"V2 adds manufacturer filtering and pagination by page number.
POST /api/v2/search/keywordandmanufacturer?apiKey=<key>
{
"SearchByKeywordMfrNameRequest": {
"keyword": "LMR51450",
"manufacturerName": "Texas Instruments",
"records": 25,
"pageNumber": 1,
"searchOptions": "InStock"
}
}
Note: the wrapper object name is SearchByKeywordMfrNameRequest (not SearchByKeywordMfrRequest — the V1 name is deprecated).
POST /api/v2/search/partnumberandmanufacturer?apiKey=<key>
GET /api/v2/search/manufacturerlist?apiKey=<key>
Returns the full list of manufacturer names for use in filtered searches.
These still work but V2 equivalents are preferred:
POST /api/v1/search/keywordandmanufacturer → use V2POST /api/v1/search/partnumberandmanufacturer → use V2GET /api/v1/search/manufacturerlist → use V2All search endpoints return the same response format:
{
"Errors": [],
"SearchResults": {
"NumberOfResult": 142,
"Parts": [...]
}
}
| Field | Type | Description |
|-------|------|-------------|
| MouserPartNumber | string | Mouser's internal part number (prefixed, e.g., 81-GRM155R71C104KA88) |
| ManufacturerPartNumber | string | Manufacturer's part number (MPN) — use for cross-distributor matching |
| Manufacturer | string | Manufacturer name |
| Description | string | Product description |
| Category | string | Product category |
| DataSheetUrl | string | URL to datasheet PDF (Mouser-hosted — see Datasheet section) |
| ProductDetailUrl | string | URL to Mouser product page |
| ImagePath | string | Product image URL |
| Availability | string | Human-readable stock text (e.g., "2648712 In Stock") |
| AvailabilityInStock | string | Numeric stock quantity (as string) |
| AvailabilityOnOrder | array | Incoming stock: [{Quantity, Date}] |
| LeadTime | string | Factory lead time (e.g., "84 Days") |
| LifecycleStatus | string|null | "New Product", "End of Life", etc. |
| IsDiscontinued | string | "true" or "false" (string, not boolean) |
| SuggestedReplacement | string | Replacement MPN if discontinued |
| Min | string | Minimum order quantity (as string) |
| Mult | string | Order multiple (as string) |
| Reeling | bool | Tape-and-reel packaging available |
| ROHSStatus | string | RoHS compliance status |
| PriceBreaks | array | Tiered pricing: [{Quantity, Price, Currency}] |
| ProductAttributes | array | Parametric specs: [{AttributeName, AttributeValue}] |
| AlternatePackagings | array|null | Alternate packaging MPNs: [{APMfrPN}] |
| SurchargeMessages | array | Tariff/surcharge info: [{code, message}] |
| ProductCompliance | array | HTS codes, ECCN: [{ComplianceName, ComplianceValue}] |
| UnitWeightKg | object | {UnitWeight: <float>} in kg |
"$0.10", not a float. Parse it before comparing.AvailabilityInStock returns "2648712" not 2648712."true" or "false", not boolean.81-GRM155R71C104KA88 — the prefix is Mouser-specific. Use ManufacturerPartNumber for cross-referencing.SearchByKeywordMfrNameRequest, not SearchByKeywordMfrRequest.SurchargeMessages may contain US tariff percentages — useful for cost estimation.AvailabilityOnOrder shows incoming stock quantities and expected dates.Mouser's DataSheetUrl field points to Mouser-hosted URLs (mouser.com/datasheet/...). These URLs block automated downloads — they return an HTML "Access denied" page when fetched with Python/curl/wget, even with browser User-Agent headers. The download scripts handle this with a multi-strategy approach:
Note: Mouser's product pages return 403 for most automated requests, so strategy 2 has limited success. DigiKey and LCSC are more reliable datasheet sources.
Use sync_datasheets_mouser.py to maintain a datasheets/ directory alongside a KiCad project. Same workflow and index.json format as the DigiKey skill.
# Sync datasheets for a KiCad project
python3 <skill-path>/scripts/sync_datasheets_mouser.py <file.kicad_sch>
# Preview what would be downloaded
python3 <skill-path>/scripts/sync_datasheets_mouser.py <file.kicad_sch> --dry-run
# Retry previously failed downloads
python3 <skill-path>/scripts/sync_datasheets_mouser.py <file.kicad_sch> --force
# Custom output directory
python3 <skill-path>/scripts/sync_datasheets_mouser.py <file.kicad_sch> -o ./my-datasheets
# Parallel downloads (3 workers)
python3 <skill-path>/scripts/sync_datasheets_mouser.py <file.kicad_sch> --parallel 3
Use fetch_datasheet_mouser.py for one-off downloads.
# Search by MPN (uses Mouser API)
python3 <skill-path>/scripts/fetch_datasheet_mouser.py --search "TPS61023DRLR" -o datasheet.pdf
# Direct URL download
python3 <skill-path>/scripts/fetch_datasheet_mouser.py "https://example.com/datasheet.pdf" -o datasheet.pdf
# JSON output
python3 <skill-path>/scripts/fetch_datasheet_mouser.py --search "ADP1706" --json
The scripts try multiple sources in order:
DataSheetUrl from the API responseplaywright is installed, uses headless Chromium as a last resortWhen all methods fail, provide the ProductDetailUrl to the user so they can download from the Mouser product page in their browser.
If no API key is available, search Mouser by fetching product pages directly:
https://www.mouser.com/c/?q=<query>Include key parameters in the query:
Min and Mult fields matter — some parts have minimum order qty or must be ordered in multiplesSurchargeMessages may include US tariff percentages — factor into cost estimatesAvailabilityOnOrder shows incoming stock with expected datesIsDiscontinued and LifecycleStatus before selecting partsdocumentation
Generate professional engineering documentation from KiCad projects — Hardware Design Descriptions (HDD), CE Technical Files, Interface Control Documents (ICD), Design Review Packages, and Manufacturing Transfer Packages. Auto-runs schematic, PCB, EMC, and thermal analyses; renders schematic and PCB SVGs with subsystem cropping, focus dimming, net highlighting, and pin-net annotation; generates power tree, bus topology, and architecture block diagrams. Produces styled PDF with cover pages, TOC, and vector SVG embedding. Markdown source of truth — human-editable, version-controllable. Use for "generate documentation", "create report", "HDD", "CE technical file", "design review package", "ICD", "render schematic", "render layout", "generate block diagram", "manufacturing package", "generate PDF", or "custom report".
development
EMC pre-compliance risk analysis for KiCad PCB designs — 17 check categories, 42 rule IDs covering ground planes, decoupling, I/O filtering, switching harmonics, clock routing, differential pair skew, board edge radiation, PDN impedance, return paths, crosstalk, ESD protection, and shielding. Produces severity-ranked risk report with pre-compliance test plan. Supports FCC Part 15, CISPR 32, CISPR 25 (automotive), MIL-STD-461G. SPICE-enhanced when available. Use when the user asks about EMC, EMI, radiated/conducted emissions, FCC compliance, CE marking, CISPR, ground plane issues, decoupling strategy, clock routing EMC, switching noise, differential pair skew, or whether their board will pass EMC testing. Also for "will this pass FCC?", "check my EMC", "is my ground plane okay?", "check my decoupling", or "generate an EMC test plan".
testing
Run automatic SPICE simulations on subcircuits detected from KiCad schematic analysis — validates filter frequencies, divider ratios, opamp gains, LC resonance, and crystal load capacitance. Supports ngspice, LTspice, and Xyce (auto-detected). Generates testbenches, runs batch mode, produces structured pass/warn/fail report. Use when the user asks to simulate, verify, or validate any analog subcircuit — RC filters, LC filters, voltage dividers, opamp circuits, crystal oscillators. Also for "simulate my circuit", "run spice", "verify with simulation", "check my filter cutoff", "does this divider give the right voltage", "what's the bandwidth of this opamp stage". Consider suggesting simulation during design reviews when the schematic analyzer reports simulatable subcircuits and a SPICE simulator is available.
development
Analyze KiCad projects and PDF schematics: schematics, PCB layouts, Gerbers, footprints, symbols, netlists, and design rules. Reviews designs for bugs, traces nets, cross-references schematic to PCB, extracts BOM data, checks DRC/ERC, DFM, power trees, and regulator circuits. Analyzes PDF schematics from dev boards, reference designs, eval kits, and datasheets. Supports KiCad 5–10. Use whenever the user mentions .kicad_sch, .kicad_pcb, .kicad_pro, PCB design review, schematic analysis, PDF schematics, reference designs, Gerber files, DRC/ERC, netlist issues, BOM extraction, signal tracing, power budget, DFM, or wants to understand, debug, compare, or review any hardware design. Also for "check my board", "review before fab", "what's wrong with my schematic", "is this ready to order", "check my power supply", "verify this circuit", or any electronics/PCB design question.