Maintainer of this skill?
by capskov
AutoCAD automation bridge for AI agents via MCP and CLI, using a native .NET API with drawing identity checks, bounded operations, and write/save verification.
# Add to your Claude Code skills
git clone https://github.com/capskov/cad-agent-foundationGuides for using ai agents skills like cad-agent-foundation.
See how cad-agent-foundation compares with popular alternatives.
cad-agent-foundation is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by capskov. AutoCAD automation bridge for AI agents via MCP and CLI, using a native .NET API with drawing identity checks, bounded operations, and write/save verification. It has 0 GitHub stars.
cad-agent-foundation's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/capskov/cad-agent-foundation" and add it to your Claude Code skills directory (see the Installation section above).
cad-agent-foundation is primarily written in Python. It is open-source under capskov on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh cad-agent-foundation against similar tools.
No comments yet. Be the first to share your thoughts!
Available after the catalog security scan passes.
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.
Public source preview v1.1.0-rc.1 (bounded native operations and Windows runtime preview). Source, documentation and a manifest-bearing Windows runtime ZIP are provided in this preview. Build prerequisites and limits. The accepted local runtime v1.0.0-local is a separate baseline. Companion Skill previews are published independently: callout v0.3.0-rc.1 and distress v0.1.0-rc.1.
简体中文 · Quick start · Capabilities · Compatibility
AutoCAD automation bridge for AI agents via MCP and CLI, using a native .NET API.
AI agents can inspect and operate a live AutoCAD drawing through structured native tools for bounded 2D geometry, text, hatches and callouts. The bridge uses MCP (Model Context Protocol) and CLI; drawing identity checks and write/save verification govern the supported operations.
CAD Agent Foundation gives CAD agents a bounded execution contract: explicitly bind a drawing, persist request ownership and execution state, inspect the original request after an uncertain reply, and verify tracked object facts after writes and saves. The current implementation integrates these mechanisms into a modified, pinned Bimwright DWG MCP host.
This Windows/AutoCAD bridge is maintained by capskov. The current preview is v1.1.0-rc.1, with an independently built runtime ZIP and scoped native evidence. The accepted v1.0.0-local baseline is retained; compatibility with every AutoCAD update is not claimed.
The project grew out of road and civil-engineering CAD work: creating boundaries, fills, quantities and linked callouts, then revising and saving them over a long agent session. A useful drawing command is only part of that workflow. The agent also needs to know which drawing it owns, whether a modification has already happened, what remains unverified, and whether another attempt would duplicate it.
The design focuses on those decisions. Durable records, drawing identity and native readback add overhead; no comparative speed, token-cost or productivity advantage has been established. Engineering judgment and domain-specific layout rules remain in separate Skills.
Download v1.1.0-rc.1 runtime, verify SHA256SUMS.txt and extract the complete folder. Requires licensed compatible Windows x64 AutoCAD 2026, .NET 8 Desktop Runtime and Python 3.11+. No Autodesk assemblies or SHX fonts are redistributed. Installation · 25-operation catalog · New validation.
New in this preview: installed-font text styles, dimension styles, native linear/aligned/radius/diameter DIMENSION, layer state management, guarded closed-boundary/hatch continuation, linked callout geometry/format, and same-drawing rotate/scale/copy of supported complete groups. It preserves original-request reconciliation and drawing/object protection.
Maturity: the bounded local runtime has native acceptance evidence; The release provides a runtime ZIP with dependency licenses, file hashes and plugin MVID; prerequisites remain separately installed. Support follows the actually exposed profile.
| Category | Current capabilities | Status / limits |
|---|---|---|
| Basic drawing | New layer, line, circle, 2D polyline and associative hatch on an earlier new boundary | Specified local workflows verified; not arbitrary editing/all hatch cases. |
| Text and callouts | Single-line DBText, multiline MText, ordinary LEADER/MText/yellow filled-dot group | Creation verified; complete domain styles/placement belong to Skill. |
| Edits / object management | Digest-guarded linked-text update and complete callout-group move/archive | Specified group workflow verified; not every entity branch individually tested. |
| Execution / delivery | Drawing binding, original-request queries, duplication guards and whole-document save/disk readback | Local workflows verified; no automatic unknown-write replay/unlock. |
| Reads / helpers | Entity properties/digests, layer list, filtered paging and static Lisp inspection | Entity readback verified; some other implemented routes lack current-version individual end-to-end proof. |
| Additional bounded operations | Four native DIMENSION types, named matching styles, layer states, closed-boundary/callout updates, rotate/scale/copy | See the 25-operation catalog for exact guards and scoped native evidence. |
| Not exposed | MLEADER, shared-style overwrite, arbitrary object editing, complex Boolean/holes, layout/plot/xref edits | No blanket coverage of every native object or upstream command. |
Full interfaces, invocation and per-item verification status. Foundation supplies reusable native operations, execution constraints, status and object management. Independently maintained Skills supply domain rules, style parameters, placement algorithms and workflows through actual supported Foundation interfaces. Missing native/backend compatibility is not supplied merely by installing a Skill.
Bind the intended drawing and verify process/session/plugin identity. Persist a stable request before submission; after an uncertain reply, query that original request. Existing edits need fresh native digests and complete associations. Confirm effects, independent readback and fence release separately; save covers the whole working drawing. See architecture and versioned interface catalog.
| Task | Required components | Versions and limits |
|---|---|---|
| Supported basic CAD operations | cad-agent-foundation only |
Local baseline v1.0.0-local; public source preview v1.1.0-rc.1, with a reviewed runtime ZIP; prerequisites are separate. Bounded 2D operations; current writes require metres; recorded Windows/AutoCAD 2026 host only. Neither Skill is required. |
| This project's callout style and placement | Foundation + cad-callout-pair-layout |
Public callout Skill v0.3.0-rc.1 (existing rules v0.3). Metre-based road defaults; Native style/pose interfaces and a bounded synthetic unchanged-Skill integration are verified in v1.1; full real-project/background coverage remains per task. Check backend coverage before writing. |
| This project's distress/demolition workflow | Foundation + cad-distress-annotation + cad-callout-pair-layout |
Public distress rules preview v0.1.0-rc.1. Requires engineering evidence, classifications and the callout rules; full workflow needs capabilities outside the current Foundation profile and is not certified on these three components alone. |
The two Skills are optional for basic operations. Their rules are not built into Foundation; installing them does not add missing native operations. Foundation source and both independent Skill previews are public. Installation entries, versions and Agent checks.
The commands below use the extracted runtime ZIP. Source checkout alone requires build/packaging first.
foundation.cmd install --workspace "C:\CAD-work\demo01"
foundation.cmd start --workspace "C:\CAD-work\demo01" --source "C:\drawings\input.dwg" --write
foundation.cmd doctor --workspace "C:\CAD-work\demo01"
foundation.cmd apply --workspace "C:\CAD-work\demo01" --plan "plan.json"
foundation.cmd save --workspace "C:\CAD-work\demo01" --handles RETURNED_HANDLES
foundation.cmd stop --workspace "C:\CAD-work\demo01"
Omit --write for a read-only session. start creates a working copy; it does not overwrite the source drawing. Save affects the entire working drawing, including other unsaved edits in that instance. Read the quick start for request handling and a small synthetic plan.
The local release was checked on two different drawing sources, with different coordinates and handles. Each workflow created ten new objects, read them independently, updated linked text, moved the complete callout group, archived it, saved and closed the drawing. Fresh CAD sessions then read the saved objects with matching native digests. The CLI/MCP entry and local package extraction/installation were also checked.
These are bounded workflow results on a recorded Windows AutoCAD 2026 environment. They do not prove universal drawing correctness, production-wide reliability, compatibility with every patch, or a general CAD engineering agent. The validation summary separates native evidence from offline tests and records unresolved historical outcomes honestly.
Plans write bounded 2D model-space geometry. Coordinates, lengths and annotation sizes are expressed in drawing units. WCS is the CAD coordinate reference; it does not imply metres or a map projection. Foundation performs no projection or unit conversion.
The current write interface is restricted to metres: plans require units: metres, and the drawing must use metres or explicitly metre-based unitless coordinates. Millimetres and other units are not enabled or validated. This implementation boundary does not limit the intended foundation to road work.
This release provides four native dimension primitives and bounded closed-boundary/single-hatch updates. It does not provide MLeader, general old-hatch repair/Boolean/holes, arbitrary polyline properties, cross-drawing copy, proxy-object semantics, layout/plotting, engineering decisions or automatic recovery/unlocking of uncertain writes. A committed operation cannot be assumed rolled back because a later verification failed.
The `.N