Skills

The skills this repo ships, by tier, each with a quick health read. Install the user skills with:

adom-wiki skills install adom/adom-lbr
No maintainer skills. This open-source app ships no dev-skills/ or publish-skills/, so a contributor (or their AI) has no in-repo guide to build, debug, or publish it. Consider adding them; they stay source-only and never ship in the tarball.
main skill adom-lbr view SKILL.md

adom-lbr — the EDA library translator. Bring a component in from ANY supported EDA tool and convert it to ANY other; the canonical adom-lbr JSON (symbol + footprint + 3D + pin↔pad map) is the hub. Import from KiCad OR Altium; export to NATIVE Altium (.SchLib/.PcbLib/.IntLib — real OLE2 binary, no Altium needed), KiCad (.kicad_sym + .kicad_mod), or EAGLE/Fusion .lbr. Merge a symbol into an existing .SchLib. `adom-lbr manage` opens the Manager: browse wiki components, view symbol/footprint/3D + the per-EDA (KiCad vs Altium) footprint layer stackup. Trigger words: adom-lbr, altium schlib pcblib intlib, convert to altium, kicad to altium, altium to kicad, any eda to any eda, eda translator, lbr, eagle library, fusion library, adom-lbr json, kicad convert, adom-lbr manager, layer stackup.

305 lines · 2.6kw · longpreamblenamedescription (long)triggersuser-invocablestructureheadingsexample
sub-skill altium-schlib view SKILL.md

Native Rust crate that parses Altium .SchLib (and .IntLib) binary schematic- symbol libraries — an OLE2 Compound File container holding a reverse-engineered binary pin-record format. Emits KiCad-shaped pin JSON, renders a native symbol SVG, and emits .kicad_sym for export. The symbol counterpart to altium-pcblib (footprints); together they read both halves of an Altium library natively, with no Altium install and no KiCad/service round-trip. Used by adom-sfconvert + chip-fetcher so each format renders its OWN geometry for cross-source comparison. Public Rust API: parse_altium_schlib_path(&Path), parse_altium_schlib_bytes(&[u8]), render_symbol_svg(&Value), to_kicad_sym(&Value, name). Validated 28/28 pins (number + name, overbars included) against KiCad 10's Altium importer on ADS1263IPWR.

66 lines · 363wpreamblenamedescription (long)triggersuser-invocableparent linkstructureheadingsexample
sub-skill altium-schlib view SKILL.md

Native Rust crate that parses Altium .SchLib (and .IntLib) binary schematic- symbol libraries — an OLE2 Compound File container holding a reverse-engineered binary pin-record format. Emits KiCad-shaped pin JSON, renders a native symbol SVG, and emits .kicad_sym for export. The symbol counterpart to altium-pcblib (footprints); together they read both halves of an Altium library natively, with no Altium install and no KiCad/service round-trip. Used by adom-sfconvert + chip-fetcher so each format renders its OWN geometry for cross-source comparison. Public Rust API: parse_altium_schlib_path(&Path), parse_altium_schlib_bytes(&[u8]), render_symbol_svg(&Value), to_kicad_sym(&Value, name). Validated 28/28 pins (number + name, overbars included) against KiCad 10's Altium importer on ADS1263IPWR.

66 lines · 363wpreamblenamedescription (long)triggersuser-invocableparent linkstructureheadingsexample
sub-skill adom-lbr-fusion-export view SKILL.md

Export a KiCad part to a Fusion 360 library (.lbr) with a REAL footprint and a 3D body — and avoid the four traps that bite. Companion to the adom-lbr app. Use when generating/importing an EAGLE .lbr for Fusion 360 (or Altium/OrCAD), attaching a 3D model to a Fusion package, or debugging a wrong footprint / a gray 3D placeholder / a rejected URN. Trigger words: fusion library export, fusion 360 library, lbr for fusion, eagle lbr, .lbr footprint, lbr 3d model, package3d, package3dinstance, wip_urn, fusion cloud urn, adsk.wipprod fs.file, bind 3d, create3dpackage, lbr placeholder footprint, lbr footprint wrong, fusion gray placeholder, fusion no components, altium lbr, orcad lbr.

115 lines · 887wpreamblenamedescription (long)triggersuser-invocableparent linkstructureheadingsexample

Health: the size chip is green when right-sized, yellow when getting long, red when the model likely skims it. A green check is a passed preamble/structure signal; an amber mark is a gentle nudge, not a hard failure.