Skip to content

nexu-io/openmotion / skills/openmotion-template-to-video

openmotion-template-to-video

Verified

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.

FileKindSize
SKILL.mdskill md15.4 KB
agents/openai.yamlconfig138 B
references/first-use.mdmarkdown3.4 KB
references/recipes.mdmarkdown5.3 KB
references/unchanged-export.mdmarkdown7.6 KB
scripts/delivery.mjsscript9.9 KB
scripts/playback.mjsscript7.4 KB

references/first-use.md

View on GitHub
# First-run template experience

Read for an accepted first-run template recommendation (including a curated reference that continues through recreation) or a submitted recommendation-card brief. Initial installation reply rules and few-shots remain in `docs/install.md`, section “Installation-success reply”; this procedure resumes creation after consent.

## First-run experience defaults

Installation opens the library without creating a project. Resolve agreement, source capability and sample scope through [accepted template selection](../../openmotion-production/references/templates.md#accepted-template-selection). Do not restart the template/assets questionnaire or substitute a fixed default. Reuse an existing experience project, including a Studio **Open and edit** project, instead of creating a duplicate.

For a reference-only selection, read its exact ID with `openmotion_get_template`, read its instructions and motionDocument, and continue through `openmotion-recreate` with the accepted sample content or submitted changes. For a directly editable source, call `openmotion_create_project` once with projectType=template, the accepted templateId, stable requestId, title and confirmed requirements. Record the source ID and returned projectId in working notes. Preserve that selection during retries and recovery; if retrieval or production is blocked, explain the blocker without switching samples. Shorter duration, faster export, builtin availability and technical smoke testing never justify switching to decision-tree or another sample. Call `openmotion_open_preview({projectId})` and open its exact previewUrl through the host's supported browser/panel; check the actual selected content and playback. Before delivery, compare the actual project with the accepted source and report any unmet scope. Export only when requested.

For a recommendation card, 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. A reference card has no `createArgs`: read its exact ID and continue through recreation. Only when the accepted unchanged card is a directly editable sample that actually supplies `createArgs`, 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. Reconcile an unknown write before retrying.

For a directly editable source with requested unchanged HTML/project or MP4 files, continue through [unchanged file export](unchanged-export.md), including its bounded handoff and parallel version-pinned work. Modified content uses [verification](../../openmotion-production/references/verification.md); reuse an applicable existing job or call `openmotion_export_request` once with the current projectId/versionId/revision and stable requestId. Poll `openmotion_get_project` with exportJobId; technical verification is automatic, actual playback is separate.

Reply, next-step invitation and failure reporting follow the shared [first-run delivery](../../openmotion-production/references/templates.md#first-run-delivery).
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall