| name | video-motion-previs |
| description | Install and drive Motion Previs Studio v4 from the `video-motion-previs` CLI to turn reference video into pose, depth, camera-motion, control-layer, and AI-video/Blender production packs. Use when an agent must check or install the desktop app, import and trim a shot, run motion analysis, export a bundle, inspect its files, capture the app, or send a layer to Blockout. Triggers on: Motion Previs Studio, video motion previs, camera solve, pose extraction, OpenPose BODY_25, depth control video, production pack, motion-previs MCP.
|
| allowed-tools | Bash Read Write Edit Glob Grep |
| compatibility | Node.js 18+; packaged app supports macOS Apple Silicon and Windows 11 x64, while source development also supports Linux with explicit media runtime overrides. The app must be running for motion commands. |
| license | Apache-2.0 |
| metadata | {"category":"creative-media","subcategory":"motion","interface":"cli","tags":"video-motion, previsualization, ai-video, pose-extraction, depth, camera-motion, openpose, control-layers, cli, mcp","version":"2.0.0","source":"https://github.com/wassermanproductions/motion-previs-studio"} |
Video Motion Previs
Use the lightweight video-motion-previs wrapper to operate the real Motion Previs Studio v4 control API. The wrapper reads the app's localhost-only, token-protected discovery descriptor and calls the same allowlisted actions as the upstream MCP bridge.
When to use this skill
Use this skill for reference-video analysis and Motion Previs Studio production packs. Route pure Blender scene scripting to a Blender skill, ComfyUI graph authoring to an AI-video/ComfyUI skill, web animation performance to optimize-web-animations, and general video editing to video-production.
This is not a fully headless renderer. A running Electron app owns MediaPipe, ffmpeg, UI state, analysis, and export. The CLI is the control surface, not a replacement analysis engine.
Instructions
1. Check before installing
From this skill directory:
node scripts/video-motion-previs.mjs check
The JSON result distinguishes:
- a packaged install in
/Applications or ~/Applications on macOS;
- a source checkout from
MOTION_PREVIS_SOURCE or common local paths;
- a live app with a healthy protocol-v1 control server;
- Node/platform incompatibility and stale discovery files.
Do not reinstall a healthy existing app by default. Motion Previs Studio's generated MediaPipe/model/runtime assets are relatively large, so keep installation idempotent.
2. Install only when needed
node scripts/video-motion-previs.mjs install
Installation policy:
- macOS Apple Silicon: use the inspected official upstream installer and latest arm64 release. Pass
--packaged only when replacing a usable source checkout with the packaged app.
- Windows 11 x64: the CLI reports the official latest-release installer URL; installation remains user-visible because the upstream NSIS installer is unsigned and interactive.
- Linux or Intel macOS: use
install --source [DIR] to clone the source, run npm ci, and prepare pinned SHA-256-verified runtime assets. Linux still needs explicit ffmpeg/ffprobe runtime overrides or PATH as documented upstream.
The upstream installer removes and replaces an existing Motion Previs Studio v4.app, so never force it without user intent.
Install the wrapper itself on PATH when terminal-wide access is desired:
