AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Kicad Project

skill-avatarsd-kiskill-kicad-project · by AvatarSD

>

No reviews yet
0 installs
5 views
0.0% view→install

Install

$ agentstack add skill-avatarsd-kiskill-kicad-project

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets Used
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-avatarsd-kiskill-kicad-project)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Kicad Project? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

KiCad project state machine

Repo: $(kx root) (engine + design docs).

Session entry protocol (always)

  1. kx env PROJECT_DIR — one call: kicad-cli (+nightly) version, lock

files (tilde = literal filename prefix), IPC socket/aliveness, recommended backend. If backends.file.writable_now is false, KiCad has the project OPEN: do not write; ask the user to close/reload, or work on a scratch copy. kx = ~/.local/bin/kx → repo bin/kx (self-sets PYTHONPATH; works from any cwd). Python API instead: run with PYTHONPATH=$(kx root) (no pip install). kicad-cli is resolved by kicadlib/kcli.py: KXKICAD_CLI env → native on PATH → flatpak → nightly. VERSION-SKEW RULE: evidence (ERC/render/netlist) must come from the same engine that writes the files — if the user edits with the v11 nightly, set KX_KICAD_CLI=kicad-cli-nightly for the session; a stable CLI may misread nightly-saved files and the diff/ERC evidence silently lies.

  1. Git: checkpoint-commit the project BEFORE the first modification.
  2. kx probe FILE — inventory (uuid, paper, symbols/refs, labels,

sheets, cached libs).

State machine (DESIGN.md §3)

CLEAN → PROBED → STAGED → VERIFIED (geometric verifier 0 violations) → RENDERED (svg→png, ERC run) → REVIEWED (pixel+semantic+ERC diff judged against rule canon) → COMMITTED. Never skip a state; never write a file that has not passed VERIFIED; never commit one that has not been REVIEWED.

Live IPC against the v11 nightly (validated 10.99.0 build 87de73b)

  • Enable once (KiCad closed): set api.enable_server: true in

~/.config/kicad/10.99/kicad_common.json.

  • Launch on a SCRATCH COPY (the nightly upgrades file formats on save):

DISPLAY=:1 sh -c '. /usr/share/kicad-nightly/kicad-nightly.env && /usr/lib/kicad-nightly/bin/eeschema COPY.kicad_sch' in background. GUI needs X11 — pick the DISPLAY where xset q answers. Kill it later with pkill; then rm stale ~*.lck files.

  • Socket appears at /tmp/kicad/api.sock within ~1 s; verify with

kx envipc_alive: true, open_documents lists the schematic.

  • kipy MASTER is required (PyPI 0.7.1's schematic module is broken

against its own protos). Bootstrap: tools/bootstrap_kipy.sh (protoc 29.x in ~/.local + protol; .pth-installs .tools/kicad-python).

  • HANDLER MAP (each frame registers its own handlers in-process):
  • standalone eeschema HANDLES: getopendocuments, get_schematic,

getitems/symbols/lines/labels/text, begin/push commit, createitems, remove_items — full live editing, undoable in GUI.

  • standalone eeschema LACKS (ApiError "no handler"): ping,

getversion, save, saveas, revert, run_action — the agent CANNOT persist from IPC; the USER saves (Ctrl+S), or do at-rest edits via the file backend instead.

  • kicad PM process handles ONLY ping + get_version (no frames).

Opening eeschema FROM the PM should merge both sets — needs one GUI click (no xdotool on this box). Re-test on newer nightlies: tests/testliveipc.py prints the gap map and flags improvements.

  • live.py's ipc_ping treats a structured ApiError as alive (transport

answered). kicad-cli-nightly (wrapper in /usr/bin) is the only way to run the nightly CLI — the raw binary fails on LDLIBRARYPATH.

Project hygiene

  • References are global across ALL sheets — collision-check project-wide.
  • Preserve root uuid and per-sheet uuids; instance paths depend on them.
  • sym-lib-table / fp-lib-table: project-local libs use ${KIPRJMOD} URIs.
  • Scratch outputs (svg_out/, .rpt, .net, *.png) never get committed.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.