RSS
Tools

teardown: a Claude Code skill that builds take-apart 3D machine simulators as one offline HTML page

teardown (elvarofficial/teardown) is a free, MIT-licensed Claude Code skill that builds a machine you ask about as one offline 3D HTML page with live gauges, cutaways and a self-running tour, and can record that tour to a 60 fps video.

Close-up of exposed mechanical engine parts illustrating the teardown skill for 3D machine simulations
Photo by Garett Mizunaka on Unsplash

teardown (GitHub: elvarofficial/teardown) is a Claude Code skill for the question "how does this machine work?". You describe a machine, and Claude builds it as a single offline HTML page: the 3D model runs in the middle, panels show numbers from the same model that moves the parts, buttons cut open each subsystem, and an idle page tours itself. The same code can record that tour to a 60 fps video with a generated soundtrack. Created on October 30, 2026 and MIT-licensed, it had 3,559 stars and 530 forks on November 16; skills.sh listed about 3,700 installs.

Quick facts

  • What it is: one skill (SKILL.md) plus a JavaScript kit and three finished example machines: a cross-plane V8, the main landing gear of a Cessna 337, and a 20-leg Theo Jansen Strandbeest.
  • Requirements: Node.js 20 or newer for the pages; ffmpeg for video; Python 3 (standard library only) for the sound.
  • Main dependencies (package.json): three.js 0.186.1 and two fonts, inlined into each page; esbuild 0.28.1; Playwright 1.58.2.
  • Output: one self-contained HTML file per machine; SKILL.md puts the V8 page at about 800 KB, and the build script says each page opens from file:// and works offline.
  • Licence and cost: MIT, free. No releases or tags; package.json says version 1.0.0.
  • Origin: the README credits whaleyxbt/claude-motion (MIT) for the runtime, frame capture, sound engine and review rules. Recorded sound samples are CC0 from Freesound.
  • Activity (November 16, 2026): 2 commits, last push October 31; 6 open issues listed (#4, #5 and #8 to #11).

How to install

The README installs it with the skills CLI, then sets up dependencies once in the installed folder:

npx skills add elvarofficial/teardown -g -a claude-code

# then, once, inside the installed skill folder:
npm install && npx playwright install chromium

The second step downloads Playwright's Chromium, used to render video frames and review stills. Builds land in teardown-out in the directory you run from; FFMPEG, PYTHON and CHROMIUM variables point at other binaries.

First run

The quickest check that your setup works is to build one of the bundled machines before asking Claude for a new one:

node sims/build.mjs v8-live          # teardown-out/dist/v8-live.html
node sims/build.mjs cessna-live
node sims/build.mjs strandbeest-live

Open the HTML file and press the buttons. Then ask Claude Code in plain words; the README's own examples include a four-stroke motorcycle engine, a mechanical watch, and a hydraulic excavator arm with a 20-second video. The skill tells Claude to copy the closest example, build the new machine, and read rendered still frames before calling it finished. Neither the README nor SKILL.md says how long a new machine takes or what it costs in tokens; expect several build-and-review rounds.

Before you judge results: the robotic bee, scorpion and octopus in the README animations are not in the repository. The October 31 commit says they were built with the same kit; only the V8, Cessna and Strandbeest ship as source.

What stands out

  • One input moves everything: crank angle for the V8, a 0-to-1 stroke for the landing gear, wind for the Strandbeest. Nothing is keyframed by hand, so page, film and soundtrack cannot drift apart.
  • Real dimensions, checked by hand. Claude must get bore, stroke, tooth counts or link lengths first and verify one number manually. Example: in the Cessna gear, a 32-tooth pinion at module 4 mm has a 128 mm pitch diameter, and half its circumference is the 201 mm rack stroke.
  • The page and the film are the same code. A live page hands control to the visitor on any click, drag, wheel or key and resumes its tour after 25 seconds of quiet. Capture steps the page's render(t) frame by frame in headless Chromium and pipes screenshots to ffmpeg, so render(t) must be pure: no randomness, no clock.
  • A review loop for a model that cannot watch video. SKILL.md says Claude can look at frames, not watch the video, so capture.mjs builds a sheet with one tile per timeline beat, and Claude checks each (parts touch, nothing passes through anything, labels never cover their part) before rebuilding. A final sheet comes from the encoded mp4.
  • Sound from the timeline. The sfx package synthesises the score in pure Python from the same timeline.json as the film and masters it to -14 LUFS automatically.

How it was built with Claude

Both commits on main are by elvarofficial and both carry a Co-Authored-By line for Claude Opus 5.5: the October 30 initial release with the three example machines, and the October 31 README change that swapped in the robot creature previews. The repository has no CLAUDE.md, AGENTS.md or design notes, so there is no record of how the work was split, or of how much came unchanged from claude-motion.

Try it with your AI. With teardown installed, this prompt makes Claude follow the skill's own rules for accuracy: real dimensions first, one input, a hand check, and frame review before it says done.

Use the teardown skill to build a simulator of [machine, e.g. a single-cylinder 4-stroke
engine].

First check: confirm the skill folder has node_modules. If it does not, show me the
setup command (npm install && npx playwright install chromium) and wait for my yes. Then
run node sims/build.mjs v8-live; if it fails, stop and show me the error. Do not install
anything else without asking.

1. Reference: I will give you [a photo / a manual cutaway / a link]. If I have not, ask
   me for one; do not invent the machine from this sentence.
2. Before writing code, list the real dimensions you will use (for example bore, stroke,
   tooth counts, link lengths) with where each came from. Mark any you guessed. Show me
   the list and wait for my confirmation.
3. Pick the one input that drives every pose and every readout. Check one derived number
   by hand and show the arithmetic.
4. Copy the closest example (v8, cessna or strandbeest) and build the live page with
   sims/build.mjs.
5. Review: build the film variant and render a stills sheet with capture.mjs --stills
   beats (no mp4 needed), read every tile against the SKILL.md checklist, fix and repeat
   until a full pass finds nothing.
6. Only render an mp4 or a score if I ask; ffmpeg must already be on PATH.
7. Do not delete or overwrite anything outside teardown-out. If you run sheet.mjs, keep
   --name a plain folder name and show me the command before running it.

Finish with: the HTML path, the dimension list with sources, what you checked by hand,
and anything you know is still wrong.

Known limits

  • Accuracy depends on what you give it. SKILL.md's first rule says machines invented from a sentence come out generic every time; a real one is rebuilt closely only with a reference to match. Nothing in the kit verifies physics beyond one hand-checked number and Claude's reading of still frames, so treat the result as an explainer, not an engineering model.
  • Results can be far below the demos. Issue #9 reports that a prompt for a mechanical hummingbird produced a rough model without the detail of the README animations; the replies suggest iterating on the prompt over several rounds.
  • Security: issue #5 reports that sheet.mjs passes --name straight into a recursive delete, so a mistaken or prompt-injected value could wipe a folder outside the output; it says this is what Socket flags on skills.sh, where the listing shows a Socket warning. Issue #11 reports that built pages accept a ?config= URL parameter whose story captions are written into the page unescaped, so a crafted link can run script if you host a built page on a website. Both include suggested fixes; as of November 16 neither had been committed, since main still held only the two original commits. The #11 reporter says the affected file is identical in claude-motion.
  • macOS video capture: issue #4 reports that headless Chromium gets no WebGL context on macOS, so capture.mjs times out; the reporter's fix, tested on an Apple M5, adds --use-angle=metal in paths.mjs.
  • Smaller bugs: issue #10 says sfx/synth.py hardcodes a Windows ffmpeg path, so the recorded-sample function fails elsewhere (the bundled scores do not use it); issue #8 reports that, with ffmpeg 9.0.2 on Windows, videos come out as full-range yuvj420p rather than the yuv420p SKILL.md promises.
  • Claude Code first. Install targets claude-code; issue #7 asked whether Codex or other agents can use it and was closed with no reply in the thread.

Problems and feedback

Use the repository's GitHub issues. The reporters on #4 and #10 say pull requests are turned off, and #8 says outside pull requests are not accepted, so fixes are posted as diffs or fork commits inside the issues; check #4, #5, #8, #10 and #11 before filing, since their patches may already solve your problem. As of November 16 no issue thread contained a comment from elvarofficial, and the repository had no CONTRIBUTING or security policy file.

FAQ

Does teardown work with Codex or other agents? The README and install command target Claude Code only. Issue #7 asked about Codex and was closed with no answer in the thread.

What do I need installed? Node.js 20 or newer, plus the npm packages and Playwright's Chromium from the one-time setup. ffmpeg is needed only for video, and Python 3 with its standard library only for the sound.

Does it work on a Mac? Issue #4 reports that video capture times out on macOS because headless Chromium gets no WebGL context, and posts a one-line fix for paths.mjs; it was still open on November 16.

Is it free? Yes, MIT-licensed; the licence names both elvarofficial and whaleyxbt, author of claude-motion.

Source: GitHub: elvarofficial/teardown, teardown README, teardown SKILL.md, teardown package.json, teardown paths.mjs, teardown sims/build.mjs, teardown commit history, teardown issues, whaleyxbt/claude-motion (upstream kit), skills.sh listing for teardown

This story first appeared in the claudefox daily briefing for November 16, 2026.