Review KiCad schematics, PCB layouts, Gerbers, and BOMs with kicad-happy
Turn a coding agent into a KiCad electronics review assistant that parses boards, checks circuits, audits EMC risks, and prepares prototype-to-production feedback.
npx skills add agentskillexchange/skills --skill review-kicad-schematics-pcb-layouts-gerbers-and-boms-with-kicad-happy
/plugin marketplace add aklofas/kicad-happy and /plugin install kicad-happy@kicad-happy; in Codex use $skill-installer for https://github.com/aklofas/kicad-happy or clone the repo and symlink the listed skills into ~/.codex/skills.Use kicad-happy when an agent needs to review a KiCad hardware project before fabrication or production handoff. The agent can analyze schematics, PCB layouts, Gerbers, passive networks, power trees, EMC exposure, datasheets, BOM completeness, sourcing options, and board-house readiness. Invoke this instead of manually using KiCad or scattered scripts when the job is a repeatable agent review of an electronics design directory, especially before ordering boards or asking for a second-pass design review. The boundary is hardware design inspection and fabrication-prep workflow for KiCad projects; it is not a generic EDA tool listing, a broad Python library, or a normal KiCad usage card.
What this skill actually does
Inputs and prerequisites: Python 3.10+, KiCad project files, Claude Code, Codex, GitHub Copilot CLI, Google Antigravity, opencode, or GitHub Actions.
Setup notes: Install through the documented agent path: in Claude Code add the marketplace with /plugin marketplace add aklofas/kicad-happy and /plugin install kicad-happy@kicad-happy ; in Codex use $skill-installer for https://github.com/aklofas/kicad-happy or clone the repo and symlink the listed skills into ~/.codex/skills .
Source and verification boundary: use https://github.com/aklofas/kicad-happy as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.