/openmotion-template-to-video

name: openmotion-template-to-video
description: Browse, 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

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](../openmotion-production/references/context.md) 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](../openmotion-production/references/edit.md), 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.

The accepted installation experience follows [first-run defaults](../openmotion-production/references/templates.md#first-run-experience-defaults): use the exact template ID and unchanged sample content offered and accepted in this conversation, with that template's own duration. A single-template yes accepts it; a three-candidate yes needs clarification. Resume an existing experience project or create one independent copy once. Open its editable preview; export only if requested. Do not restart the template/assets questionnaire or substitute a fixed default. Initial installation reply rules and few-shots come from `docs/install.md`, section “Installation-success reply”; this Skill resumes creation after consent.

A native recommendation card identifies the exact ID in this chat's corresponding result. Its Recreate template button only prepares a composer draft; it does not submit a task or authorize creation/export. Wait for the user to send the brief, then honor its template title/ID, requirements, attachments and requested HTML/MP4 delivery. Do not substitute legacy frozen sample `createArgs` for a customized submitted brief. For a numbered acceptance of the unchanged offered copy, pass its complete frozen `createArgs` to `openmotion_create_project` without adding a current `sessionId`, changing its `requestId` or rewriting its title/requirements on retry. User changes form a new intent under the existing workflow; do not reuse an old request ID with altered inputs. Reuse a confirmed project from this experience, including a GUI-created copy, rather than creating again after a card redisplay. Draft preparation is not project creation evidence; reconcile an unknown write before retrying. Presentation itself remains read-only.

When selecting, obtaining or replacing assets, read the [shared material policy](../openmotion-production/references/materials.md), preserving the template's agreed structure, motion and content constraints. An unchanged preview handoff does not trigger asset acquisition.

Browse or recommend catalog templates

For library discovery rather than creation, follow [browsing and recommendations](../openmotion-production/references/templates.md#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.

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. An unchanged request needs only the editable preview handoff below. Preserve source, assets and hidden Studio manifests. Do not require `template.json`, a local template ID or catalog registration.

If the user selected a gallery/catalog item instead, read its exact source/guide and ID, then follow [catalog capabilities](../openmotion-production/references/templates.md). Bundled projects use `openmotion_create_project` with projectType=template, templateId, requestId, title and requirements only when the selected project has not already been created. Editable registry sources are inspected and adapted from their real source and assets; builtin and Prism catalog templates can create a project with projectType=template. 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](../openmotion-recreate/SKILL.md); a request to produce a reusable template uses [openmotion-video-to-template](../openmotion-video-to-template/SKILL.md). Correct the route once, carrying the selected source and scope, rather than substituting an unrelated example.

See the [portable project contract](../openmotion-production/references/portable-project.md) for the handoff layout. HTML/CSS/JS is authoritative; metadata and editable variables are aids, not modific