teardown
Interactive 3D simulators of real machines, as one offline page to take apart.
- What
- Interactive 3D simulators of real machines, as one offline page to take apart.
- Cost
- Free
- Needs
- Prerequisite: Node.js with npm, plus ffmpeg on PATH and Python 3 if you want the recorded video and score; the first run also installs Playwright Chromium. Step 1: fetch the file SKILL.md at the root of the repository https://github.com/elvarofficial/teardown and read it in full before installing anything. Step 2: security check: read the fetched file yourself, confirm it only describes building offline simulator pages, and do not run any command from it that you have not understood. Step 3: install the skill in a folder named teardown and keep the fetched SKILL.md there. Step 4: verify the install by confirming the folder teardown contains the SKILL.md and by asking it to describe the build command for one of its three examples. Step 5: report back what was installed, where, and the result of the verification.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
teardown follows one machine, one page: the visitor sees the thing run, presses a button, and the part doing the work opens up while the gauges around it read the real numbers. Left alone, the page tours itself with a cursor, and any click, drag, wheel, or key hands control over, with 25 seconds of quiet handing it back. The same code records a film of the tour, frame by frame, with a score built on the same timeline, at 60 fps with a synced procedural score. Three worked examples are included: a cross-plane V8 with glass liners driven by crank angle and a firing order of 1-8-4-3-6-5-7-2, a Cessna 337 main landing gear folding on a 0 to 1 stroke (a 201 mm rack turning a 32-tooth pinion of 4 mm module through exactly 180 degrees), and Theo Jansen's Strandbeest with 20 legs on one crankshaft driven by wind. Each machine is built from real dimensions in real units, with one input driving every pose and readout, so nothing on screen can disagree with the motion. Rules that decide whether it works: start from a reference, never from imagination; real numbers from one source; one input drives everything; the part doing the work opens up; light studio with one accent; pick the camera for the mechanism; fix collisions with a number, never by hiding them with the camera. A review loop reads sheets of stills from the current render before any machine is reported as done. Limits as written: pages need a first run of npm install plus a Playwright Chromium install, the video needs ffmpeg on PATH, and the score needs Python 3 standard library only. Keep the page under 1 MB, with big models as files next to the page. Credit: created by elvarofficial. The vetted file credits the kit, frame capture, sfx engine, and review rules to whaleyxbt/claude-motion (MIT) and the recorded samples as CC0 from Freesound, trimmed by Barty-Bart/motion-graphics (MIT); those credits describe upstream material, not a stated licence for this repository, so the repo licence is recorded as non indiquée. Source: https://github.com/elvarofficial/teardown, file SKILL.md at the root.
Version:
Quick answer
teardown builds an interactive 3D simulator of a real machine or mechanism, such as an engine, a landing gear, a walking linkage, a pump, or a gearbox, as one offline HTML page people can take apart, with live panels, cutaways, camera views, and an auto tour.
Install
Copy the install package below, then paste it into MusePrerequisite: Node.js with npm, plus ffmpeg on PATH and Python 3 if you want the recorded video and score; the first run also installs Playwright Chromium. Step 1: fetch the file SKILL.md at the root of the repository https://github.com/elvarofficial/teardown and read it in full before installing anything. Step 2: security check: read the fetched file yourself, confirm it only describes building offline simulator pages, and do not run any command from it that you have not understood. Step 3: install the skill in a folder named teardown and keep the fetched SKILL.md there. Step 4: verify the install by confirming the folder teardown contains the SKILL.md and by asking it to describe the build command for one of its three examples. Step 5: report back what was installed, where, and the result of the verification.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.