Skills

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

adom-wiki skills install adom/solidworks-bridge
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 solidworks-bridge view SKILL.md

Drive SOLIDWORKS desktop CAD on the user's Windows PC from any Adom container through swx_* verbs - create parts, assemblies and drawings, open and import files, model with a JSON DSL, read geometry back in mm, drive dimensions, export a dozen formats, generate BOMs, run mass-properties/interference/rebuild checks, and close or quit SOLIDWORKS safely (every open document is saved to a recovery folder first). Use when the user mentions SOLIDWORKS or its files, asks to model, open, import, export or measure a CAD part, wants a BOM or custom properties, or wants SOLIDWORKS closed or quit, or closed work found again. Trigger words - solidworks, swx, sldprt, sldasm, slddrw, new solidworks part, model a bracket, open in solidworks, import step, export step, export glb, solidworks bom, mass properties, interference check, pack and go, custom properties, change a dimension, close solidworks, quit solidworks, recover my solidworks file, recovery folder.

192 lines · 1.9kwpreamblenamedescription (long)triggersuser-invocablestructureheadingsexample
sub-skill solidworks-memory view SKILL.md

How to keep SOLIDWORKS from running a Windows PC out of memory while an AI drives it - what the SOLIDWORKS Resource Monitor 'available committed memory is critically low' warning means, why SOLIDWORKS keeps memory after documents close, how to read the bridge's memory report before and during long runs, when and how to recycle a bridge-started session safely, and what never to close. Use before any long or repeated SOLIDWORKS run (test batteries, many new parts, batch exports, renders), whenever swx_status reports low commit memory, and whenever the user mentions the Resource Monitor warning, low memory, commit charge, SOLIDWORKS slowing down or a PC running out of memory. Trigger words - solidworks memory, resource monitor, committed memory critically low, commit charge, out of memory, low memory warning, solidworks slow, memory leak, recycle solidworks, long run, test battery, many parts.

144 lines · 1.7kwpreamblenamedescription (long)triggersuser-invocableparent linkstructureheadingsexample
sub-skill solidworks-sign-in view SKILL.md

How to get through the 3DEXPERIENCE ID login that SOLIDWORKS and SOLIDWORKS Visualize raise when the platform session has lapsed - where the window comes from, how to find it, the measured two-page flow, what to type with and what never to touch, and where the login comes from (never from this skill). Use when a SOLIDWORKS launch is waiting on a sign-in, when swx_status says waitingOn userSignIn, or when a License Manager notice says it failed to check a license. Trigger words - solidworks sign in, 3DEXPERIENCE login, sign me in, login window, License Manager failed to check license, session expired, Visualize login.

204 lines · 2.0kwpreamblenamedescription (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.