wzyn20051216/solidworks-automation-skill

SolidWorks Automation Skill – AI‑driven CAD automation

What it is

• A toolkit that lets large‑language‑model agents (e.g., Codex, Claude, Cursor) control the desktop version of SolidWorks (and some other CAD packages) through natural‑language commands.
• It ships as three interchangeable entry points:
  1. Skill – a tiny plug‑in that agents can import.
  2. MCP – a command‑line client for the Smithery MCP framework.
  3. CAD Studio – a Windows desktop app for managing projects, previewing results and delivering artifacts.
• All three share the same capability catalogue (capabilities.yaml) and the same execution core, so you only need to install one of them.

How it works

1. User writes a natural‑language request (e.g., “Create a M6×1 threaded hole”).
2. An LLM agent calls the Skill/MCP via a structured tool call.
3. The Execution Core translates the request into a sequence of SolidWorks COM or OCCT operations, runs them, and records a trace.
4. After the CAD software finishes, the core verifies the result (e.g., reads back the created geometry, checks dimensions) and produces evidence (files + verification logs).
5. If verification fails, a deterministic recovery decision is made and the task can be retried or handed back to the agent with a CAPABILITY_GAP response.

Key features

• Verification‑first: success of the tool call does not equal task success; every output is validated before being accepted.
• Deterministic reliability scenarios: 37 built‑in cases test normal execution, fault injection, backend fallback, and capability gaps. The current baseline reports 0 false completions.
• Broad CAD support:
  • Full SolidWorks native formats (SLDPRT, SLDDRW, SLDASM).
  • Open‑format export via OCCT (STEP, STL, IGES, BREP, OBJ, GLB, DXF, SVG, PDF, PNG).
• Capability matrix: each function is labeled verified, stable, pilot, or blocked in capabilities.yaml so agents know what is reliably available.
• Subskills: modular workflows for specific tasks (threaded holes, CNC fillet/chamfer, gear generation, etc.) that the root skill can invoke automatically.
• No extra runtime service: the execution core runs inside the same process that talks to SolidWorks; you don’t need to start a separate server.

Getting started

Entry point	Who it’s for	GUI needed?	Typical use
Skill	Agents that support skill import	No	Pure natural‑language driving of SolidWorks
MCP	Users of the Smithery MCP client (Codex, Claude, Cursor, Windsurf)	No	Automated tool‑calling from LLMs
CAD Studio	Engineers who want a visual project manager	Yes	Submit tasks, preview models, download PDFs

Install one of the three, then run the provided diagnostic script (python scripts/cad_doctor.py) to verify your SolidWorks environment.

Documentation & resources

• Quick‑start guide (Skill, MCP, CAD Studio) – in the README.
• Detailed architecture of the Execution Core – docs/architecture/execution-core.md.
• Reliability evaluation methodology – docs/architecture/v2-evaluation.md.
• Full list of capabilities and their status – capabilities.yaml.
• Subskill specifications – subskills/ and SUBSKILLS.md.
• Example projects covering modeling, assembly, drawing, motion, and FEA – examples/.

Roadmap

• Expand verified native SolidWorks capabilities.
• Improve capability routing and observability in CAD Studio.
• Add more community‑contributed subskills with automated testing.

License – MIT.

---

In short, SolidWorks Automation Skill is a production‑grade bridge that lets LLM agents reliably command real CAD software, with built‑in verification, deterministic error handling, and a clear capability catalog.