← ClaudeAtlas

digikeylisted

Search DigiKey for electronic components and download datasheets — primary source for prototype orders and the preferred API-based method for fetching datasheets. Find parts by keyword or part number, check pricing/stock, download datasheets directly via API, analyze specifications. Sync and maintain a local datasheets directory for a KiCad project — extract components from schematics, download all missing datasheets, keep them up to date. Use with KiCad for BOM creation and part selection. Use this skill when the user asks about electronic components, part specifications, datasheets, footprints, pricing, stock availability, or needs to download/read a datasheet — even if they don't mention "DigiKey" by name. Also use when the user says "sync datasheets", "download datasheets for my board/project", or mentions a datasheets directory. DigiKey is the default distributor for prototyping and the preferred datasheet source because its API returns direct PDF links without web scraping. For package cross-reference t
Guru254-pixel/kicad-happy · ★ 2 · Data & Documents · score 75
Install: claude install-skill Guru254-pixel/kicad-happy
# DigiKey Parts Search & Analysis DigiKey is the **primary source for prototype orders** (Mouser is secondary). Its API returns direct PDF datasheet links, making it the preferred datasheet source. For production orders, see `lcsc`/`jlcpcb`. For BOM management and export workflows, see `bom`. ## API Credential Setup The DigiKey API requires OAuth 2.0 credentials. Here's how to set them up: 1. **Create a DigiKey account** at [digikey.com](https://www.digikey.com) if you don't have one 2. **Register an API app** at [developer.digikey.com](https://developer.digikey.com): - Sign in with your DigiKey account - Go to "My Apps" → "Create App" - App name: anything (e.g., "claude-code") - Select **"Product Information v4"** API - OAuth type: **Client Credentials** (2-legged, no user login needed) - Callback URL: `https://localhost` (not used for client credentials, but required) - After creation, note the **Client ID** and **Client Secret** 3. **Set the environment variables** before running the scripts: ```bash export DIGIKEY_CLIENT_ID=your_client_id_here export DIGIKEY_CLIENT_SECRET=your_client_secret_here ``` If credentials are stored in a central secrets file (e.g., `~/.config/secrets.env`), load them first: ```bash export $(grep -v '^#' ~/.config/secrets.env | grep -v '^$' | xargs) ``` The client credentials flow has no user interaction — once configured, API calls work automatically. ## DigiKey Product Information API v4 The AP