← Search

element14 Parts Search
Engineering
⚙ Needs: an AI agent with file tools (Read, Write, Bash)…

element14 Parts Search

Search Newark, Farnell and element14 through one API for parts, pricing, stock and datasheets.

At a glance
What
Search Newark, Farnell and element14 through one API for parts, pricing, stock and datasheets.
Cost
Free
Needs
an AI agent with file tools (Read, Write, Bash), such as Claude Code or Codex; Python 3 for the helper scripts; a free element14 API key from a developer account, stored as an environment variable, with simple query-parameter authentication and no OAuth.
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

Quick answer

element14 Parts Search is a free Muse skill that covers Newark, Farnell and element14 through API with catalog, pricing and stock varying by region. It finds parts by number, checks pricing and stock, downloads datasheets and syncs a directory. Its key needs a developer account, lives in an environment variable, never in a chat, and prices need comparing before ordering.

⌁

Install

Copy the install package below, then paste it into Muse

Prerequisites: an AI agent with file tools (Read, Write, Bash), such as Claude Code or Codex; Python 3 for the helper scripts; a free element14 API key from a developer account, stored as an environment variable, with simple query-parameter authentication and no OAuth. Install "element14 Parts Search" for me. A skill that searches Newark, Farnell and element14 through one API, finds parts by manufacturer or distributor part number, checks pricing and stock, downloads datasheets, and syncs a local datasheets directory for a KiCad project. Repository: https://github.com/aklofas/kicad-happy/tree/main/skills/element14 1. Fetch the SKILL.md file (plus its scripts/ folder) from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). It must never contain hardcoded secrets. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "element14". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. save my element14 API key as an environment variable). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it is in the prerequisites above. Rules: do not touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.

🔒 Security, provenance and what this touches
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.