Agent skill

Wired Subcircuit Design

by oaslananka in oaslananka/kicad-mcp-pro

Build a genuinely wired, showcase-grade KiCad schematic with KiCad MCP Pro — wired sub-circuit islands plus a tidy label bus — instead of the correct-but-plain by-name-label output of auto layout.

MITAuto-check passedAgent Workflows

Install Wired Subcircuit Design

skills CLI
$ npx skills add oaslananka/kicad-mcp-pro --skill wired-subcircuit-design -a claude-code

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

GitHub CLI
$ gh skill install oaslananka/kicad-mcp-pro wired-subcircuit-design --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/oaslananka/kicad-mcp-pro.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/wired-subcircuit-design .claude/skills/wired-subcircuit-design && 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
wired-subcircuit-design
GitHub stars
120
Token cost
~1.2k tokens
SKILL.md length
643 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

Build a genuinely wired, showcase-grade KiCad schematic with KiCad MCP Pro — wired sub-circuit islands plus a tidy label bus — instead of the correct-but-plain by-name-label output of auto layout.

  • Works in 6 steps: Anchor the main part (MCU / module) in… → Wire the sub-circuit islands.… → Label bus for the breakout. Route… → …
  • Tasks that involve MCP servers
  • SKILL.md covers Why auto layout is not enough, The one rule that avoids a…, Design pattern and Attach labels correctly, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Wired Subcircuit Design is an agent skill from oaslananka/kicad-mcp-pro. Build a genuinely wired, showcase-grade KiCad schematic with KiCad MCP Pro — wired sub-circuit islands plus a tidy label bus — instead of the correct-but-plain by-name-label output of auto layout.

Its SKILL.md is about 1.2k 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: MCP server for KiCad, connecting AI agents to schematic and PCB workflows, ERC/DRC validation, DFM checks, BOM analysis, and manufacturing preparation—with controlled edits and… The licence is MIT.

When your agent uses it

  • Tasks that involve MCP servers

Example prompts

  • “/wired-subcircuit-design”

Workflow steps

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

  1. Anchor the main part (MCU / module) in the center.
  2. Wire the sub-circuit islands. Decoupling, reset, boot-strap, status LED,
  3. Label bus for the breakout. Route general IO to a header with matched local
  4. Conventional power. +3V3 up, GND down; put exactly one PWR_FLAG on
  5. Place each sub-circuit in its own x-column below the anchor, and keep
  6. Fill the title block with sch_set_title_block_info.

What it can do on your machine

Read from SKILL.md and the folder at commit bfbed31. 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

Wired Subcircuit Design loads about 1.2k tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 643 words of instructions outside code blocks.

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

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 oaslananka/kicad-mcp-pro at commit bfbed31, republished under its MIT licence (© oaslananka). 643 words, ~1,190 tokens.

Download SKILL.mdSave it as .claude/skills/wired-subcircuit-design/SKILL.md (or your agent's skills folder).
name
wired-subcircuit-design
description
Build a genuinely wired, showcase-grade KiCad schematic with KiCad MCP Pro — wired sub-circuit islands plus a tidy label bus — instead of the correct-but-plain by-name-label output of auto layout.

Wired Sub-circuit Design Skill

Use this skill when an agent must produce a schematic that looks like a person drew it — wired functional blocks, conventional power, a clean breakout bus — not just an electrically valid netlist. It is the deliberate, higher-effort path that sch_build_circuit(auto_layout=True, nets=...) cannot reach.

Specific to oaslananka/kicad-mcp-pro. Keep in sync with docs/tools-reference.generated.md. Worked reference: examples/gallery/esp32-c3-wroom-02-breakout.

Why auto layout is not enough

sch_build_circuit with nets uses a collision-safe terminal strategy: every pin endpoint gets a stub plus a same-named global label / power symbol, so nets connect by name and can never short by crossing geometry. That is correct and ERC-clean, but it reads as a machine netlist: every decoupling cap floats between its own +3V3 and GND labels instead of being wired. Showcase quality needs explicit placement and wires. The cosmetic score never measures this — judge the render, not the number.

The one rule that avoids a blank sheet

Build the whole sheet in a single sch_build_circuit pass with explicit symbols (with coordinates), wires, labels and power_symbols — and no nets, no auto_layout. Do not assemble a schematic from scratch with repeated sch_add_symbol calls: a freshly seeded sheet has no root UUID that the reader round-trips, so each incremental add stamps a different instance path and KiCad renders a blank sheet even though the file parses. One pass writes one consistent root UUID, so every symbol lands on the root sheet.

Compute exact pin coordinates up front with get_pin_positions(lib, sym, x, y, rot) (pure geometry — no placement needed), then wire pin-tip to pin-tip.

Design pattern

  1. Anchor the main part (MCU / module) in the center.
  2. Wire the sub-circuit islands. Decoupling, reset, boot-strap, status LED, regulators — draw each as a real wired block ending in power symbols. This is what separates a showcase from auto output; do not let these become floating labelled pins.
  3. Label bus for the breakout. Route general IO to a header with matched local labels. Generate the part-side and header-side labels from one source list so the two label sets are identical by construction — this eliminates the whole isolated_pin_label / label_dangling class, not just the ones you happen to see.
  4. Conventional power. +3V3 up, GND down; put exactly one PWR_FLAG on each supply net so ERC sees the rails driven.
  5. Place each sub-circuit in its own x-column below the anchor, and keep decoupling clear of the anchor's stub fan — most first-pass ERC errors (multiple_net_names) come from a power symbol landing on a neighbouring label.
  6. Fill the title block with sch_set_title_block_info.
Show full SKILL.md (225 more words)Show less

Attach labels correctly

A net label must sit on a wire endpoint. When tapping a sub-circuit node, add a short stub wire and place the label at the stub's free end — a label floating beside a wire raises label_dangling.

The loop

  1. Plan all coordinates from get_pin_positions; assemble the four lists.
  2. Build in one sch_build_circuit pass.
  3. Guard with ERC. Run run_erc. Fix every violation before judging looks — a blank/oddly-passing ERC means KiCad isn't reading your symbols (see the root UUID rule).
  4. See. Render with sch_render_png (or kicad-cli sch export svg) and judge against the rubric below. The render is ground truth.
  5. Refine placement for overlaps and composition; rebuild. Stop when ERC is clean and nothing overlaps — do not chase the cosmetic score past that.

Rubric — what "wired showcase" looks like

  • Functional blocks are wired, not floating labelled pins.
  • Power symbols are conventional; one PWR_FLAG per supply.
  • The breakout bus is tidy and every label is matched (no isolated labels).
  • Orthogonal wiring, on-grid, no diagonal runs, no overlapping graphics.
  • Complete title block; content composed rather than crammed in one corner.

Guardrails

  • Wired ≠ correct-by-magic. Finish with run_erc; a showcase must also be clean.
  • Prefer the label bus over routed nets wires (unsafe_routed_wires=True can short by crossing geometry — avoid it).
  • One curated example is worth more than a bulk auto-generated gallery; expect per-example effort.

© oaslananka, MIT. 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 skills/wired-subcircuit-design of oaslananka/kicad-mcp-pro.

Open the folder on GitHubat commit bfbed31

Compare with similar skills

Wired Subcircuit Design 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.

Wired Subcircuit Design compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Wired Subcircuit Design this skilloaslananka/kicad-mcp-pro120—~1.2kAutomated safety check: PassMIT
Crush Configurationcharmbracelet/crush29k—~3.7kAutomated safety check: PassCustom licence
PicoClaw Agentsipeed/picoclaw30k—~7.2kAutomated safety check: NotesMIT
Chatgpt AppsHaohao-end/openagent7911 repos~4.9kAutomated safety check: PassApache-2.0
Chatgpt App Builderalpic-ai/skybridge2.2k—~1kAutomated safety check: PassMIT
Agent Setup Health Audittw93/Waza7.2k—~5.2kAutomated safety check: NotesMIT

Similar skills

  • 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
  • PicoClaw Agent

    sipeed/picoclaw

    Answers questions about running and changing PicoClaw, from onboarding and model selection to MCP server setup, skill loading and scheduled jobs.

    30k GitHub stars~7.2k tokensUpdated yesterday
    Agent WorkflowsAuto-check: notes
  • Chatgpt Apps

    Haohao-end/openagent

    Build, scaffold, refactor, and troubleshoot ChatGPT Apps SDK applications that combine an MCP server and widget UI.

    791 GitHub starsUsed in 1 repo~4.9k tokens
    Agent WorkflowsAuto-check passed
  • Chatgpt App Builder

    alpic-ai/skybridge

    Guide developers through creating and updating ChatGPT plugins.

    2.2k GitHub stars~1k tokensUpdated 2 days ago
    Agent WorkflowsAuto-check passed
  • Audits a project's agent configuration, instruction drift, hooks, MCP and AI maintainability, then reports prioritized findings with evidence and next actions.

    7.2k GitHub stars~5.2k tokensUpdated today
    Agent WorkflowsAuto-check: notes
  • Record Demo

    apify/mcpc

    Official

    Record or regenerate the mcpc demo GIFs (the README hero docs/images/mcpc-demo.gif and the focused tapes in docs/vhs/) with VHS.

    1k GitHub stars~3.3k tokensUpdated yesterday
    Agent WorkflowsAuto-check: notes

More from oaslananka/kicad-mcp-pro

All 11 skills in this repo
  • Kicad Pcb Review

    oaslananka/kicad-mcp-pro

    A skill your agent uses when reviewing, fixing, validating, or preparing KiCad PCB projects with the kicad MCP server.

    120 GitHub stars~585 tokensUpdated today
    Auto-check passed
  • Code Review

    oaslananka/kicad-mcp-pro

    A skill your agent uses for GitHub Copilot pull request and code reviews in oaslananka/kicad-mcp-pro.

    120 GitHub stars~3.9k tokensUpdated today
    Auto-check passed
  • Kicad Design Review

    oaslananka/kicad-mcp-pro

    Comprehensive KiCad design review skill covering schematic, PCB, DFM, manufacturing, high-speed, and simulation review workflows.

    120 GitHub stars~529 tokensUpdated today
    Auto-check passed
  • Repo Repair

    oaslananka/kicad-mcp-pro

    A skill your agent uses for maintainer-requested pull request repairs in kicad-mcp-pro; maps changes to repository-native validation gates and safety constraints.

    120 GitHub stars~581 tokensUpdated today
    Auto-check passed
  • Drc Check

    oaslananka/kicad-mcp-pro

    KiCad MCP workflow for ERC/DRC execution, issue triage, waiver review, and revalidation.

    120 GitHub stars~1k tokensUpdated today
    Auto-check passed
  • Fabrication Output

    oaslananka/kicad-mcp-pro

    KiCad MCP manufacturing release workflow for Gerbers, drill files, BOM, pick-and-place, DFM, release evidence, and final human review.

    120 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

Questions about Wired Subcircuit Design

What does Wired Subcircuit Design do?

Build a genuinely wired, showcase-grade KiCad schematic with KiCad MCP Pro — wired sub-circuit islands plus a tidy label bus — instead of the correct-but-plain by-name-label output of auto layout. Wired Subcircuit Design is an agent skill from oaslananka/kicad-mcp-pro. Build a genuinely wired, showcase-grade KiCad schematic with KiCad MCP Pro — wired sub-circuit islands plus a tidy label bus — instead of the correct-but-plain by-name-label output of auto layout.

When should I use Wired Subcircuit Design?

Wired Subcircuit Design fits situations like: tasks that involve MCP servers.

How do I install Wired Subcircuit Design in Claude Code?

Run `npx skills add oaslananka/kicad-mcp-pro --skill wired-subcircuit-design -a claude-code`. Or copy the skill folder (skills/wired-subcircuit-design in oaslananka/kicad-mcp-pro) into .claude/skills/wired-subcircuit-design in your project. Claude Code loads it when a task matches its description.

How do I install Wired Subcircuit Design in Codex?

Run `npx skills add oaslananka/kicad-mcp-pro --skill wired-subcircuit-design -a codex`. Or copy the skill folder (skills/wired-subcircuit-design in oaslananka/kicad-mcp-pro) into .agents/skills/wired-subcircuit-design in your project. Codex loads it when a task matches its description.

Can I use Wired Subcircuit Design 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 oaslananka/kicad-mcp-pro --skill wired-subcircuit-design -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/wired-subcircuit-design, .gemini/skills/wired-subcircuit-design, .github/skills/wired-subcircuit-design and .opencode/skills/wired-subcircuit-design in your project.

What does Wired Subcircuit Design need to run?

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

Does Wired Subcircuit Design 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 Wired Subcircuit Design 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 Wired Subcircuit Design use?

Wired Subcircuit Design is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Wired Subcircuit Design use?

About 1.2k tokens (SKILL.md is roughly 4.8k 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 Wired Subcircuit Design?

Skills that share tags, products or a category with Wired Subcircuit Design: Crush Configuration (charmbracelet/crush, 29k stars), PicoClaw Agent (sipeed/picoclaw, 30k stars), Chatgpt Apps (Haohao-end/openagent, 791 stars) and Chatgpt App Builder (alpic-ai/skybridge, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Wired Subcircuit Design?

oaslananka (a GitHub user) maintains it in oaslananka/kicad-mcp-pro, which has 120 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 10, 2026.

Source: oaslananka/kicad-mcp-pro on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.