solidworks-automation-skill
SolidWorks Automation Skill connects coding agents to desktop CAD. It ships three peer entry points that share one capability registry (`capabilities.yaml`): an agent Skill, an MCP server with about 60 tools, and a Windows desktop app called CAD Studio. You pick one; no separate runtime service has to be started.
Its main idea is that a tool returning success is not the same as the task being done. An internal Execution Core verifies results, decides how to recover from backend failures and writes a structured trace. When no existing tool covers a request it returns a `CAPABILITY_GAP` instead of improvising, and it does not run unknown code from the internet on its own.
Each capability carries a status in the registry: verified, stable, pilot or blocked. Threaded holes and open-format export are marked verified, while gears, motion studies, FEA and mold work are still pilot and need human review. The README lists SolidWorks 2024/2026 and AutoCAD 2024 as the real-machine baselines; without SolidWorks it can still write STEP, STL, GLB and similar files through OCCT, but native SLDPRT/SLDASM/SLDDRW need a licensed SolidWorks.
Features
Why choose it
Trade-offs
Maintenance check
- Last commit
- 2026-10-17
- Commits, last 90 days
- 100+
- Releases, last 90 days
- 2
- Latest release
- v2.0.0 (2026-10-05)
- Open issues
- 3
- Recent issues with at least one comment
- 16/16
Oldest week on the left; the latest four weeks are orange. Source: GitHub commit activity.
Status rule: archived on GitHub = Archived; last commit within 90 days = Active; 91 to 365 days = Slowing; older = Stale. All figures come from the GitHub API on the date shown.
Most discussed open issues
- #3 有没有考虑做一个CLI，让效率更快1 comments · 2026-05-30
- #2 codex使用1 comments · 2026-05-30
- #1 使用时出现了图片中的问题1 comments · 2026-05-19
Issue titles are quoted from GitHub. Open the link to check whether a problem still applies to the version you use.
Compatibility
Quick start
Use cases
Alternatives
Comments
No comments yet. Be the first!