Skills

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

adom-wiki skills install adom/altium-schlib
main 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-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

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.