nexu-io/openmotion / skills/openmotion-production
openmotion-production
VerifiedExecute local edits, asset or audio replacements, previews, technical troubleshooting, exports, and delivery on an existing OpenMotion project under established creative decisions. Use openmotion-director for narrative, motion, or audiovisual redesign; openmotion-template-to-video for existing templates; openmotion-recreate for recreating a reference video; and openmotion-video-to-template for reusable templates. Repository development and documentation maintenance do not trigger video production.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.0 KB |
| agents/openai.yaml | config | 139 B |
| fonts/catalog.json | config | 139.4 KB |
| references/context.md | markdown | 15.1 KB |
| references/decisions.md | markdown | 8.7 KB |
| references/edit.md | markdown | 5.9 KB |
| references/fonts.md | markdown | 8.6 KB |
| references/intake.md | markdown | 7.1 KB |
| references/materials.md | markdown | 19.4 KB |
| references/native.md | markdown | 21.4 KB |
| references/portable-project.md | markdown | 5.8 KB |
| references/production.md | markdown | 12.9 KB |
| references/reference-video.md | markdown | 15.5 KB |
| references/review.md | markdown | 11.2 KB |
| references/sound.md | markdown | 12.3 KB |
| references/templates.md | markdown | 9.9 KB |
| references/typography.md | markdown | 10.1 KB |
| references/verification.md | markdown | 12.5 KB |
references/templates.md
View on GitHub# Native template catalog capabilities
Shared catalog capability reference; read when the selected route needs templates. This page does not restart intake or require original productions to choose a template. Reuse an already selected ID and scope. Editable builtin/Prism sources belong to openmotion-template-to-video; video-only references and catalog guidance packages without editable project files (`hasHtmlProject: false`, returned with `workflowGuide.workflow: "recreate"`) belong to openmotion-recreate. Both routes are implemented. Creating a reusable template from a video is a separate openmotion-video-to-template task, chosen only for that requested deliverable.
## Browsing and recommendations
A request to browse, compare or recommend OpenMotion catalog templates is a discovery task, not permission to create. Use existing preferences without a new creative questionnaire.
1. Call `openmotion_open_preview({target: "templates"})` and complete its `previewHandoff` in this turn. Reuse a currently visible matching library tab; do not merely return a text table. Do not pass project/session/version fields or submit project `record_display` for this page. An explicit text-only/no-opening request, including a still-applicable earlier refusal, takes precedence. An exact selected template plus explicit creation intent goes directly to the existing creation flow instead.
2. Present the exact returned URL in the host browser/panel, preserving parameters and the current chat. Verify native panel visibility and actual library content before saying it opened. Only host-confirmed inactivity permits queued deferral; recheck on return. Retry a failed presentation once, then report the failure. If the host lacks a browser/panel, provide the real library URL and explain the limitation. A service failure without a usable URL is a failure, not a link handoff. Prepared, queued and hidden states are not successful display.
3. Read the current connection's catalog with `openmotion_list_templates`, search its local JSONL index and use `openmotion_get_template` as needed to verify candidates. Catalog lookup and page preparation may run concurrently. Usually suggest two or three relevant choices with accurate names and brief reasons; offer one if only one fits, and never invent or pad candidates. State verified duration/capability only: guidance-only references are not directly editable projects. If the catalog is unavailable, still hand over a working library if possible and explain that reliable recommendations are unavailable.
4. Browsing and playback must preserve project contents, selection and history. Do not create a project, download template project source, acquire production assets or export until the user asks to use a selected template. Catalog/preview loading is allowed. If the user already created a project through Studio, continue it instead of making a duplicate.
The detailed policy lives here. Discovery descriptions carry its short trigger/creation boundary. New Tool descriptions and installed Skills must actually be loaded by the host; a compatible backend connection does not refresh an existing chat's context. Use supported host refresh when needed, preserving projects and running work; report unavailable refresh rather than claiming a stale chat is fixed.
## Continue an authored guide example
When the user explicitly chooses a guide’s trial example or supplies its copied `templateId` and `guideDraft`, preserve that exact scope. Read `openmotion_get_template` and the selected `motion.md` declaration, then call `openmotion_create_project` with `projectType=template`, the exact ID, `guideDraft: {title, accent}`, title, requirements and a stable requestId. This explicit option creates the guide’s authored canvas example, even when the entry’s default workflowGuide is recreate; it does not reconstruct the reference film or change the default route for ordinary reference requests. An unsupported declaration must fail rather than substitute a different example.
If Studio already created the draft’s project, use that returned project identity instead of creating another. Replays retain the complete original creation payload, including namingLanguage. Only a server-confirmed `applied=false` creation failure allows a new requestId; unknown outcomes retain the original request. The project includes the motion document and its referenced source bundle. Open its returned preview and verify the trial values. Canvas text has no ordinary inspector edit control; the Agent can continue native variables/source edits. This editor-only handoff does not render, export or send a task automatically.
## Selected template creation
Select an exact editable builtin or Prism template through the Studio gallery or a supplied guide, then call `openmotion_create_project` with projectType=template, templateId, requestId, title and requirements. For discovery, call `openmotion_list_templates` with no arguments: it returns a local JSONL index path, total and catalogVersion, not search results. Search the index using local shell/file tools, then call `openmotion_get_template` with the chosen templateId to read the file manifest and TEMPLATE.md. A known ID can skip listing. These paths are accessible only on the machine running OpenMotion. Other sources require host inspection and native authoring; reference footage is not a copyable template.
A copied gallery prompt deliberately contains only a guide link and template ID. Read that URL for the current workspace, connection config and full instructions. Preserve the chosen ID and defaults; no repeated template selection or optional media intake. For external references, inspect the actual video or registry source, import real assets and author native compositions with openmotion_edit_project. Do not substitute an unrelated built-in example or claim that placing the unchanged reference video on a track is a recreation.
Only when a template choice remains unresolved, offer two or three relevant options, preferably with the user's actual material. Do not present all options when only one fits. Show ID/name, the concrete opening, shot sequence, duration, asset needs, visual difference and tradeoff. The recommendation is advisory until the user selects it or explicitly delegates the choice.
## Accepted template selection
All hosts share the same three distinct reference IDs sampled once from the four-entry curated pool in `shared/onboarding-templates.ts`. Use the exact prepared selection and order from the installation result; do not independently draw another set. When the user asks the Agent to choose a first experience, recommend the first prepared card by name before creating. Installation catalog metadata uses that same selection, including hosts without video cards. Its `recommendedTemplateId` is advisory, not user acceptance. If preparation fails, report the unavailable recommendations with the usable library link and preserve any prior selection; do not replace the list with local builtin samples.
A user-sent “yes / 好 / 就这个” after one named recommendation accepts that recommendation's exact ID. Continue with it without repeating template selection. A number, name or submitted card brief selects that exact card; only a generic agreement to several equal choices without a single recommendation needs clarification. Browsing, playing or copying a card does not authorize creation. Export follows the user's requested scope.
Carry the accepted ID, source and requirements until the user explicitly changes the selection. A directly editable source can use `projectType=template`; a reference-only source requires recreation, not a different template. Sample experiences retain the accepted content, motion and native duration; unrelated workspace branding is not a request to adapt them.
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. Draft preparation is not project creation evidence. Presentation itself remains read-only.
## First-run delivery
Applies to the first successful delivery of an accepted onboarding recommendation, whether it continued as a template or a recreation.
For a successful first-run delivery, keep the editable OpenMotion page open on the right. The final reply contains, in order, one concise completion sentence and the contextual next-step invitation below. Use plain Markdown. Keep screenshots and verification evidence in local records; omit editor screenshots, ZIPs, duplicate project links and checklists unless requested. The selected final-video preview follows [shared delivery](production.md#choose-one-final-video-preview), including host-native embedding; additional downloads still depend on the requested scope. HTML wrappers such as `<details>` and `<summary>` are not part of the reply format.
After the completion sentence, generate one brief, natural sentence in the user's language asking what video they want to make next and introducing three ways to start: choose an existing template, send a video link to recreate, or describe their requirements for an original video. Adapt the wording to the conversation; this is a behavior instruction, not a fixed script. If the user already supplied their next request, acknowledge or continue that request instead of asking again. Otherwise wait for their choice before starting another video. This invitation belongs only to the first successful experience delivery, not follow-up edits or exports.
If a host lacks browser/panel capability, provide the project URL and briefly state that the page could not be opened automatically. Report any material delivery limitation before inviting new work. If the project cannot be created or does not load and play, or a requested export fails, preserve the editable project and report the concrete failure without a success statement or next-step invitation. If tools are unavailable, carry this selected template/defaults/project scope into a continuation without asking the user to choose again.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 198k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |