nexu-io/openmotion / skills/openmotion-video-to-template
openmotion-video-to-template
VerifiedRebuild a reference video (pure motion graphics or mixed media with products, people, or audio) into a reusable editable OpenMotion template with source files, assets, preview, editing guide, and folder or ZIP delivery. Use only when a reusable template is requested; use openmotion-recreate for a single film recreation, openmotion-template-to-video for adapting an existing template, and openmotion-director for original videos.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.7 KB |
| agents/openai.yaml | config | 146 B |
| references/measure.md | markdown | 2.4 KB |
| references/rebuild.md | markdown | 6.0 KB |
| references/rule-sources.md | markdown | 3.5 KB |
| references/verify.md | markdown | 8.6 KB |
references/verify.md
View on GitHub# Check and deliver the project
Native directory workflow: run the pinned CLI lint/timeline/info and render commands in the project directory, then inspect the actual output. The MCP calls below are alternatives for projects managed by the plugin, not requirements for portable projects.
## 1. Inspect the project
Use the pinned native CLI lint/timeline/info commands for source diagnostics and timing; consult that runtime's help. Fix actual errors. Things the original genuinely has (its colours, its small text) stay when they are valid native content — keep matching the original. Check each element's timing against `TEMPLATE.md`.
Phase-one MCP has no standalone inspection Tool. For managed projects, opening a requested editor runs lint, and an export automatically runs lint and technical verification. Neither result proves that each element matches the reference. Do not open Studio or render an unwanted final video merely to obtain diagnostics; use host CLI capabilities for draft-only checks, or record an unavailable check.
## 2. Export and compare with the original
For a plugin-managed project:
1. Read `openmotion_get_project({projectId})` for the inspected source's revision and currentVersionId. Reuse a completed export only when both match the required deliverable.
2. Otherwise call `openmotion_export_request({projectId,requestId,versionId,expectedRevision,audio})`, using that currentVersionId as versionId and a stable requestId. Use audio=required when the reference has sound to retain, or silent for a silent reference. Creation or successful saving is not an export.
3. Poll `openmotion_get_project({projectId,exportJobId:jobId})` for that job. Only completed with a passed automatic verification is technical success. On failed, inspect the diagnostic, fix the source if needed, read its new version and use a new requestId for the corrected export. Do not submit repeated jobs while one is pending/running.
4. Compare the actual exported file with the local reference using available host playback, frame inspection or native CLI diagnostics. There is no public video-comparison Tool or implicit `latest-export` candidate; use the actual returned MP4 path. Produce the original-versus-template comparison video with available host media tooling, outside the template ZIP. If a capability is unavailable, record the specific missing evidence and delivery gap rather than inventing results.
For an independent native folder, use the pinned CLI to inspect/render that directory, then probe/decode the output and compare it with the reference. An unrelated managed projectId or revision cannot protect or verify these files. Do not claim MCP snapshot verification for a direct CLI render.
When comparing:
- Apply the shared [fidelity checks](../../openmotion-production/references/reference-video.md#check-fidelity-and-edit-dependencies) at the same actual timestamps, including composition, motion, pacing and missing stretches.
- Open the relevant source/rendered frames; optional similarity diagnostics only locate differences, never define visual acceptance.
- Before packaging, run the shared cut audit on the reference and the rendered preview. List each unpaired cut that remains under `Differences from the original`.
- Check duration, retained sound and audio offset through actual media evidence. A stream can contain only silence; inspect decoded audio before choosing the export mode and verify the actual content and synchronization when sound is present. At a cut, cue or narration anchor that depends on precise timing, compare its position in the decoded source and final file; container timestamps alone do not establish alignment. Record listening separately from decoded timing using the [shared audiovisual evidence rules](../../openmotion-production/references/verification.md#verification-scope). For mixed-media shots, compare representative start, action and cut frames for product/subject continuity and for the intended layering and readability. Check narration against the actual voice and caption timing when present.
Fix locatable issues relevant to the request, then re-export the changed source. When a fix stops reducing the difference, follow the shared bounded repair in the same fidelity checks and record the issue in `TEMPLATE.md`. A limitation note does not turn an unresolved defect into a passed check. Similarity scores locate differences; humans decide visual acceptance. The package self-containment check is below.
**Record checks in one of three states** in `TEMPLATE.md`:
- Ran, passed
- Ran, did not pass (say where it differs)
- Did not run (environment, tooling, timeout). **A check that didn't run is never reported as passed**, and never left out.
## 3. Package the native project
Follow the [portable project contract](../../openmotion-production/references/portable-project.md). Deliver the complete project directory or ZIP with source, required assets, preview, cover and `TEMPLATE.md`. Rendering must not require a local template ID, custom `template.json` or a custom registration tool.
Check that intended content and motion remain reasonably editable. A whole reference video, full-frame sequence or unadaptable contour transcription is not a substitute for that work; ordinary time-driven arrays and functions are allowed. Keep optional root variables as convenient edits, not the only allowed changes. Check local file references and required Studio manifests before packaging. For mixed media, render one representative edit from a separate copy: change visible copy independently of its footage and, where the template promises a replaceable media slot, substitute its asset and verify crop, timing and unaffected overlays. For a product or brand that repeats, verify the edit at each affected shot, including marks on the product itself. Do not send an unchanged render or this local edit back to a generation model.
`preview.mp4` must come from exactly the source being delivered. If source changes after export, re-export before packaging.
## 4. Verify the delivered copy
This checks that the ZIP works on its own, so later edits can render. It is not a pixel comparison or a new model run: `preview.mp4` is the packaged baseline, while unchanged reuse follows the selected template workflow.
Unpack the ZIP into another directory. Do not use a registered template ID or read files back from the original working project. Run the pinned native CLI there; consult its help for the runtime's supported options. For HyperFrames 0.9.7:
```sh
node /absolute/path/to/hyperframes/bin/hyperframes.mjs render /absolute/path/to/unpacked-project -o /absolute/path/to/reproduced.mp4
```
- The render completes without missing files, fonts or assets, creator-machine paths or undeclared remote dependencies.
- Frame rate, actual decoded frame count and duration equal those of `preview.mp4`.
- A few representative frames look like the preview.
Do not compare every frame, and do not spend repair rounds on pixel differences that are not visible (for example GPU antialiasing). Fix a failed render, a missing file or a visible difference. Record the result in `TEMPLATE.md` as passed, failed or not run.
Run `node <runtimeRoot>/scripts/lint-project.mjs <runtimeRoot> <unpackedDirectory>` on the unpacked copy for every template, because later template use imports it into Studio; structural errors there are delivery failures. When the handoff includes Studio import, also validate the exact ZIP in an isolated workspace using the [native ZIP import flow](../../openmotion-production/references/portable-project.md#import-a-native-zip-into-studio). Import has its own native validation. If the linter or import rejects nested timeline media, use top-level timed layers or the pinned guide's native sub-compositions, then rerender and repackage the corrected source. Record the import and version-read results separately from the unpacked render.
This is a self-containment check, not independent-agent proof. Do not claim an independent test happened inside the creating session.
## 5. Delivery
Reply briefly with absolute local file paths, not relative paths (they break when the reply is copied or opened in another host) or a temporary localhost URL that stops when the session ends. Put only the plain path in each link target. Link the preview, the folder/ZIP and the original-versus-template comparison video for human review (saved next to the ZIP, outside the package). Then state what can be changed (the Studio Variables panel or source) and the remaining differences from the original in plain words. Leave measurements, scores and check states in `TEMPLATE.md` unless one affects the user. A score is diagnostic, not a visual-quality verdict. Optional catalog IDs are secondary and never replace the portable files.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |