メニュー
Check and configure motiscope — verify ffmpeg/ffprobe are installed and scaffold the API-key config used for optional (stubbed) asset generation. Use for first-time setup, "motiscope isn't working", dependency errors, or /motiscope:doctor.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Recreate an analyzed animation as working web code — GSAP (JavaScript), CSS/Web Animations, Framer Motion (React), or Lottie/SVG. Use after `motiscope-analyze`, or when the user asks to "build/recreate this animation in <framework>". Reads the motiscope animation spec and emits a runnable component.
Recreate an analyzed animation as working web code — GSAP (JavaScript), CSS/Web Animations, Framer Motion (React), or Lottie/SVG. Use after /motiscope:analyze, or when the user asks to "build/recreate this animation in <framework>". Reads the motiscope animation spec and emits a runnable component.
Rebuild a whole landing page / multi-section website from a screen recording that scrolls or walks through it. Use when the user has a recording of an ENTIRE page (not a single animation) and wants the full page recreated — layout, sections, copy, design system, and scroll animations. Orchestrates analyze (measured timing + section structure + curated frames) + asset generation + a full multi-section build. For one isolated animation, use `motiscope-recreate` instead.
Rebuild a whole landing page / multi-section website from a screen recording that scrolls or walks through it. Use when the user has a recording of an ENTIRE page (not a single animation) and wants the full page recreated — layout, sections, copy, design system, and scroll animations. Orchestrates analyze (measured timing + section structure + curated frames) + asset generation + a full multi-section build. For one isolated animation, use /motiscope:recreate instead.
Analyze a screen recording of an animation to characterize its motion — timing, easing, transforms, and sequencing — so it can be recreated as web code. Use when the user drops or points at a video of an animation (.mp4/.mov/.webm/.mkv/.m4v/.avi/.gif) and says things like "I want this animation on my site", "recreate this motion", "how is this animated", or runs `motiscope-analyze`.
Analyze a screen recording of an animation to characterize its motion — timing, easing, transforms, and sequencing — so it can be recreated as web code. Use when the user drops or points at a video of an animation (.mp4/.mov/.webm/.mkv/.m4v/.avi/.gif) and says things like "I want this animation on my site", "recreate this motion", "how is this animated", or runs /motiscope:analyze.
| name | doctor |
| description | Check and configure motiscope — verify ffmpeg/ffprobe are installed and scaffold the API-key config used for optional (stubbed) asset generation. Use for first-time setup, "motiscope isn't working", dependency errors, or /motiscope:doctor. |
| argument-hint | |
| allowed-tools | Bash, AskUserQuestion |
| user-invocable | true |
Verify dependencies and scaffold config. motiscope's pipeline is pure Python standard library, so the only hard dependencies are ffmpeg and ffprobe.
SCRIPTS="${CLAUDE_PLUGIN_ROOT:-}/scripts"
[ -f "$SCRIPTS/mvsetup.py" ] || SCRIPTS="<absolute dir of this SKILL.md>/../../scripts"
(Windows: use python.)
python3 "$SCRIPTS/mvsetup.py" --json
The JSON reports status, missing_binaries, install_hint, platform, config_file, env_file, and per-provider key presence.
Do not install silently. Ask the user for permission (AskUserQuestion), then run the platform command:
brew install ffmpegsudo apt-get install -y ffmpeg (or sudo dnf install ffmpeg)winget install Gyan.FFmpeg (or choco install ffmpeg)Re-run mvsetup.py --check afterward to confirm (exit 0 = ready).
python3 "$SCRIPTS/mvsetup.py"
This creates, if absent:
~/.config/motiscope/config.json — non-secret preferences (default_target, frame_budget, resolution, frame_format, image_provider, video_provider).~/.config/motiscope/.env (mode 0600) — optional API keys for asset generation, commented out by default.Asset generation (creating an image an animation needs) is optional — no key is required for analysis or code recreation. Image generation is real for Gemini/Imagen; the other providers write a labeled placeholder until wired. To configure one, ask the user (AskUserQuestion) which provider, and write the key into ~/.config/motiscope/.env:
| Purpose | Providers (env var) |
|---|---|
| Image | Gemini/Imagen (GEMINI_API_KEY) — implemented; OpenAI (OPENAI_API_KEY), Stability (STABILITY_API_KEY), Replicate (REPLICATE_API_TOKEN), fal (FAL_KEY) |
| Video | Runway (RUNWAY_API_KEY), Replicate (REPLICATE_API_TOKEN), fal (FAL_KEY) |
Image generation works today with gemini (Imagen). Other providers write a
labeled placeholder until wired.
Reassure the user: keys stay in a local 0600 file, are never printed, never written into generated code, and never committed (the repo .gitignore excludes .env).
Summarize: dependency status, what was scaffolded, and whether any provider keys are configured. If everything is ready, say so in one line and point them at /motiscope:analyze.