← Search

Datasheet Extraction
Engineering
⚙ Needs: an AI agent with file tools (Read, Write, Bash)…

Datasheet Extraction

Pull structured specs out of component datasheet PDFs and cache them for schematic, EMC and SPICE analysis.

At a glance
What
Pull structured specs out of component datasheet PDFs and cache them for schematic, EMC and SPICE analysis.
Cost
Free
Needs
an AI agent with file tools (Read, Write, Bash), such as Claude Code or Codex; Python 3 for the helper scripts; component datasheet PDFs in a project folder (downloaded with a distributor skill). No API key is needed by this skill itself.
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

Quick answer

Datasheet Extraction is a free Muse skill that takes datasheet PDFs and pulls out specifications: pinouts, electrical characteristics, peripherals, topology and features, then caches them so schematic, EMC and SPICE analysis can look up component knowledge. It is a producer of facts, not a reviewer. It needs PDFs supplied, pairs with a distributor, and scanned PDFs need a human check.

⌁

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; component datasheet PDFs in a project folder (downloaded with a distributor skill). No API key is needed by this skill itself. Install "Datasheet Extraction" for me. A skill that extracts structured specifications from component datasheet PDFs, pinouts, electrical characteristics, peripherals and features, and caches them per project for schematic, EMC and SPICE analysis. Repository: https://github.com/aklofas/kicad-happy/tree/main/skills/datasheets 1. Fetch the SKILL.md file (plus its references/, schemas/, prompts/ and scripts/ folders) 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 "datasheets". 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. point it at a project datasheets folder). 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.