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/portable-project.md
View on GitHub# Portable HyperFrames template project
The deliverable is a native HyperFrames project, closest to an official `hyperframes:example`: editable HTML/CSS/JS and the assets needed to render it. It must work after unpacking in a different directory, without the creator's local catalog or plugin cache paths.
A useful layout (split scenes only when helpful):
```text
project/
index.html
compositions/
assets/
hyperframes.json
TEMPLATE.md
preview.mp4
poster.jpg
```
`index.html` is the content authority. `hyperframes.json` is native runtime configuration, not a second description of the video. Preserve hidden Studio manifests if the project uses them. Bundle fonts and dependencies that the project actually needs; use project-relative references, not creator-machine paths or undeclared remote assets. Do not package runtime caches (including Studio `.thumbnails/`), node_modules, temporary measurement files, or the `AGENTS.md`/`CLAUDE.md` agent instructions that `hyperframes init` creates. Keep the folder to what renders the video plus `TEMPLATE.md`, `preview.mp4` and the cover. Do not re-encode `preview.mp4` to shrink it: it is the finished video delivered as-is for unchanged reuse. Store an extracted soundtrack as AAC (`.m4a`) by default. If a decoded timing check shows that the pinned renderer shifts this encoding at the trim or edit point, use a supported local encoding (for example, FLAC) that preserves the alignment in the actual export; record the trade-off and recheck the unpacked copy. The comparison video is for human review only, so encode it for web playback (H.264, for example `-crf 28`) rather than at preview quality.
For a distributable package, use fonts/assets with documented redistribution permission and include required license files. A locally installed system font is not evidence of that permission. Prefer open-licensed fonts, such as Google Fonts families under SIL OFL, and bundle each with its license file. For Chinese text, declare a fallback chain such as the Latin font, then Noto Sans SC (Noto Serif SC for serif), then generic families, rather than bundling a system Chinese font. If permission is unconfirmed, replace it with an appropriate permitted font and regenerate affected previews, or identify the delivery as local-only with the unresolved dependency.
Include a preview MP4 from the delivered source and a representative cover for browsing. `TEMPLATE.md` identifies the entry, pinned HyperFrames version, exact tested preview/render commands, common editable content and known differences from the reference. Variables are shortcuts; agents may also edit native source. Neither fixed slots nor a custom `template.json` is required to read or render the project.
`TEMPLATE.md` is the single handoff note, mainly for the next agent and template producers: what to change (variable or source/asset entry and its layout/timing dependencies), differences from the original, the rebuild record (observations, named objects, choices) and check results. Organize it by meaningful objects or systems, not every decorative fragment. It is not a content schema or an editing whitelist. The user-facing editing surface is the root variables shown in the Studio Variables panel. Update or remove stale variable declarations after source edits.
For website/registry publication, add an official `registry-item.json` of type `hyperframes:example` using the schema and examples shipped with the pinned runtime. Its file list must include referenced source and assets. Follow that schema for preview metadata; do not invent a separate content schema. Registry publication and website upload are separate from making a usable project. The team's gallery/import integration owns discovery, categories and IDs.
Save the template folder and its same-named ZIP in the current workspace (the session's working directory), not in plugin caches, temporary or system data directories. The ZIP is the single delivery unit, including for cloud upload. Record reference provenance and verification results in `TEMPLATE.md`. Save the original-versus-template comparison video next to the ZIP as `<template-name>-comparison.mp4`, outside the package: it shows the reference footage, which must not be redistributed with the template. Do not put comparison videos, comparison screenshots or check data files in the package. Keep working files such as frame dumps, measurement scripts and intermediate renders out of the package. They describe what was tested; they do not drive rendering. Video, audio and generated assets used by the selected workflow must be packaged as the exact local media needed by the project. The portable package must render without a provider connection or access to the creator’s asset library.
The team gallery owns catalog registration and template IDs. A delivered folder or ZIP can be reused directly without a gallery listing.
## Import a native ZIP into Studio
Use **Import projects** in Studio, or `openmotion_project_archive` with `action: "import"`, an absolute local `sourcePath`, and a stable `requestId`. To bring an independent folder into Studio, package it as a native ZIP first. Import creates a copy.
Open the copy from Studio's project list and wait for the editor to load its media before calling `openmotion_get_project` with the returned project ID. A project-specific call starts managed version capture even when it only requests an HTML file. Workspace listing with `openmotion_get_project({})` is safe while Studio loads. The pinned Studio runtime adopts larger files after first open, and an early project-specific read can record an incomplete version.
Use background editor access if the host supports it and the user requests background work. If the host cannot open Studio, stop at the confirmed import receipt and report the version check as pending. Keep the independent source and archive available.
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 |