← Search

EMC Pre-Compliance Analysis
Engineering
⚙ Needs: an AI agent with file tools (Read, Write, Bash)…

EMC Pre-Compliance Analysis

Catch common EMC failures before fabrication with 18 check categories and a severity-ranked risk report.

At a glance
What
Catch common EMC failures before fabrication with 18 check categories and a severity-ranked risk report.
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 KiCad PCB design to analyze. A SPICE simulator (ngspice, LTspice or Xyce) is optional, for SPICE-enhanced checks only.
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

Quick answer

EMC Pre-Compliance Analysis is a free Muse skill that runs EMC risk analysis on a KiCad PCB design using rule checks, formulas and SPICE, across 18 check categories and 44 identifiers covering ground planes, decoupling and shielding. It produces a risk report with a test plan. It catches roughly 70 percent of mistakes; only a calibrated lab measurement guarantees compliance.

⌁

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 KiCad PCB design to analyze. A SPICE simulator (ngspice, LTspice or Xyce) is optional, for SPICE-enhanced checks only. Install "EMC Pre-Compliance Analysis" for me. A skill that runs EMC pre-compliance risk analysis on KiCad PCB designs, 18 check categories and 44 rule identifiers, producing a severity-ranked risk report with a pre-compliance test plan. Repository: https://github.com/aklofas/kicad-happy/tree/main/skills/emc 1. Fetch the SKILL.md file (plus its references/ 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 "emc". 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 KiCad PCB design). 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. This skill analyzes risk, it does not certify compliance.

🔒 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.