Agent skill

Kicad Library

by mixelpixx in mixelpixx/Konnect

Library management workflow for KiCAD — creating symbols, footprints, and managing libraries via MCP tools.

AGPL-3.0Auto-check passedAgent Workflows

Install Kicad Library

skills CLI
$ npx skills add mixelpixx/Konnect --skill kicad-library -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mixelpixx/Konnect kicad-library --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mixelpixx/Konnect.git skills-src && mkdir -p .claude/skills && cp -r skills-src/crates/konnect/assets/skills/kicad-library .claude/skills/kicad-library && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
kicad-library
GitHub stars
917
Token cost
~5.1k tokens
SKILL.md length
2,180 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Library management workflow for KiCAD — creating symbols, footprints, and managing libraries via MCP tools.

  • Works in 7 steps: search_symbols / list_symbols_in_library… → Confirm the exact manufacturer part… → Note the drawing view of every datasheet… → …
  • : create a symbol
  • SKILL.md covers Toolset Loading, Refresh Placed Footprints, Search First Principle and Symbol Creation, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Kicad Library is an agent skill from mixelpixx/Konnect. Library management workflow for KiCAD — creating symbols, footprints, and managing libraries via MCP tools. Triggers on: "create a symbol", "make a footprint", "custom component", "register library", "find a part", "pin numbering", "new symbol", "new footprint", "add to library", "library path", "pad layout".

Its SKILL.md is about 5.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering MCP servers. It works with Model Context Protocol. The repository describes itself as: AI-assisted PCB design for KiCAD 10. Native KiCAD plugin — a single Rust binary exposing 217 schematic, layout, routing, placement, design-review, and manufacturing tools to…. The licence is AGPL-3.0.

When your agent uses it

  • : create a symbol
  • Make a footprint
  • Custom component
  • Register library

Example prompts

  • “create a symbol”
  • “make a footprint”
  • “custom component”
  • “/kicad-library”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. search_symbols / list_symbols_in_library first — prefer an existing
  2. Confirm the exact manufacturer part number and package suffix.
  3. Note the drawing view of every datasheet figure (top, bottom, component,
  4. Walk the physical leads from the documented key, in the documented
  5. Reconcile three counts: datasheet leads, symbol pins, footprint pads.
  6. Read the result back with get_symbol_info and get_footprint_info
  7. Refuse to use the part in a real schematic while any mirror,

What it can do on your machine

Read from SKILL.md and the folder at commit 9488e5f. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Kicad Library loads about 5.1k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 2,180 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~81
When it runs · the whole SKILL.md, loaded when a task matches
~5.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mixelpixx/Konnect at commit 9488e5f, republished under its AGPL-3.0 licence (© mixelpixx). 2,180 words, ~5,109 tokens.

Download SKILL.mdSave it as .claude/skills/kicad-library/SKILL.md (or your agent's skills folder).
name
kicad-library
description
Library management workflow for KiCAD — creating symbols, footprints, and managing libraries via MCP tools. Triggers on: "create a symbol", "make a footprint", "custom component", "register library", "find a part", "pin numbering", "new symbol", "new footprint", "add to library", "library path", "pad layout".
argument-hint
[component or library task]

KiCAD Library Management Workflow

This skill guides Claude through creating and managing KiCAD symbols, footprints, and libraries using Konnect MCP tools. ALL modifications go through MCP tools — never edit .kicad_sym or .kicad_mod files directly.


Toolset Loading

load_toolset('library')    # search_symbols, search_footprints, create_symbol, create_footprint,
                           # edit_footprint_pad, set_footprint_graphics, set_footprint_metadata,
                           # set_footprint_models, get_footprint_info, register_symbol_library,
                           # register_footprint_library, get_symbol_info
load_toolset('pcb_components') # update_footprints_from_library for placed instances

Always call get_active_toolsets() first to see what is already loaded.


Refresh Placed Footprints

Editing a .kicad_mod library file does not change copies already embedded on a board. After a library edit, call update_footprints_from_library; it is Konnect's MCP equivalent of KiCad Tools → Update Footprints from Library.

This operation is not update_pcb_from_schematic. Schematic sync updates schematic-owned fields while preserving artwork. Library refresh replaces supported library-owned pads, graphics, attributes, metadata, and 3D models while preserving the placed footprint's reference, value, position, rotation, board side, locked state, KIID, symbol metadata, instance overrides, and pad nets by logical pad number.

Always dry-run first:

text
update_footprints_from_library(
  board,
  references?,
  library_ids?,
  dry_run,
  expected_plan_revision?
)
  • Use dry_run=true and review status, coverage, changes, and diagnostics.
  • Apply with dry_run=false and the exact returned expected_plan_revision.
  • Keep the requested board open in live KiCad; there is no closed-board file fallback.
  • One successful apply is one KiCad undo entry.
  • A stale plan, unresolved library, removed connected pad, or unsupported library content returns a non-mutating conflict for the whole selection.

Search First Principle

Always search existing libraries before creating custom components.

search_symbols(query)       # Search all symbol libraries
search_footprints(query)    # Search all footprint libraries

KiCAD ships with extensive libraries. Common parts almost always exist:

  • Standard passives (R, C, L) → Device library
  • Connectors → Connector_Generic, Connector_USB, Connector_HDMI, etc.
  • Common ICs (STM32, ATmega, LM7805, NE555) → manufacturer-specific libraries
  • Transistors/MOSFETs → Transistor_FET, Transistor_BJT

Only create a custom symbol/footprint when:

  • The part does not exist in any library
  • The existing symbol has wrong pin count/arrangement
  • You need a proprietary/unusual package

Symbol Creation

Pin Numbering — the datasheet decides, not a convention

There is no safe universal pin-numbering rule for a real part. Physical lead numbers are defined by the exact manufacturer part number and package suffix. BJT and MOSFET lead order varies between manufacturers, packages and variants; bottom-view, mirrored, socketed and connector drawings reverse it. A symbol can be syntactically valid and still be electrically wrong when its pins and the footprint's pads describe different physical leads.

Even KiCad's own generic symbols do not follow one order — Device:LED is pin 1 = K (cathode), pin 2 = A (anode), the opposite of the "pin 1 = anode" rule people expect. Check, do not assume.

Before creating or wiring a package-sensitive part:

  1. search_symbols / list_symbols_in_library first — prefer an existing library symbol over authoring a new one.
  2. Confirm the exact manufacturer part number and package suffix.
  3. Note the drawing view of every datasheet figure (top, bottom, component, solder, mating). An unstated view is the most common source of mirrored parts.
  4. Walk the physical leads from the documented key, in the documented direction.
  5. Reconcile three counts: datasheet leads, symbol pins, footprint pads. Document any intentional duplicate or mechanical-only pad.
  6. Read the result back with get_symbol_info and get_footprint_info rather than trusting what you just wrote.
  7. Refuse to use the part in a real schematic while any mirror, reversal, duplicate, missing lead or view ambiguity is unresolved.
Physical pin-map acceptance contract

For every custom or package-sensitive part, complete this record before the symbol and footprint are accepted. "Looks sequential" and a matching pin count are not evidence.

Record the manufacturer, exact MPN and package suffix, datasheet document number/revision, source URL, relevant page numbers, symbol library ID, and footprint library ID. Then add one row for every physical lead:

Datasheet leadFunctionSymbol pin / name / typeFootprint padX/Y (mm)Drawing view / directionEvidence
1Example only1 / NAME / passive10.00 / 0.00bottom view, clockwise from keydatasheet p. N, figure M

Apply these rules to the table:

  • Walk from the datasheet's documented key, notch, dot, flat, bevel, or other datum in the stated direction. State top, bottom, component, solder, pin, or mating view in every row; never silently translate between views.
  • Give repeated physical leads separate rows even when they share one electrical function. List exposed pads, shields, mounting tabs, and mechanical holes separately and state whether each is an electrical pad, a duplicated connection, or intentionally absent from the symbol.
  • Reconcile and record the datasheet physical-lead count, symbol electrical-pin count, footprint electrical-pad count, duplicate-pad count, and mechanical-only feature count. Explain every difference.
  • Treat a symbol pin number and footprint pad number as the same physical lead only when the evidence row proves it. Names such as A/K, G/D/S, B/C/E, COM, or VCC do not establish the physical number.

Acceptance procedure:

  1. Create or select the exact symbol and footprint only after completing the source columns above.
  2. Query the symbol back with get_symbol_info and the footprint with get_footprint_info(include_pads=true). The returned pad coordinates and rotations are footprint-local. Compare every returned pin/pad number, name, type, coordinate, drill, size, and layer set to the table and datasheet.
  3. Place a disposable symbol and footprint in a scratch project. Render the schematic and board, then inspect the pin-1/key marker, numbering direction, top/bottom orientation, pad geometry, drill/slot geometry, courtyard, fab, and silkscreen. For mating parts, inspect the mating view as well.
  4. Read the disposable instances back; do not accept only the values requested during creation as proof they were written.
  5. Refuse acceptance and keep the part out of a real schematic or PCB if any lead is missing, duplicated without explanation, mirrored, reversed, assigned to a different function, or ambiguous in view/direction. Record an unavailable datasheet figure, query, or render as BLOCKED, never as pass.

The rows below are starting hypotheses for generic parts only. Verify each against the actual symbol with get_symbol_info before relying on it.

Component TypeTypical (verify before use)
Passives (R, C, L)Pin 1 and Pin 2, interchangeable when unpolarised
Polarised capsPin 1 = +, pin 2 = −, but confirm on the symbol
ConnectorsSequential from 1
CrystalPin 1, Pin 2 (+ case ground if 4-pin)
ICs, diodes, BJTs, MOSFETsNo default — datasheet + symbol only
Pin Types
TypeUse For
inputLogic/analog inputs, gate inputs
outputLogic/analog outputs, push-pull drivers
bidirectionalData bus lines, I2C SDA, GPIO
tri_stateOutputs with high-impedance state
passiveResistor/capacitor/inductor pins, crystal pins
power_inVCC, VDD, GND pins (power consumer)
power_outRegulator output, power source pins
open_collectorOpen-drain/open-collector outputs
open_emitterOpen-emitter outputs
unspecifiedPins with no clear electrical type
no_connectPins that must not be connected
Required Symbol Properties

Every symbol must have these fields:

PropertyDescriptionExample
ReferenceDesignator prefixU, R, C, J, D, Q, L
ValuePart name or valueSTM32F103C8, 10k, 100nF
FootprintDefault footprint assignmentPackage_SO:SOIC-8_3.9x4.9mm
DatasheetURL to datasheethttps://...

Optional but recommended:

  • LCSC — LCSC/JLCPCB part number for assembly
  • MPN — Manufacturer part number
  • Description — Short text description
Symbol Layout Guidelines
  • Pin 1 indicator (dot or bar) on the symbol body
  • Inputs on the left side, outputs on the right side
  • Power pins on top (VCC) and bottom (GND)
  • Pin spacing: 2.54mm (100mil) standard grid
  • Symbol body: rectangle for ICs, standard shapes for passives/discretes

Footprint Creation

Pad Types
TypeUse For
smdSurface-mount pads (no drill hole)
thru_holeThrough-hole pads (plated drill)
np_thru_holeNon-plated through hole (mounting holes, slots)
Pad Side and Shape Details

create_footprint defaults SMD pads to the front-side layer set ["F.Cu", "F.Paste", "F.Mask"]. For bottom-side SMD pads, set layers=["B.Cu", "B.Paste", "B.Mask"] explicitly. Through-hole pads default to ["*.Cu", "*.Mask"].

Each pad may also set:

  • rotation in degrees; omit it for 0.
  • roundrect_rratio from 0 through 0.5 when shape="roundrect".
  • layers using only canonical pad layers: F.Cu, B.Cu, F.Paste, B.Paste, F.Mask, B.Mask, *.Cu, and *.Mask.
text
create_footprint(
  ...,
  pads=[{
    number: "1",
    type: "smd",
    shape: "roundrect",
    x: -8.075,
    y: 4.7,
    width: 2.5,
    height: 2.55,
    layers: ["B.Cu", "B.Paste", "B.Mask"],
    rotation: 180,
    roundrect_rratio: 0.2
  }]
)
Standard Pad Sizes Reference
PackagePad Size (mm)Pitch (mm)Notes
04020.5 x 0.5—2 pads, 0.5mm gap
06030.8 x 0.8—2 pads, 0.8mm gap
08051.0 x 1.0—2 pads, 1.0mm gap
12061.5 x 1.2—2 pads, 1.6mm gap
SOT-230.9 x 0.70.953 pads
SOT-23-50.9 x 0.70.955 pads
SOIC-81.5 x 0.61.278 pads, 5.4mm row spacing
SOIC-161.5 x 0.61.2716 pads, 5.4mm row spacing
TSSOP-161.4 x 0.40.6516 pads, 4.4mm row spacing
QFP-321.5 x 0.30.832 pads, quad-flat
QFP-481.5 x 0.30.548 pads, quad-flat
QFN-320.7 x 0.250.532 pads + exposed pad
QFN-480.7 x 0.250.548 pads + exposed pad
Show full SKILL.md (833 more words)Show less
Courtyard
  • Extend courtyard 0.25mm beyond the outermost pad edges on all sides
  • This ensures minimum spacing between components during assembly
  • Use F.CrtYd layer, 0.05mm line width
Footprint Layers
LayerPurpose
F.CuFront copper (pads)
B.CuBack copper (pads for bottom-side components)
F.MaskFront solder mask opening (auto-generated from pads)
B.MaskBack solder mask opening
F.PasteFront solder paste (stencil openings)
B.PasteBack solder paste (stencil openings)
F.SilkSFront silkscreen (component outline, pin 1 marker)
F.CrtYdFront courtyard (assembly spacing)
F.FabFront fabrication (true component dimensions)
Footprint Layout Guidelines
  • Pin 1 marker on silkscreen (dot, bar, or chamfered corner)
  • Component outline on F.Fab layer with true dimensions
  • Silkscreen outline 0.1mm outside F.Fab outline
  • Reference (%R) on F.SilkS, readable at 1.0mm text height
  • Value on F.Fab layer
Existing Footprint Graphics

Use set_footprint_graphics to add or change line, arc, rectangle, circle, or polygon primitives in an existing .kicad_mod. Never patch the file directly.

text
set_footprint_graphics(
  footprint path,
  selector={layer: "B.CrtYd"},
  mode="replace",
  graphics=[...]
)
  • append preserves existing supported graphics on the selected layer.
  • replace replaces all supported graphics on the selected layer in one atomic write.
  • delete removes all supported graphics on the selected layer.
  • Text, pads, properties, models, groups, and graphics on other layers are preserved.
  • Replacement/deletion stops with a conflict if a selected graphic belongs to a group; do not work around this by editing the file.
  • Polygons close automatically. Supply at least three distinct points; repeating the first point at the end is optional.
  • Use get_footprint_info with graphics inclusion enabled and a layer filter to verify the resulting type, geometry, stroke width, fill, and item ID.
Existing Footprint Metadata

Use set_footprint_metadata to replace a footprint description, search tags, or KiCad footprint attributes without changing pads, graphics, properties, groups, or 3D models.

text
set_footprint_metadata(
  footprint_path=".../Part.kicad_mod",
  description="Optional replacement",
  tags=["keyboard", "hot_swap"],
  attributes=["exclude_from_pos_files"]
)
  • Supply at least one metadata field.
  • Only supplied fields change.
  • Empty tags or attributes removes the corresponding block.
  • exclude_from_pos_files omits the footprint from pick-and-place output without implicitly adding exclude_from_bom.
  • Use edit_footprint_pad with new_number and optional match_all=true to renumber one or every matching direct-child pad atomically.
  • Use edit_footprint_pad with zone_connect (solid, thermal, none) to override how zones connect to one pad, or inherited to remove the override.
Existing Footprint 3D Models

Use set_footprint_models to append, replace, or delete top-level 3D model associations without changing any non-model footprint content.

text
set_footprint_models(
  footprint_path=".../Part.kicad_mod",
  mode="replace",
  models=[{
    path: "../models/Part.step",
    offset: {x: 0, y: 0, z: 0},
    scale: {x: 1, y: 1, z: 1},
    rotate: {x: 0, y: 0, z: 90}
  }]
)
  • append and replace require at least one model.
  • delete requires models to be omitted or empty and removes every top-level model.
  • Omitted transforms default to offset 0/0/0, scale 1/1/1, and rotation 0/0/0.
  • Multiple model blocks are written in payload order in one atomic operation.

Library Registration

Register a Symbol Library
register_symbol_library(nickname, library_path, scope?, project?, replace_existing?)
Register a Footprint Library
register_footprint_library(nickname, library_path, scope?, project?, replace_existing?)
  • Registration is idempotent by default: an existing nickname is left unchanged.
  • Set replace_existing=true to update a stale URI for that nickname in place.
  • Project-local and same-repository sibling libraries are written as portable ${KIPRJMOD} URIs; existing options, descriptions, and unrelated entries are preserved.
Scope
ScopeLocationVisible To
globalUser-level sym-lib-tableAll projects
projectProject-level sym-lib-tableThis project only

Recommendation: Use project scope for project-specific custom parts. Use global scope only for reusable personal libraries used across multiple projects.

Library File Locations
  • Symbol libraries: *.kicad_sym files
  • Footprint libraries: directories containing *.kicad_mod files
  • Project-level tables: sym-lib-table and fp-lib-table in project directory

IPC Naming Conventions (Brief Reference)

Standard footprint naming follows IPC-7351:

[Type]_[Dimensions]_[Pitch]_[Suffix]

Examples:

  • R_0402_1005Metric — 0402 resistor (1.0x0.5mm metric)
  • C_0805_2012Metric — 0805 capacitor (2.0x1.2mm metric)
  • SOIC-8_3.9x4.9mm_P1.27mm — SOIC-8 with 1.27mm pitch
  • QFN-32-1EP_5x5mm_P0.5mm — QFN-32 with exposed pad, 5x5mm body
  • SOT-23 — SOT-23 3-pin
  • TSSOP-16_4.4x5mm_P0.65mm — TSSOP-16 with 0.65mm pitch

Dimension format: LxW in mm (body dimensions, not pad-to-pad).


Common Workflows

Create a New IC Symbol + Footprint
  1. search_symbols(query) — pass the part name; confirm it does not exist
  2. search_footprints(query) — pass the package name; check if the footprint exists (often it does)
  3. Create symbol with correct pin count, names, numbers, and types
  4. Assign existing footprint OR create custom footprint from datasheet
  5. Register library if new
  6. Set Footprint property on symbol to link them
Add LCSC Number to Existing Components
  1. Load sch_analysis toolset
  2. Find components missing LCSC field
  3. Search JLCPCB parts for matching part numbers
  4. Update component fields with LCSC numbers
Create Project-Specific Library
  1. Create new .kicad_sym file for symbols
  2. Create new directory for footprints
  3. Register both with project scope
  4. Add custom components as needed

Rules

  1. Always search before creating — most parts already exist in KiCAD libraries
  2. Never edit .kicad_sym or .kicad_mod directly — use MCP tools only
  3. Derive pin numbering from the datasheet and verify it against the symbol — there is no universal convention; read the part back with get_symbol_info
  4. Set pin types correctly — ERC depends on accurate pin types
  5. Include all required properties — Reference, Value, Footprint, Datasheet
  6. Use 0.25mm courtyard margin — standard clearance for assembly
  7. Mark pin 1 clearly — both on symbol and footprint silkscreen
  8. Use project scope by default — avoid polluting global libraries
  9. Name footprints per IPC — consistent naming helps future reuse
  10. Load toolsets first — check get_active_toolsets() and load library before starting
  11. Use layer-scoped graphic edits deliberately — replace and delete affect every supported primitive on the selected layer

© mixelpixx, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in crates/konnect/assets/skills/kicad-library of mixelpixx/Konnect.

Open the folder on GitHubat commit 9488e5f

Compare with similar skills

Kicad Library next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Kicad Library compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Kicad Library this skillmixelpixx/Konnect917—~5.1kAutomated safety check: PassAGPL-3.0
MCP Server Builderanthropics/skills180k63 repos~2.3kAutomated safety check: PassApache-2.0
MCP Server BuildershareAI-lab/learn-claude-code78k5 repos~1.2kAutomated safety check: PassMIT
MCP Integration for Pluginsanthropics/claude-plugins-official38k11 repos~3.1kAutomated safety check: PassApache-2.0
Crush Configurationcharmbracelet/crush29k—~3.7kAutomated safety check: PassCustom licence
Context Mode Output Sandboxmksglu/context-mode26k—~4.1kAutomated safety check: PassCustom licence

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 63 repos~2.3k tokens
    Agent WorkflowsAuto-check passed
  • MCP Server Builder

    shareAI-lab/learn-claude-code

    Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.

    78k GitHub starsUsed in 5 repos~1.2k tokens
    Agent WorkflowsAuto-check passed
  • MCP Integration for Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.

    38k GitHub starsUsed in 11 repos~3.1k tokens
    Agent WorkflowsAuto-check passed
  • Crush Configuration

    charmbracelet/crush

    Explains how to configure the Crush coding agent with crushrc or crush.json, covering providers, models, LSPs, MCP servers, hooks, permissions and config precedence.

    29k GitHub stars~3.7k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Context Mode Output Sandbox

    mksglu/context-mode

    Routes large command, file, API and browser output through context-mode tools so only the needed result enters the agent's context, instead of dumping it via Bash.

    26k GitHub stars~4.1k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Migrates the compatible subset of settings and global file-based MCP servers from the Warp desktop app into Warp Agent CLI without exposing credentials or state.

    65k GitHub starsUsed in 1 repo~2.1k tokens
    Agent WorkflowsAuto-check passed

More from mixelpixx/Konnect

  • Kicad Manufacture

    mixelpixx/Konnect

    Manufacturing and fabrication workflow for KiCAD projects via MCP tools.

    917 GitHub stars~2.2k tokensUpdated 3 days ago
    Auto-check passed
  • Kicad Review

    mixelpixx/Konnect

    Design review and validation workflow for KiCAD projects via MCP tools.

    917 GitHub stars~3.2k tokensUpdated 3 days ago
    Auto-check passed
  • Kicad Schematic

    mixelpixx/Konnect

    Workflow skill for KiCAD schematic design via MCP tools. An agent skill from mixelpixx/Konnect.

    917 GitHub stars~4.1k tokensUpdated 3 days ago
    Auto-check passed
  • Kicad Pcb

    mixelpixx/Konnect

    Workflow skill for KiCAD PCB layout and routing via MCP tools.

    917 GitHub stars~5.6k tokensUpdated 3 days ago
    Auto-check passed
  • Konnect

    mixelpixx/Konnect

    Mandatory operating rules for ANY task involving KiCAD projects.

    917 GitHub stars~2.1k tokensUpdated 3 days ago
    Auto-check passed

Categories

Questions about Kicad Library

What does Kicad Library do?

Library management workflow for KiCAD — creating symbols, footprints, and managing libraries via MCP tools. Kicad Library is an agent skill from mixelpixx/Konnect. Library management workflow for KiCAD — creating symbols, footprints, and managing libraries via MCP tools.

When should I use Kicad Library?

Kicad Library fits situations like: : create a symbol; make a footprint; custom component; register library.

How do I install Kicad Library in Claude Code?

Run `npx skills add mixelpixx/Konnect --skill kicad-library -a claude-code`. Or copy the skill folder (crates/konnect/assets/skills/kicad-library in mixelpixx/Konnect) into .claude/skills/kicad-library in your project. Claude Code loads it when a task matches its description.

How do I install Kicad Library in Codex?

Run `npx skills add mixelpixx/Konnect --skill kicad-library -a codex`. Or copy the skill folder (crates/konnect/assets/skills/kicad-library in mixelpixx/Konnect) into .agents/skills/kicad-library in your project. Codex loads it when a task matches its description.

Can I use Kicad Library in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mixelpixx/Konnect --skill kicad-library -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/kicad-library, .gemini/skills/kicad-library, .github/skills/kicad-library and .opencode/skills/kicad-library in your project.

What does Kicad Library need to run?

SKILL.md names no scripts, command-line tools or credentials: Kicad Library is instructions for the agent only.

Does Kicad Library access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Kicad Library safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Kicad Library use?

Kicad Library is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Kicad Library use?

About 5.1k tokens (SKILL.md is roughly 20k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Kicad Library?

Skills that share tags, products or a category with Kicad Library: MCP Server Builder (anthropics/skills, 180k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars), MCP Integration for Plugins (anthropics/claude-plugins-official, 38k stars) and Crush Configuration (charmbracelet/crush, 29k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Kicad Library?

mixelpixx (a GitHub user) maintains it in mixelpixx/Konnect, which has 917 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 6, 2026.

Source: mixelpixx/Konnect on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.