nexu-io/openmotion / skills/openmotion-template-to-video
openmotion-template-to-video
VerifiedBrowse, compare and recommend OpenMotion catalog templates with a visible library preview, or make a video from an existing editable template, project folder, ZIP or selected gallery source. Preserve agreed motion and content; resume existing work. Video-only references use openmotion-recreate; reusable template production uses openmotion-video-to-template.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 15.4 KB |
| agents/openai.yaml | config | 138 B |
| references/first-use.md | markdown | 3.4 KB |
| references/recipes.md | markdown | 5.3 KB |
| references/unchanged-export.md | markdown | 7.6 KB |
| scripts/delivery.mjs | script | 9.9 KB |
| scripts/playback.mjs | script | 7.4 KB |
references/unchanged-export.md
View on GitHub# Unchanged template file export
Use this branch when the user selects an editable catalog template, accepts its existing content/assets/timing/specification, and requests HTML/project files or MP4. Empty additional requirements mean the selected sample defaults. A new brand, supplied replacement material, copy edit, sound change or new output specification returns to the template edit flow. A request to browse/open only remains editor-only.
## Read once, then execute
This page is the complete unchanged-export procedure. Reuse current connection, workspace and prior operations. Read the selected template's instructions through `openmotion_get_template` when not already available. A known ID needs no catalogue listing. Load the [runtime transport rules](../../openmotion-production/references/production.md#tool-transport-and-workspace-readiness) only for an unknown/failed connection; retain the actual error and verify the expected data directory through a real project read. Read the engine authoring guide, creative review, material selection and edit references when the task actually needs authoring or a detected defect. Apply [shared verification scope](../../openmotion-production/references/verification.md#verification-scope); technical checks and normal-speed playback below remain required for a new MP4.
1. **Resolve once.** Read the expected workspace through the available OpenMotion connection and reconcile an existing project from this intent before any create retry. Create one independent copy using `projectType: "template"`, the exact template ID, accepted requirements and a stable requestId. Keep its projectId/sessionId; an unrelated previous sample is not this intent's project. Retain the source identity and output dimensions/fps/duration/audio policy.
2. **Pin the ready source.** Apply [shared source pinning](../../openmotion-production/references/native.md#pin-source-for-independent-deliverables) to this independent unchanged copy, including native preview normalization before the project read. Apply [shared delivery scope](../../openmotion-production/references/production.md#delivery-scope) when deciding whether presentation needs a work round; unchanged file delivery itself does not author content.
3. **Run independent delivery work together.** For requested MP4, call `openmotion_export_request` once with that revision/version and a stable requestId; use the template's actual audio policy. In parallel, package requested HTML with the helper below and request the same editor URL in the host. Both outputs follow the shared source-pinning and reconciliation rules.
4. **Bound presentation.** Reuse the actual editor tab. Follow the [shared handoff](../../openmotion-production/references/native.md#editable-preview-handoff), including observed visibility and a paused, stable zero-second preview. At most one failed host-presentation retry is useful; retain queued/hidden/unavailable status and the exact usable URL when still unobserved. Continue the independent file work and report this limitation separately. Opening a hidden tab or receiving a queued acknowledgment is not visible delivery. A user request to stay in the background takes precedence.
5. **When MP4 was requested, wait for the named export.** Use `openmotion_get_project({projectId, exportJobId})` with bounded polling and return only status changes to the model when a permitted deterministic client is available. Keep the registered MCP transport, workspace, permissions and tool restrictions; a shell HTTP call is not native MCP recovery. Read the completed job's automatic technical report once; keep its expected specification, version, revision and file hash. Existing complete verification on this exact file does not need a second FFmpeg decode. A failed/blocked job is not a delivered MP4; diagnose before any new request.
6. **When MP4 was requested, check the actual final file once.** Use a supported player or the bundled playback helper. Observe normal-speed full playback, seek to start/middle/near-end and replay; inspect the actual opening, main content and closing. The helper automates player operations and reports observable media facts, not perceived motion/sound quality. Listen when sound is part of the template and listening is available; otherwise mark that evidence unavailable. Preserve the original template's creative choices rather than launching a new storyboard/design comparison. A changed or broken result returns to the affected repair flow. A technically passed file alone is not a playback/creative pass.
7. **Deliver immediately after checks.** HTML/project-only requests finish after package and editor checks, without an export or MP4 playback task. Copy the completed MP4 only when requested, preserving its SHA-256; link the actual HTML entry plus its portable ZIP when requested. Keep one compact receipt with project/template/version/revision, job/file hash, automatic technical result, playback evidence and editor status. The helper writes the package receipt; append actual observed results instead of drafting several redundant reports. State any pending check/presentation accurately. No unrelated cleanup or publication belongs on the delivery path.
## Deterministic host helpers
The helpers operate on an explicitly returned project/file and write outside the managed project. They do not create projects, edit source, render, submit paid jobs or bypass MCP guards. Full/source installations use their owning runtime; thin adapters pass their `scope.json.runtimeRoot` as `--runtime-root` for packaging. Resolve actual absolute paths from the installation rather than guessing a checkout.
```sh
node /absolute/skill/scripts/delivery.mjs package --project-json /absolute/project-detail.json --output /absolute/new-delivery-directory --runtime-root /absolute/runtime
node /absolute/skill/scripts/playback.mjs --video /absolute/final.mp4 --report /absolute/playback.json
```
Save the actual `openmotion_get_project` structured result as project-detail.json. Packaging checks source hashes before/after copying, rejects unpinned source files, preserves local dependencies (including vendored `dist` trees the page loads and quoted CSS `@import` targets)/licenses/native manifests, excludes render outputs and caches, and verifies the ZIP. Keep the error and pinned source identity after a failed package; the helper removes only its new partial output, while existing destinations stay untouched. The playback server prints its actual loopback URL, supports byte ranges and serves only the selected file/internal diagnostic page. Open that URL through the supported browser, start its real playback-check control, observe the picture and read its completion summary. Stop only the helper server you started after closing its diagnostic tab; keep the delivered editor and files.
## Reuse and timing
Reuse an existing successful export only when it is bound to the same project content version/revision, output specification, complete asset/dependency identity and actual file hash. An arbitrary template preview or matching template ID is insufficient. If this provenance is absent, render once. An explicit fresh-render benchmark always requests a new export and records cache/environment state.
For timing comparisons, start when executing the same creation brief, before guidance/connection work for that run. End at actual final delivery; also record files/checks-ready separately. Exclude Skill development/installation from the replay metric and report that exclusion, warm-context/runtime caches, version differences and the number of trials. One faster replay is a case result, not proof of a stable speedup. Keep the technical/normal-speed playback requirements comparable with the baseline.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |