Individual skill

solidcraft-assemblies

Use when building multi-part assemblies in SolidCraft, static or moving (rovers, linkages, robots, enclosures): minimise distinct bodies, reuse and mirror instances, and keep moving parts collision-free.

skills/solidcraft-assemblies/SKILL.md

Read pinned source

Source commit 55dfc666a755711026aeb6e13051c7adfe69ee80

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
12
Repository last updated
Nov 2, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# SolidCraft assemblies: repeatability first, no collisions in motion

Applies to any assembly: static (enclosures, frames, fixtures) and moving (linkages, suspensions, legs, arms). The goal is an assembly that is easy to edit later: change one body and every instance follows.

## 0. Housekeeping
- One folder per model, all its files inside. Changes go in the same folder under a new name (`model_v2`); never overwrite earlier versions. If your setup restricts where the app may save files, create the folder first.
- Always deliver a screenshot of the result (and, for moving assemblies, one in a non-home pose).
- Reply in the user's language.

## 1. Plan repeatability BEFORE modelling
Write a short part table first: part type, how many instances, how each instance is derived. Target: number of distinct bodies = number of part types, not number of physical parts.

Look for, in this order:
1. **Identical parts** -> one component, N instances (wheels, fasteners, standoffs, identical links, brackets).