akcli-altium-interoplisted

Work with Altium Designer through the zero-dependency `akcli` CLI: parse Altium .SchDoc/.SchLib/.PcbDoc files without an Altium install, export normalized JSON and Protel/KiCad/CSV netlists, deliver schematic edits back into Altium (offline human draw instructions + importable netlist, or the optional Windows Altium 22+ live bridge), and migrate Altium designs to KiCad with netlist-diff verification. Use this skill whenever the task involves: reading, exporting, or converting an Altium file; getting a design out of Altium into another tool; getting changes into an Altium schematic; an Altium-to-KiCad migration or equivalence check; or the Altium live bridge. Triggers on keywords: Altium, Altium Designer, SchDoc, SchLib, PcbDoc, Protel netlist, OLE2/CFBF, Altium export, Altium import, migrate to KiCad, AD to KiCad, live bridge, DelphiScript, X2.EXE.
tipoLi5890/akcli · ★ 4 · Data & Documents · score 74

Install: claude install-skill tipoLi5890/akcli

# akcli-altium-interop — Altium Designer in and out through `akcli` This skill covers the Altium-specific interop surface of `akcli`: what Altium content parses, how to get designs **out** (JSON / netlists), how to get changes **in** (offline instructions or the optional Windows live bridge), and how to migrate AD → KiCad with proof of equivalence. For general read/analyze/draw mechanics (op-list format, `plan`/ `draw`, checks, exit codes, config), **see the akcli-circuit-design skill** — do not re-derive them here. ## What parses vs. what is refused (and the read-only guarantee) `akcli` opens Altium OLE2/CFBF containers directly, on any OS, with **strictly read-only** access — no code path modifies a `.SchDoc`/`.SchLib`/`.PcbDoc`, ever. Parses: - **`.SchDoc`** — components, pins (electrical-tip coordinates), designators, parameters, footprints, wires/junctions/net labels/power ports/ports/No-ERC markers → full inferred netlist. Hierarchical designs are followed: sheet symbols (RECORD 15/16) recurse into child `.SchDoc`s with per-instance namespaces and sheet-entry↔child-port pairing (Altium *Automatic* scope: ports merge globally only in designs without sheet symbols). `.PrjPcb` is accepted too — akcli reads the project's top sheet and honors `PowerPortNamesTakePriority`. Sheet-entry edge-position scale follows the documented convention; validating against a real AD hierarchical design is still pending — flag it when it matters. - **`.SchLib`** — text-rec