sim-assembly-fea SKILL.md skillA
sim-assembly-fea from partcad/partcad is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add partcad/partcad/sim-assembly-fea@git:20261025.0dcd877Pins git:20261025.0dcd877 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- partcad/partcad
- Path
ai-agents/common/skills/sim-assembly-fea/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261025.0dcd877, committed Oct 25, 2026
- First version recorded
- Oct 20, 2026
- Size
- 15,232 bytes
- Repository stars
- 528
- License
- Apache-2.0
Turn what a simulation of an assembly measured into a stress analysis of one part in it - run the assembly's `simulate:` entry, read the forces and moments acting on the body the part is welded into at the end of the run (the "after" state), work out which of them load the part and where, and add the part a new named FEA scenario (an entry of its `fea:` section, beside any it already has) that applies them as forces with directions in its own frame (with its apparent gravity), then run that…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# pc:sim-assembly-fea Find out what a mechanism does to one of its parts, and analyse the part under it. `$ARGUMENTS` names three things: the **assembly**, the **simulation** (the name of an entry in its `simulate:`), and the **part** (a link path in the assembly, such as `lower/knee-worm-gear/gear`, or a part name such as `motion/worm_gear_28t` when only one placement of it is in the assembly). Ask for whichever is missing; `pc --no-ansi info -a <assembly>` prints the assembly's `simulate:` entries, and the result of a run lists its parts. What you produce is a new **FEA scenario** -- one named entry of the part's `fea:` section, which is a map of scenarios the way `simulate:` is a map of simulations -- whose every number came out of the simulation, a run of that scenario with its result, and a short account of how each load got from the simulation to the part. You add a scenario; you never replace the section. A part may already be analysed under other loads -- by hand, or from another simulation or another moment of this one -- and those scenarios are somebody's questions too. A rigid-body simulation knows what acts on each **body**, and a body is often …
Read the whole file at its exact version.
How to install
mdr add partcad/partcad/sim-assembly-fea@sha256:8340192ccf082210The line at the top of this page pins the label git:20261025.0dcd877, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_obskdfr4qn7353zm)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Oct 20, 2026 and Oct 25, 2026, about one every 6 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261025.0dcd877 latest | 2026-10-25 | 0dcd877 | 15,232 B | A | view · diff |
| git:20261020.730bc52 | 2026-10-20 | 730bc52 | 12,170 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (15232 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
partcad/partcad · 528 stars · license Apache-2.0 · pushed 2026-11-08 · branch devel
API
GET https://markdownregistry.com/api/v1/artifacts/art_obskdfr4qn7353zm GET https://markdownregistry.com/api/v1/resolve?ref=partcad/partcad/sim-assembly-fea GET https://markdownregistry.com/api/v1/blob/8340192ccf0822101eb0141197ff1957ccd112926dcd5e2c42069303f12456b4
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.