← LeaderboardThe Skill Leaderboard

openmotion-onboarding

Welcome the user after OpenMotion plugin setup and open its template library.

Published by nexu-io ↗nexu-io/openmotion

Try your first task

A source-grounded starter task has not been verified for this skill yet.

SKILL.md

name: openmotion-onboardingdescription: Welcome the user after OpenMotion plugin setup and open its template library.

OpenMotion onboarding

Read the installation-success contract and follow it in this conversation. Reuse the installed connection and data directory; setup is already complete, so do not reinstall.

For an automatic installation callback, read its exact event file, verify that its thread matches this chat, and use event.onboarding directly. Preserve event.appRoot and event.dataDirectory. Never rerun setup or schedule another callback. The queue acknowledgment is not a displayed welcome; this turn must perform and verify the actual presentation below.

Use the installation's existing onboarding result when setup returned one. When the desktop plugin callback has no result yet, run the installed application's node --experimental-strip-types scripts/install-onboarding.mjs from its plugin root, preserving the connection's MOTION_DATA_DIR and setting OPENMOTION_ONBOARDING_LANGUAGE from the latest request. This invokes the same default flow as source and CLI setup, without reinstalling, requiring user flags or creating a project. Resolve the workspace from the installed connection; never substitute another workspace.

If this host has an inline HTML renderer, the default flow returns inlinePresentation (under onboarding for npm setup). The runtime document is not automatically readable by the chat. First run the installed scripts/inline-onboarding.mjs --publish-from PATH --sha256 SHA256 --host-directory DIRECTORY using its prepared path/hash and this chat's explicitly permitted visualization directory. Never infer that directory from application/data write access or guess another chat's root. If no host-readable directory is available, report that limitation instead of emitting a runtime path. Visibly open the real template-library preview, then emit the publisher's exact content reference once. This preserves the installed production welcome and three verified videos without waiting for native MCP discovery. Recreate retains the copyable brief; never submit it automatically. Preserve directAccess and its environment when supplied. Do not require a restart or repeat setup. Preparation/publication and awaiting_host_delivery are not proof of displayed content.

For CLI setup, resolve the contract's hostHandoff before native presentation. A registration result, queued refresh or independent MCP probe is insufficient. Keep a requested complete onboarding pending when this chat cannot discover the presentation tool; report the actual host-action requirement instead of silently declaring the library-only fallback complete.

Source setup returns a concise onboardingStatus and detailsFile rather than printing the full success examples. Read the details only when needed. host_action_required and refresh_requested forbid a library-only success reply in Codex. If this host has the inline renderer, generate the presentation from the existing application as described in the contract and complete that route without a restart. If neither route is available, present the prepared library while reporting the specific presentation limitation; do not reinstall or create another chat. Resume in this workspace after supported host recovery.

Open the template library in the calling chat's right panel using the returned preview handoff, then call the natively discovered presentation tool with onboarding: true and language matching the latest user request (or their explicit requested output language), never the host interface language. Use zh, en, ja, ko, fr, es or pt; use en for unsupported languages. The component displays the persistent welcome and three cards; send no separate welcome, duplicated template descriptions or trailing status reply. Verify the actual opening result and use the matching welcome example from the contract. Keep project creation and export pending until the user submits a creation request.