/openmotion-recreate

name: openmotion-recreate
description: >-
  Recreate a reference video (a link or file) as the user's own film with OpenMotion: rebuild it as an
  editable OpenMotion project and hand it over open in the editor, keeping the original content or
  swapping in the user's copy, brand and assets. This includes small edits to
  the user's own finished video when no editable project for it exists. "Make one like this" and "I
  want this feel" both count as recreation. In a workspace with the user's product material, a bare
  link alone means "make one like this for us". Not for only analysing or discussing a video. Use
  openmotion-director when the reference is only inspiration for an original film,
  openmotion-template-to-video for an existing template, openmotion-production for edits to an existing
  editable OpenMotion project, and openmotion-video-to-template for a reusable template package.

OpenMotion Recreate — reference video → the user's own film

Role and goal

The user supplies a video and wants a version of it for themselves. Deliver the editable OpenMotion project, open in the editor, where the user reviews it and keeps editing. Before handing it over, export it and check the exported film against the reference by numeric measurement and by inspecting extracted frames; the export is for this check, not a file to send. This Skill carries the recreation rules and the measuring script; shared engineering rules still come from the documents in §0. [rebuild](references/rebuild.md) covers reading, measuring and rebuilding the reference; [check and deliver](references/verify.md) covers export and numeric measurement. Use only the Tools actually returned by tools/list.

This workflow currently covers motion graphics only. For live action, talking heads or AI footage, say that this workflow does not support them yet. Do not suggest that footage or other material would make such a recreation possible: material the user provides can only go into a motion-graphics adaptation, which you may offer. State the limit as a fact about this workflow; never mention, quote or link this Skill or its files in the reply.

0. Shared context

Read the [shared context](../openmotion-production/references/context.md) before working; it lists the references a recreation needs and how to reuse documents already read. When the work changes an existing draft or project, also apply the [shared edit workflow](../openmotion-production/references/edit.md). If the reference turns out to be only loose inspiration for an original film, switch to [openmotion-director](../openmotion-director/SKILL.md).

1. Read the user's context before anything else

Before asking anything, look in the current workspace for the user's own material: README and docs, product or marketing copy, brand files, logos, screenshots, colour or font definitions, package or site metadata. Read what is there. This is the user's brand, product and latest features; use it as the content of the film.

Then read the reference as [rebuild](references/rebuild.md) describes: a local decodable copy, its URL and checksum, the whole video and consecutive frames around important changes. Links and local files take the same route. A cover image or an unreachable link is not a viewed video; never claim to have watched it.

2. Decide what the user wants

Work out the film the user wants from everything available: their words, whose film the reference is, what the workspace holds and the conversation so far. Short requests often mean more than they say. A bare link in a workspace with product material usually asks for a film like this about that product; "do this for our new feature" or "I want this feel" usually asks for the reference's craft carrying the user's story; an explicit list of changes asks for exactly those changes.

Whether the reference's brand stays or becomes the user's is your judgement from the request and context, not a fixed rule. When a wrong guess would change the whole film, such as "make one identical" while the workspace holds the user's own brand, put it in the single question below; otherwise decide and state the assumption at delivery.

Parts the request does not cover keep the original. Requested changes are in scope without restriction: wording, brand, images, colours, typography, pacing, duration, adding or removing scenes.

3. Ask at most once

Ask only when the workspace and the request together still lack something only the user can supply (brand, product, claims, numbers, prices, logos, images), or when an ambiguity would materially change the result. With usable material in the workspace, do not ask who the film is for. Offer "you decide" where it fits. When selecting, obtaining or replacing an image, clip or sound, apply the [shared material policy](../openmotion-production/references/materials.md) within this workflow's supported media scope. Ask for a material gap only when it cannot be resolved within the current scope, available sources and authorization. For configured BYOK generation, use openmotion_media_use and read action=reference for the selected provider; this does not expand the creative scope of the request.

Ask all of it in one batch through the host's question interface, in the user's language. If nothing is missing, do not ask. Do not ask about technical choices, intermediate approval or storyboards. After the answers, work through to the finished film without stopping.

4. Create the project

Follow the [runtime adapter](../openmotion-production/references/production.md) and [Native authoring](../openmotion-production/references/native.md). A continued recreation reuses its projectId. Otherwise create one project with `openmotion_create_project` and a stable requestId: `projectType: "reference_video"` with `referenceUrl` for a link, or `projectType: "natural_language"` for a local file, with the file path and the agreed brief in `requirements`. Creation makes an empty carrier, not