// Start or reuse CAD Viewer and return review links for explicit CAD, robot-description, and G-code files. Use when visually reviewing `.step`, `.stp`, `.glb`, `.stl`, `.3mf`, `.gcode`, `.dxf`, `.urdf`, `.srdf`, or `.sdf` files, especially when handed off from CAD, G-code, URDF, SRDF, or SDF generation skills.
Create, modify, inspect, and validate STEP-first build123d/Python CAD parts and assemblies. Use for natural-language CAD specs, STEP/STP generation or direct inspection, build123d source, build123d source-level joints, @cad references, geometry facts, measurements, mating deltas, CAD Viewer handoffs, snapshots, and secondary DXF/STL/3MF/native GLB outputs from CAD geometry.
SDFormat/SDF model and world generation, validation, and simulator handoff. Use for `.sdf` files, SDFormat XML, Python `gen_sdf()` sources, models, worlds, links, joints, poses, frames, inertials, visual/collision geometry, mesh URIs, sensors, lights, physics, plugins, includes, Gazebo, static SDF review, or simulator-specific metadata. Do not use for signed-distance-field geometry.
MoveIt2 SRDF generation, validation, and planning-semantics workflow. Use when creating, editing, regenerating, inspecting, or validating `.srdf` files, `gen_srdf()` sources, MoveIt planning groups, virtual joints, passive joints, end effectors, group states, disabled collisions, URDF-linked planning semantics, or SRDF handoff for live review. Use the URDF skill for robot structure, the SDF skill for simulator descriptions, and the cad-viewer skill for rendering, live review links, and optional MoveIt2 controls.
URDF robot description generation and default generation-time validation. Use when creating, editing, regenerating, inspecting, or debugging `.urdf` files, Python `gen_urdf()` sources, robot links, joints, limits, inertials, visual/collision geometry, mesh references, frame conventions, or generated robot-description artifacts. Use the SRDF skill for MoveIt2 semantic groups and IK/path-planning semantics; use the cad-viewer skill for local MoveIt2 server controls; use the CAD skill for STEP/STL/3MF/DXF/GLB outputs.
Dry-run, upload, and cautiously initiate local Bambu Lab print jobs from validated plain `.gcode`, using Bambu LAN FTPS/MQTT handoffs.
Generate, inspect, dry-run, and statically validate plain FDM `.gcode` from 3D mesh files by orchestrating real slicer CLIs. Use when Codex needs to slice `.stl`, `.obj`, unsliced `.3mf`, `.ply`, `.glb`, or `.gltf` into printer-profiled G-code, discover local slicer backends, inspect whether a mesh is slice-ready, or validate generated G-code before any printer-specific handoff.
| name | cad-viewer |
| description | Start or reuse CAD Viewer and return review links for explicit CAD, robot-description, and G-code files. Use when visually reviewing `.step`, `.stp`, `.glb`, `.stl`, `.3mf`, `.gcode`, `.dxf`, `.urdf`, `.srdf`, or `.sdf` files, especially when handed off from CAD, G-code, URDF, SRDF, or SDF generation skills. |
Provenance: maintained in earthtojake/text-to-cad. Use the installed local skill files as the runtime source of truth; the repository link is only for provenance and release review.
Use this skill to open existing or newly generated CAD, robot-description, DXF, or plain FDM G-code files in CAD Viewer and hand back live review links. The expected input is one or more explicit file paths.
Start or reuse one local CAD Viewer with npm run agent:start, then select
local files by URL. The launcher uses Vite dev mode when this skill's
scripts/viewer path is a development symlink, and the packaged dist/ server
for production skill installs. Every Viewer link returned from this skill MUST
include ?dir= with an absolute path. Set ?dir= to the workspace-local
artifact root that owns the model files and related sidecars, usually the
project models/ directory, such as /Users/name/project/models. This root
should be the shared directory containing STEP/STL/GLB/URDF/SRDF/SDF/G-code/DXF
files, not a relative path and not just the selected file's parent when a
broader model workspace root exists. The ?file= value must be relative to
?dir=; choose a ?dir= root that makes the relative ?file= stable and
readable. The agent:start launcher
owns port selection: it starts from its requested or default port candidate,
checks the local CAD Viewer server registry, probes candidate ports with
GET /__cad/server, reuses a compatible live Viewer when found, or starts a new
Viewer on the first free port. When git is available, the launcher passes a
single git value derived from the worktree git dir and branch; a live Viewer
with a different git value is treated as another worktree or branch and
skipped. If either side has no git value, git is not used as a port reuse
condition.
If you need to inspect a running server manually, GET /__cad/server returns
JSON with app: "cad-viewer", dynamicRoot: true, serverApiVersion >= 2,
viewerVersion, an optional git value, and the selected port. Treat a legacy
root-bound CAD Viewer without the dynamic-root fields as incompatible because
returned links must support absolute ?dir= values and relative ?file= values
inside that root.
Always start new local Viewer servers with --shutdown-after 12h so forgotten
review servers clean themselves up. Do not rely on a default shutdown; the
server stays alive until stopped unless this flag or VIEWER_SERVER_LIFETIME_MS
is set.
Do not manually choose or increment ports. Run agent:start, use the base URL
it prints, and append the requested absolute ?dir= plus a ?file= relative
to ?dir=. Do not start a separate Viewer just to change
directories; the same local server can scan a new absolute ?dir=.
Run from this skill directory:
npm --prefix scripts/viewer run agent:start -- --host 127.0.0.1 --shutdown-after 12h
Use the printed base URL and append query parameters:
http://127.0.0.1:<printed-port>/?dir=/absolute/workspace/models&file=path/to/model.step
Use the base URL printed by agent:start. If a non-Viewer process or another
worktree's Viewer occupies the candidate port, the launcher will continue to
the next port automatically. In sandboxed agent environments, local binding
failures such as EPERM or EACCES can be expected; rerun the same command
with the needed permission/escalation.
?dir=/?file= query only.?dir=<absolute-model-root> on every returned Viewer link.
This is mandatory for cad-viewer handoffs: do not omit it for convenience, do
not use a relative path, and do not rely on the Viewer's session-storage
?dir= fallback.?dir= as the absolute workspace folder that contains the model
artifacts, commonly <repo>/models or the consuming project's equivalent
model directory.file=<path> for each requested file, one URL per file. The file path
must be relative to ?dir=. For directory-only review links, include
?dir=<absolute-root> without file=.references/development.md when the user asks to modify, debug, or
iterate on CAD Viewer source.references/viewer-features.md when you need supported file types, Viewer controls, or file-specific feature details.references/moveit2-server.md only when the user specifically needs optional SRDF MoveIt2 IK or path-planning controls.