Menu

Individual skill

unrealmotion

0upvotes

Create silent motion-graphics explainers from a prompt through ImageGen references, actual Three.js reconstruction, causal motion and deterministic MP4 rendering. Use for process explainers, cutaways, reassembly, product films and kinetic typography; not for footage-only editing.

SKILL.md

Read pinned source

Source commit 12fc787dfb4d4c6e46ba441f6426c5f2c4112b72

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 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)
16
Repository last updated
Nov 4, 2026
License
MIT

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

# UnrealMotion

Deliver a playable MP4 and the scene source from the user's prompt. The active coding agent is the creative engine; the bundled scripts retrieve references, serve the scene, capture frames, and encode video. No separate language model, API key, or paid video service is needed. This is Three.js, not Unreal Engine.

Resolve `<skill>` to the directory containing this file; run package commands there. Use a new `<project>` directory for each production, preserving prior work. If dependencies are missing: `npm ci` and `npx playwright install chromium`. Check `node <skill>/scripts/unrealmotion.mjs doctor`. Node 22+, Python 3.10+, FFmpeg and ffprobe are required; Python packages are needed only to retrieve full dataset code.

## From prompt to film

1. Infer subject, action, intended message, language, duration, format, and realism from the request. **For explainers, read [imagegen-threejs.md](references/imagegen-threejs.md) and [explainers.md](references/explainers.md). Use ImageGen → real Three.js model → silent video**, starting with `--mode explainer`: default 60 seconds, 1080×1920, 30 fps. Keep the established simple pastel cutaway style unless the user explicitly changes it. The prompt determines the subject, model, story and motion recipe; a bundled demo is not default content. Short showcases retain 12 seconds, 1920×1080 at 60 fps. Honor requested formats and assets. Proceed with reasonable assumptions; no required template/approval questionnaire.
2. Read [art-direction.md](references/art-direction.md) and [motion-library.md](references/motion-library.md). Choose a scene foundation and motion profile, then author a compact `plan.json`: identity-defining geometry, material palette, shot timings, subject actions, camera trajectory, transitions, local assets and provenance. An adjective such as “realistic” needs concrete evidence: proportions, surface response, contact, coherent light, and motion.
3. Search the bundled **4,146-entry HF catalog**, using English subject/material/mechanism terms. Read [dataset.md](references/dataset.md) to retrieve 1–3 relevant code examples when structural detail would help. Inspect actual HTML/JS construction, not only titles. Cite scene ids in `plan.json`. Do not copy reasoning traces. The dataset is a reference corpus, not a trained or fine-tuned model.
   For industrial/object assets with limited storage, read [simready-imagegen.md](references/simready-imagegen.md): search the 2,677-entry NVIDIA metadata catalog and retrieve only a relevant budgeted thumbnail/license. This feeds ImageGen appearance references and original mesh reconstruction; never download the whole USD/texture corpus. For teardown/reassembly, also read [reassembly.md](references/reassembly.md).
4. Create the project. For an explainer, **generate the prompt-specific simple ImageGen reference, inspect it, specify named parts in `reconstruction.json`, and build actual Three.js volumes in `model.mjs`**. Save exact prompts/provenance in `asset-plan.json`. Author `storyboard.json` with the question, causal progression, per-beat action/copy, 3D camera and resolution. Retain one mesh hierarchy through cutaways, reassembly and operation. No raster-plane/cropped-image substitute. For showcases, author `scene.mjs` directly. The CLI is an authoring starter, not a semantic prompt interpreter; a changed title over an unrelated model is not completion.
5. Preview, scrub, run QA, and inspect representative frames at native resolution. Follow [quality.md](references/quality.md): check fidelity, mechanics/anatomy, materials, framing, copy, transitions and meaningful motion in the latter half. Correct failures and repeat the affected checks. Record a truthful `review.json`, tied to the source hash.