agentleFS
darellchua2darellchua2/civiltekk-opencode-claude-skills/skills/cad-specialist-skill/SKILL.md

cad-specialist-skill

Skill7 starsChanged 58 days agoApache-2.0View on GitHub

CAD, robotics, and hardware router — one entry point for parametric CAD, STEP/STL/3MF/GLB parts, DXF drawings, drawing redraw, URDF/SRDF/SDF robot descriptions (Gazebo, MoveIt), G-code slicing, 3D printing, SendCutSend preflight, Civil 3D, Autodesk APS, Open3D point clouds, and part catalogs. Routes each task to the right specialist route.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No invented printer profiles (gcode route).

    line 85

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

CAD Specialist Router

One entry point for CAD, robotics, and hardware tasks. Identify the task, run only the matched route's file, and follow it. Heavy tooling lives in installable sibling skills — never absorbed here.

Provenance: routes consolidated from the former cad-* skill family (2026-10, #679); per-route provenance lines live in the route files.

Routes (load exactly one)

TaskRouteReadSkip-when
URDF robot description (.urdf)urdfreferences/routes/urdf.mdMoveIt semantics → srdf
MoveIt planning semantics (.srdf)srdfreferences/routes/srdf.mdURDF structure → urdf
Gazebo SDFormat model/world (.sdf)sdfreferences/routes/sdf.mdsigned-distance-field geometry → sibling cad-generation
Slice meshes to G-code / validate .gcodegcodereferences/routes/gcode.mdBambu upload/start → bambu
Bambu Lab LAN print handoffbambureferences/routes/bambu.mdslicing itself → gcode
SendCutSend upload preflight (DXF/STEP)sendcutsendreferences/routes/sendcutsend.mdgeometry generation → sibling cad-generation
step.parts catalog search/downloadstep-partsreferences/routes/step-parts.mdcustom geometry → sibling cad-generation
Civil 3D corridors, pipes, grading, surveycivil3dreferences/routes/civil3d.mdAPS cloud APIs → aps
Autodesk APS/Forge REST + Revit/Fusion/AutoCAD add-insapsreferences/routes/aps.mddesktop Civil 3D design → civil3d
Open3D point clouds, meshes, reconstructionopen3dreferences/routes/open3d.mdCAD authoring → sibling cad-generation

Route files open with their own Load when / Skip when lines. Route detail dirs (references/routes/<id>/) load on demand when the route file names them — never preload.

Sibling skills (install-if-missing)

Heavy tooling stays out of this skill. When a task matches a sibling row and the skill is not installed (check the user's skill list), offer:

npx github:darellchua2/civiltekk-opencode-claude-skills add <skill>
TaskSibling skill
Parametric CAD parts, STEP/STL/3MF/GLB outputcad-generation-skill
2D DXF drawings from Python ezdxf sourcescad-dxf-skill
Drawing redraw (DWG/DXF/PDF/image source)cad-redraw-skill
Implicit CAD (.implicit.js / .mjs)cad-implicit-skill
Browser preview / review links for artifactscad-viewer-skill

Contract: dry-run first, show the resolved install set, install only with user consent (install-assistant-skill conventions). Never auto-install. On decline or install failure, report the capability as unavailable — do not improvise the tooling.

Shared spine (all routes)

  • gen_urdf() / gen_srdf() / gen_sdf() Python sources are the source of truth; generated XML is an artifact. Edit the generator, regenerate explicit targets only.
  • python in examples is an interpreter placeholder — substitute python3, a project virtualenv, or the configured interpreter.
  • Derive spatial data (frames, poses, axes, units, masses) from source data or explicit documented assumptions — never from visual impression.
  • Validate every generated artifact at generation time; run consumer smoke tests when available.
  • Viewer handoff: after creating or modifying a viewable artifact, hand the file path(s) to cad-viewer-skill (install-if-missing). Report when unavailable — never silently omit.
  • Report assumptions, skipped checks, and unresolved risks; route files define their own report shapes (the sdf route carries the canonical example).

Hard rules

  • No invented printer profiles (gcode route); no scraping — hosted APIs only (step-parts, sendcutsend fetch official sources directly).
  • Printer starts require explicit --execute --confirm-start-print; the bambu route owns the full safety rules — read it before any live printer action.
  • Scripts run from this skill's directory: scripts/<tool> as each route file documents; one merged requirements.txt at the skill root.
  • Each route file owns its deep detail; this router never restates it.

Gates

  • Zero-preload: only the matched route file (+ its on-demand detail dir) enters context.
  • Report shape complete before declaring done: outputs, checks run/skipped, assumptions, risks.
  • Any sibling-dependent capability goes through the install-if-missing contract above.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.