AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Synthcad Cad Authoring

skill-bencaunt-synthcad-synthcad-cad-authoring · by BenCaunt

Build, modify, and validate SynthCAD build123d CAD projects, including project-local tests and generated review artifacts.

No reviews yet
0 installs
8 views
0.0% view→install

Install

$ agentstack add skill-bencaunt-synthcad-synthcad-cad-authoring

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-bencaunt-synthcad-synthcad-cad-authoring)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
3mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Synthcad Cad Authoring? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

SynthCAD CAD Authoring

Use this skill when working in the SynthCAD repository on CAD projects, exports, inspection, project-local tests, or URDF handoff.

Operating Rules

  • Use millimeters for all CAD dimensions.
  • Discover the active project and target before editing. Use the build

registry or user request as the source of truth.

  • Prefer small parameterized changes in the target's existing source module.
  • Preserve real component interfaces first: hole patterns, shafts, registers,

fastener clearances, mounting faces, service access, cable/connector access, and other constraints documented by the current project.

  • Do not hand-edit generated STEP, STL, GLB, URDF, inspection, or BREP files.
  • Keep each project's source references, docs, tests, and generated artifacts

inside projects//.

  • Put project-specific tests under projects//tests/. Reserve

root tests/ for reusable framework, CLI, registry, and library behavior.

  • When creating a new project or build target, add or update tests for its

geometry invariants, critical component interfaces, source refs/docs metadata, and expected assembly interferences.

  • If a drawing or component constraint is incomplete, record the assumption in

the project's own docs/ directory.

Commands

Set these from the current repo and request:

uv run synthcad-build --list
PROJECT=
TARGET=
ASSEMBLY_TARGET=
URDF_TARGET=

Use the variables consistently:

uv run synthcad-build --project "$PROJECT"
uv run synthcad-probe --target "$TARGET" --children
uv run synthcad-inspect --target "$ASSEMBLY_TARGET"
uv run show-interference --target "$ASSEMBLY_TARGET"
uv run synthcad-report --project "$PROJECT"
test -z "$URDF_TARGET" || uv run synthcad-urdf --target "$URDF_TARGET"
uv run pytest
uv run pytest "projects/$PROJECT/tests"

Use synthcad-probe before writing throwaway geometry scripts. It reports target bounds, child labels, and inspection model structure quickly.

Done Criteria

A CAD change is done when:

  • the changed target imports and builds without errors;
  • relevant project-local tests are added/updated and pass;
  • exports regenerate for the affected project or target;
  • inspection artifacts are generated for the changed target or assembly;
  • unexpected interferences are fixed or documented as intentional; and
  • project-specific assumptions or validation notes are updated.

Reference

Open references/project-workflow.md for the generic project workflow and test expectations.

Robotics Robustness Extension

For robotics parts/assemblies, pair this skill with:

  • references/robotics-robustness-prompt.md for a reusable prompt add-on.
  • docs/robotics-design-guidelines.md for design guardrails and tooling roadmap.

When outputs include rotating shafts, bearing supports, or structural load paths, require explicit rationale and fail the task if support topology is unsafe or insufficiently specified.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.