Agent skill

Kicad Manufacture

by mixelpixx in mixelpixx/Konnect

Manufacturing and fabrication workflow for KiCAD projects via MCP tools.

AGPL-3.0Auto-check passedAgent Workflows

Install Kicad Manufacture

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

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

GitHub CLI
$ gh skill install mixelpixx/Konnect kicad-manufacture --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-manufacture .claude/skills/kicad-manufacture && 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-manufacture
GitHub stars
927
Token cost
~2.2k tokens
SKILL.md length
1,025 words
Files
3 (incl. references)
Skills in repo
6
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Manufacturing and fabrication workflow for KiCAD projects via MCP tools.

  • Works in 6 steps: Capture the order contract → Establish direct design evidence → Export into a fresh destination → …
  • Export for production
  • SKILL.md covers Toolset loading, 1. Capture the order contract, 2. Establish direct design… and 3. Export into a fresh…, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Kicad Manufacture is an agent skill from mixelpixx/Konnect. Manufacturing and fabrication workflow for KiCAD projects via MCP tools. Triggers on: "send to fab", "order boards", "gerbers", "JLCPCB", "manufacturing", "export for production", "pick and place", "assembly files", "generate fabrication outputs", "BOM for fab", "production files", "fab house".

Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/gerber-layers.md` and `references/jlcpcb-rules.md`).

It sits in Agent Workflows, covering MCP servers. It works with EasyEDA. 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

  • Export for production
  • Generate fabrication outputs
  • Production files

Example prompts

  • “send to fab”
  • “order boards”
  • “gerbers”
  • “/kicad-manufacture”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Capture the order contract
  2. Establish direct design evidence
  3. Export into a fresh destination
  4. Use manual exports when control is required
  5. Treat cost output as a heuristic
  6. Record manufacturing acceptance

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 Manufacture loads about 2.2k tokens when it runs, and up to ~3.7k if it reads all its reference files. Until then it costs about 78 tokens; SKILL.md has 1,025 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~78
When it runs · the whole SKILL.md, loaded when a task matches
~2.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.7k

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). 1,025 words, ~2,221 tokens.

Download SKILL.mdSave it as .claude/skills/kicad-manufacture/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
kicad-manufacture
description
Manufacturing and fabrication workflow for KiCAD projects via MCP tools. Triggers on: "send to fab", "order boards", "gerbers", "JLCPCB", "manufacturing", "export for production", "pick and place", "assembly files", "generate fabrication outputs", "BOM for fab", "production files", "fab house".
argument-hint
[fab house or export task]

KiCAD Manufacturing & Fabrication Workflow

Prepare manufacturing outputs through Konnect MCP tools. Treat each tool result as evidence with a named scope: a successful request is not by itself proof of a complete, current, upload-ready package. A required check or artifact that cannot be established makes the manufacturing verdict INCOMPLETE.

Toolset loading

Load the required toolsets:

load_toolset('pcb_export')       # Gerber, drill, BOM, position, 3D, and direct DRC evidence
load_toolset('manufacturing')    # Package export, manufacturing preflight, and rough cost estimate

Load additional toolsets only for the branch that needs them:

load_toolset('sch_analysis')     # schematic inventory and footprint assignment
load_toolset('integration')      # local JLCPCB catalogue and alternatives

Call get_active_toolsets() before loading more.

References by manufacturing branch
  • Read references/gerber-layers.md when selecting plot layers or accepting a generated artifact inventory.
  • Read references/jlcpcb-rules.md only when JLCPCB is the selected fabricator or assembler. It defines how to capture the current order contract without caching volatile limits, prices, categories, or field names in this skill.

1. Capture the order contract

Before checking or exporting, record the selected fabricator, service tier, stackup, copper weight, finish, assembly sides, stencil requirement, quantity, and any controlled-impedance service. Record the source and retrieval date for every vendor-controlled requirement. Project rules and output acceptance are judged against that record.

Completion criterion: every applicable fabrication and assembly constraint has one current authority, and no decision rests on an undated table in this skill.

2. Establish direct design evidence

Run direct KiCad DRC against the saved target board and resolve every error or record a deliberate, reviewable waiver. Then run:

validate_for_manufacturing(board, fab_house?)

The current handler checks only:

  • presence of at least one Edge.Cuts item;
  • presence of footprints;
  • the configured minimum trace width against its built-in fab profile;
  • the coarse case where several nets exist but no routed tracks exist; and
  • direct kicad-cli DRC evidence, which must be available and complete for a READY verdict.

Read verdict, issues, and drc together. A null or incomplete drc, a NOT READY verdict, or an unadjudicated issue blocks release.

This preflight does not prove outline closure, copper on every pad, drill-size acceptance, silkscreen clearance, stackup compatibility, or assembly readiness. Establish those separately with direct DRC, the selected fabricator's current contract, Gerber/drill inspection, BOM/CPL review, and the order preview.

Completion criterion: direct DRC is complete, every reported issue is resolved or waived, and every check outside the handler's stated scope has named evidence.

3. Export into a fresh destination

Prefer a new, empty output directory for each invocation. This makes stale files structurally unable to impersonate output from the current invocation.

For a package attempt:

export_manufacturing_package(board, output_dir, fab_house?, schematic?, jlcpcb_cpl_corrections_path?)

Pass schematic when assembly output requires a BOM. The tool attempts Gerber, drill, position, and BOM exports according to the request; individual failures can still leave a partial directory.

For JLCPCB assembly, open the exact target board with IPC enabled before export. The package uses a stable live board snapshot and native pad-box midpoints; placement_orientation.geometry records the observed source. Saved project settings and schematic BOM remain separate inputs. Review legacy position offsets that compensated for anchors before retaining them. Read docs/JLCPCB_CPL_CORRECTIONS.md for coordinates, refusals, and migration details.

For fab_house="jlcpcb", use millimetres (the default) and provide the BOM fields, labels, and grouping required by the current order contract. The tool emits BOM-<project>.csv plus CPL-<project>.csv; the CPL uses JLCPCB's Designator,Mid X,Mid Y,Layer,Rotation schema, and KiCad is instructed to enumerate grouped BOM references instead of compressing them into ranges. DNP parts are excluded from both native exports; any remaining population mismatch caused by board/schematic exclusion flags makes the package incomplete. This conversion applies Konnect's independently verified built-in CPL correction policy. Pass a checked-in project policy through jlcpcb_cpl_corrections_path when an unmatched footprint or one exact designator needs a correction. The precedence and JSON format are documented in docs/JLCPCB_CPL_CORRECTIONS.md.

Inspect placement_orientation.applied_corrections and placement_orientation.unmatched_footprints. complete: true proves the package is structurally complete; it does not prove physical placement orientation. Require placement_orientation.status == "PREVIEW_REQUIRED" to be discharged by inspecting every component in JLCPCB Component Placements before an order is approved. Never describe the CPL as physically validated from the automated result alone.

Show full SKILL.md (398 more words)Show less
Artifact acceptance gate
  1. Inspect warnings and files_generated. Any warning or missing requested artifact type keeps the result INCOMPLETE.
  2. Reconcile the requested copper, mask, silkscreen, paste, and Edge.Cuts layers against the actual files in the fresh output directory.
  3. Confirm every required artifact is a regular, non-empty file produced by the current invocation. A directory entry, reported path, or zero exit status is not enough.
  4. Confirm the required plated and non-plated drill outputs for the actual board hole inventory. Absence is acceptable only when the design proves that output is inapplicable.
  5. Open the Gerbers and drills in a viewer. Inspect layer registration, outline, apertures, holes/slots, mask, paste, and silkscreen.
  6. For assembly, inspect BOM contents, DNP handling, designator coverage, CPL side/units/origin/rotation, and the fabricator's export preview.

The files field is derived from regular, non-empty artifacts verified at the export boundary; files_generated describes each successful export. That evidence does not establish vendor acceptance, correct component rotations, or that unrelated stale files elsewhere in a reused directory are safe to upload. Preserve the viewer and order-preview checks.

Completion criterion: an accepted manifest accounts for every required output, every accepted path is fresh and non-empty, and visual/order previews agree with the saved design.

4. Use manual exports when control is required

Use the individual tools when a package needs explicit layer, BOM, side, unit, or filename choices:

export_gerber(board, output_dir, layers?, drill_file?)
export_bom(schematic, output, format?, fields?, group_by?, labels?, exclude_dnp?)
export_position_file(board, output, format?, side?, units?)

Apply the same fresh-destination and artifact acceptance gate. A manual sequence does not lower the evidence requirement.

5. Treat cost output as a heuristic

estimate_cost(board, quantity?, layers?, fab_house?)

estimate_cost is an indicative heuristic built from fixed assumptions and rough average component costs. Use it only for coarse comparisons. It is not a vendor quote and does not know the selected finish, service, complete BOM, shipping, taxes, coupons, or current pricing. Budget and purchasing decisions require a current quote from the selected fabricator.

6. Record manufacturing acceptance

The final report must include:

  • saved design revision or hash;
  • direct DRC status and any explicit waivers;
  • validate_for_manufacturing verdict, issues, and DRC coverage;
  • selected fabricator/order contract with source and retrieval date;
  • accepted artifact manifest with file type, path, and non-empty evidence;
  • Gerber/drill viewer result;
  • BOM/CPL and order-preview result when assembly is in scope;
  • 3D/enclosure inspection status when mechanically relevant; and
  • final READY, NOT READY, or INCOMPLETE verdict.

Only READY permits upload. Preserve the accepted manifest rather than telling the user to upload every entry found in a reused directory.

© 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

SKILL.md and 2 other files (references) in crates/konnect/assets/skills/kicad-manufacture of mixelpixx/Konnect.

  • SKILL.md
  • references/gerber-layers.md
  • references/jlcpcb-rules.md

Open the folder on GitHubat commit 9488e5f

Compare with similar skills

Kicad Manufacture 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 Manufacture compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Kicad Manufacture this skillmixelpixx/Konnect927—~2.2kAutomated safety check: PassAGPL-3.0
Autodesignsalitronic/eda-agent244—~1.2kAutomated safety check: PassApache-2.0
Easyeda Copilotbiosshot/easyeda-copilot170—~2.7kAutomated safety check: PassMIT
MCP Server Builderanthropics/skills180k63 repos~2.3kAutomated safety check: PassApache-2.0
MCP Server BuildershareAI-lab/learn-claude-code78k4 repos~1.2kAutomated safety check: PassMIT
MCP Integration for Pluginsanthropics/claude-plugins-official38k11 repos~3.1kAutomated safety check: PassApache-2.0

Similar skills

  • Autodesign

    salitronic/eda-agent

    Drive an autonomous spec-to-board PCB design with the eda-agent MCP server (Altium Designer or EasyEDA Pro).

    244 GitHub stars~1.2k tokensUpdated 4 days ago
    Agent WorkflowsAuto-check passed
  • Easyeda Copilot

    biosshot/easyeda-copilot

    Create, modify, place, route, or review EasyEDA schematics and PCBs with EasyEDA Copilot, using direct MCP tools when available or the generated standalone CLI skill.

    170 GitHub stars~2.7k tokensUpdated 2 days ago
    Agent WorkflowsAuto-check passed
  • 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 4 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
  • Microsoft Skill Creator

    MicrosoftDocs/mcp

    Official

    Create agent skills for Microsoft technologies using official documentation.

    1.9k GitHub starsUsed in 3 repos~2.1k tokens
    Agent WorkflowsAuto-check passed

More from mixelpixx/Konnect

  • Kicad Review

    mixelpixx/Konnect

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

    927 GitHub stars~3.2k tokensUpdated 5 days ago
    Auto-check passed
  • Kicad Schematic

    mixelpixx/Konnect

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

    927 GitHub stars~4.1k tokensUpdated 5 days ago
    Auto-check passed
  • Kicad Pcb

    mixelpixx/Konnect

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

    927 GitHub stars~5.6k tokensUpdated 5 days ago
    Auto-check passed
  • Konnect

    mixelpixx/Konnect

    Mandatory operating rules for ANY task involving KiCAD projects.

    927 GitHub stars~2.1k tokensUpdated 5 days ago
    Auto-check passed
  • Kicad Library

    mixelpixx/Konnect

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

    927 GitHub stars~5.1k tokensUpdated 5 days ago
    Auto-check passed

Works with

Categories

Questions about Kicad Manufacture

What does Kicad Manufacture do?

Manufacturing and fabrication workflow for KiCAD projects via MCP tools. Kicad Manufacture is an agent skill from mixelpixx/Konnect. Manufacturing and fabrication workflow for KiCAD projects via MCP tools.

When should I use Kicad Manufacture?

Kicad Manufacture fits situations like: export for production; generate fabrication outputs; production files.

How do I install Kicad Manufacture in Claude Code?

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

How do I install Kicad Manufacture in Codex?

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

Can I use Kicad Manufacture 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-manufacture -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-manufacture, .gemini/skills/kicad-manufacture, .github/skills/kicad-manufacture and .opencode/skills/kicad-manufacture in your project.

What does Kicad Manufacture need to run?

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

Does Kicad Manufacture 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 Manufacture 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 Manufacture use?

Kicad Manufacture 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 Manufacture use?

About 2.2k tokens (SKILL.md is roughly 8.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.5k tokens, read only when the agent opens those files.

What are the alternatives to Kicad Manufacture?

Skills that share tags, products or a category with Kicad Manufacture: Autodesign (salitronic/eda-agent, 244 stars), Easyeda Copilot (biosshot/easyeda-copilot, 170 stars), MCP Server Builder (anthropics/skills, 180k stars) and MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Kicad Manufacture?

mixelpixx (a GitHub user) maintains it in mixelpixx/Konnect, which has 927 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.