Update to Motionvid

{
  "description": "Turn a topic, script, blog post or docs page into a narrated animated explainer video with motion graphics. Use when the user wants an explainer, a how-it-works video, a tutorial animation, or a video version of a page.",
  "included_files": [],
  "name": "explainer-video",
  "skill_md_contents": "---\nname: explainer-video\ndescription: \"Turn a topic, script, blog post or docs page into a narrated animated explainer video with motion graphics. Use when the user wants an explainer, a how-it-works video, a tutorial animation, or a video version of a page.\"\n---\n\n# Explainer video\n\nBuilds a narrated explainer from a topic, a script or a URL. With a URL, MotionVid fetches the page and matches its design, so pass the link in the prompt instead of pasting the page text.\n\n- Script provided: pass it as the prompt and say it is the narration script.\n- Topic only: MotionVid writes the script and researches current topics on the web itself.\n- Default length is about 30 seconds. For 60-90 second explainers, pass `duration`.\n\nWrite narration as a paraphrase of any source page, not lifted sentences.\n\n## Build loop\n\n1. Collect only what changes the video: topic or script, length, aspect ratio (16:9 landscape, 9:16 for Reels/TikTok/Shorts, 1:1), narration yes/no, and any brand link or logo. Ask at most one short question, and only if the answer would change the video.\n2. If the look matters and the user has not picked one, call `list_animation_styles`, then `suggest_animation_styles` with 2-6 fitting ids and let the user pick. If the account has a brand kit (`list_brand_kits`), offer it.\n3. Call `create_video` with `render=true` when the user wants a file. Put any URL (site, launch page, docs) in the prompt itself: MotionVid reads its copy, palette and typography.\n4. Poll `get_video_status` until the job is terminal. Don't quote an ETA; use `poll_after_seconds`.\n5. Give the user the `download_url` and the `app_url` (the project in the MotionVid editor, where every scene stays editable).\n\n## Changes after the first cut\n\nUse `edit_video` with the job id for any change to a finished video (\"change the headline\", \"make scene 2 blue\", \"shorter intro\"). It edits only what the instruction names and keeps the rest. Don't rebuild with `create_video` for a tweak. Use `preview_video` to check frames before rendering again.\n\n## Errors\n\nIf a tool returns an account or credit error, tell the user plainly what it says. Never start a purchase in chat.\n"
}