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.
OpenMotion Template to Video
Scope and shared execution
For an accepted onboarding recommendation or submitted recommendation-card brief, read first-run execution and recovery before choosing the delivery branch below.
For unchanged HTML/project or MP4 delivery from a selected catalog template, follow unchanged catalog file export. For a supplied folder or ZIP, go directly to the portable project. Opening an unchanged template without requesting files uses the editor-only flow below.
Turn the selected editable template into the requested draft, editable project or finished video, preserving its agreed structure, motion and style. This is the implemented template route, including direct Skill selection. Read shared context once and apply only dependencies needed by this scope; reuse complete bodies and completed operations. Continue here without returning to production/start. MCP-only clients use resources/read openmotion://workflow/template/start, which returns this same file with status: "ready".
Changes to existing content use the shared edit workflow, including required related changes and preserved content. Missing instructions and target sources must finish returning to the model before a later call applies a template, imports, writes or exports. Entering this Skill again does not create another copy, apply the template again or repeat a completed export.
When selecting, obtaining or replacing assets, read the shared material policy, applying its generation timing ladder, replacement rules and cross-shot consistency while preserving the template's agreed structure, motion and content constraints. A generated or replacement asset takes the planned asset's place; keep the accepted motion, holds and cuts and do not add movement or re-cut unless the user asks. An unchanged preview handoff does not trigger asset acquisition.
Browse or recommend catalog templates
For library discovery rather than creation, follow browsing and recommendations. Open the library in this turn and complete its host handoff unless the user requested text-only/no opening. Give grounded candidates without creating a project, acquiring production assets or restarting creative intake. An already selected template plus an explicit creation request continues below directly.
When an adaptation needs a new editorial outline, read the optional template recipes. Keep an accepted template's structure unless the request changes it; unchanged delivery and local edits do not load recipes.
Open the supplied project
A template is a complete native HyperFrames project, not necessarily a catalog entry. For a supplied folder or ZIP, inspect/unpack it and make a working copy when editing or rendering is needed; resume that copy on later turns. Read index.html, native configuration and TEMPLATE.md (older templates may have EDITING.md/REPLICA.md instead) for changes or a fresh render. Preserve source, assets and hidden Studio manifests. Do not require template.json, a local template ID or catalog registration.
For an unchanged MP4 request from a supplied folder or ZIP, use the packaged preview when it decodes, belongs to that source and meets the requested specification. Deliver its exact bytes. If the preview is missing, stale, unreadable, mismatched, or the user requests a fresh render, render the independent source once with the pinned CLI below and verify that result. Opening an unchanged portable project uses the editor handoff for the supplied source.
If the user selected a gallery/catalog item instead, read its exact source/guide and ID, then follow catalog capabilities. Bundled projects use openmotion_create_project with projectType=template, templateId, requestId, title and requirements only when the selected project has not already been created. Only builtin and editable Prism catalog templates can create a project with projectType=template; registry entries and project-less guidance packages return the recreate workflow and leave this route. An explicit user-selected guide example with a supported guideDraft is the narrow exception described in Continue an authored guide example: preserve its exact trial values and existing project identity, and do not substitute reference-film recreation. For discovery call openmotion_list_templates, read or grep/jq the returned local JSONL index, and call openmotion_get_template for the chosen ID. Known IDs can go directly to openmotion_get_template. Preserve the instructions and review limitations in TEMPLATE.md. An external reference video is not an editable template: ordinary video recreation uses openmotion-recreate; a request to produce a reusable template uses openmotion-video-to-template. Correct the route once, carrying the selected source and scope, rather than substituting an unrelated example.
See the portable project contract for the handoff layout. HTML/CSS/JS is authoritative; metadata and editable variables are aids, not modification limits.
For a plugin-managed artifact, use the runtime adapter: confirm projectId/session ownership with openmotion_get_project, use openmotion_import_assets for supported local media, then read the current revision/version and save through openmotion_edit_project with projectId, requestId, expectedRevision and expectedVersionId. After a version conflict, read the newer source and reapply the intended edit while preserving Studio changes. Fonts use the existing batch import path and its metadata/license result.
If Studio is requested for a supplied folder or ZIP, follow the native ZIP import flow before editing the managed copy. For local edits or file-only rendering, continue from the actual folder or unpacked copy and record its before-edit source identity.
Unchanged: open it in the editor; changed: edit the working project
With no requested changes to the supplied template, the editable preview handoff below is the delivery: the template's own preview.mp4 already represents that source, so do not render, export, copy or compare it. If the editor cannot show this source (for example an independent folder the handoff cannot adopt), state that limitation and give the absolute path of its preview.mp4 after confirming the file exists, decodes and belongs to this unchanged source. On a continued project that has already been edited, the original template preview is no longer the current result. For unchanged template opening, render or export only when the user asks for a video file; completed video creation or content edits follow the shared final-video delivery flow. Use the existing working project, or create a copy once, without re-creating its design or changing its content/assets, using the pinned HyperFrames runtime identified in the project notes. Read its authoring guide/help via resources/read openmotion://engine/SKILL.md or the installed guide; managed project details return hyperframesCli/authoringGuide paths. Do not open Studio merely to locate a runtime. Render an independent directory directly with host shell capabilities, for example with HyperFrames 0.9.7:
node /absolute/path/to/hyperframes/bin/hyperframes.mjs render /absolute/path/to/project-copy -o /absolute/path/to/output.mp4
Native lint, snapshots and rendering can run in the background; complete the editable preview handoff below when this turn's final video HTML and assets are ready. For plugin-managed projects, request MP4 through openmotion_export_request with projectId, requestId, versionId and expectedRevision; poll openmotion_get_project with projectId/exportJobId. Lint and technical verification are automatic; inspect the actual completed job report and review visuals/audio separately. There is no separate public inspection or verification Tool. Use the pinned native CLI for lint/timeline/info checks before the HTML is ready.
Before editing, ask the user when the request needs facts or assets only they can supply (brand, product, claims, prices, images), or when an ambiguous request would materially change the result. Ask all needed questions at once. Decide minor layout and timing details yourself and mention them briefly. Do not ask anything for an unchanged render.
With requested changes, apply the shared edit workflow to the current working project. Use variables when helpful; edit HTML/CSS/JS, scene structure and media directly when the request needs it. Preserve unrelated content and motion. For longer wording, make the necessary related wrapping/layout/reading-time changes instead of forcing it into an unreadable original interval. Keep replaced wording in the template's type character (the same pixel, stencil, wide or display style), not a generic fallback face. Check text fitting and media cropping after edits. When replacement footage is shorter than its slot, first use other supplied shots or shorten the hold where the soundtrack and following cuts allow; slow motion, freeze frames or repeats are fallbacks. Name any slowed, frozen, repeated or generated shot in the reply, because viewers can see it; when fewer supplied clips fill more slots, say how many slots each clip fills. When new narration plays over supplied footage of a person speaking, their mouth will not match it: say so, and use the person's own recorded sound when they supply it. If brand, image or named-object replacements recur, update their relevant repeated appearances, not just the most prominent one. Do not invent prices, claims or other missing facts.
When a reading hold shifts later pictures, inspect existing audio timing too. Preserving the audio file does not prove synchronization or continuous sound. Report any retained mismatch or silent tail; do not introduce audio generation services to resolve it. When the request replaces narration, time scenes and captions to the delivered voice track instead of keeping the old duration with unplanned silent gaps, and report the resulting length. When updating copy or narration on a template that uses captions, keep the editable caption layer synchronized and legible through the shared caption-sync contract.
Open the editable result
When the final requested video is ready, open it through the editable preview handoff in the same working project. Unchanged template opening uses the same handoff and needs no render or export for this step.
Verify and deliver
For an unchanged request, confirm in the editor that the intended template loaded and plays; unless the user asks for a video file, do not render, export or compare it. For an edited request, play the changed content and its related motion and sound in the editor preview; native snapshots help with layout but do not show motion. For completed video creation or content edits, follow shared final-video delivery and verify the actual MP4; explicit draft, editor-only and review-only requests do not export.
After the playback check, finish the handoff's paused playback state and display confirmation before delivering the editor.
Before rendering, packaging or importing an edited project, run node <runtimeRoot>/scripts/lint-project.mjs <runtimeRoot> <projectDirectory> on the exact folder. It applies Studio's import validation; a plain hyperframes lint or a successful render does not. Fix structural errors (for example timed media nested inside another timed element) with top-level timed layers or the pinned guide's sub-compositions while keeping the picture unchanged, then rerender. Apply the same repair when the supplied template itself fails, and record it in TEMPLATE.md.
For an edited request, inspect the requested content, its related layout/timing and unchanged sections against the template's preview.mp4. Verify that supplied replacement assets are actually used and old brand content does not remain at another relevant appearance. Record passed, failed and unrun checks separately in the copy's TEMPLATE.md. Deliver the final editable project in the editor and, for a completed video creation or content edit, its verified final video in the chat through the shared delivery flow. The shared workflow selects the final preview independently of download requests. Supplementary file delivery follows the user’s requested scope; save those files in the current workspace and use absolute local link targets. For the editable Studio page, use the exact previewUrl from the handoff. Keep the reply short and in the user's words: one or two sentences on what changed and only the limitations the user would notice, including how many slots each supplied clip fills when clips repeat and any mouth mismatch from the edit section above. For an unchanged request, use one completion sentence; the editable page remains open in the host. An accepted first-run experience follows the shared first-run delivery, including its limited exceptions, instead of adding project screenshots or technical evidence. Humans decide visual acceptance; do not give a subjective pass/fail verdict. Do not claim independent-agent verification unless a separate session actually performed it.
For edited or freshly rendered requests, apply the relevant review standards; changed multi-scene relationships use production decisions, and sound changes load the shared context's sound references. These standards do not restart original creative intake or impose a new style on the template. For a fresh managed export, follow verification using the completed job/revision; reuse a matching existing job. Unchanged template opening and explicit draft, editor-only or review-only work create no export job. Stop at the user's requested delivery stage; a draft or review-only request does not automatically render.
If source edits change exposed variables, keep those shortcuts connected or remove stale declarations and explain the source editing entry. A variable declaration alone does not prove the control still works.
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 |