scenario-video-to-motion
Use when turning a reference video into 3D character animation through the Scenario MCP: markerless motion capture from a phone clip or a generated performance, auto-rigging an uploaded FBX, GLB, or OBJ character and applying the captured motion, raw motion on a Mixamo or MetaHuman skeleton to retar…
Install / Use
npx skills add scenario-labs/skills --skill scenario-video-to-motionInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of scenario-video-to-motion
scenario-video-to-motion scores 84/100 on our quality scale, 2939th of 4,700 Development & Engineering skills we index.
Its SKILL.md is 7.9 KB long, well organised into 8 sections and no code examples: a thorough specification that gives an agent plenty to work with.
With 1,048 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 29 days ago, so scenario-video-to-motion is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-11-10. Automated pattern scan on 2026-11-10. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
scenario-video-to-motion compared with similar skills
All 4 of these similar skills score higher than scenario-video-to-motion; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| scenario-video-to-motion (this skill)by scenario-labs | 84 | 1.0k | 29d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.8k | today | CLAUDE.md |
Frequently asked questions
- How do I install scenario-video-to-motion?
- Run
npx skills add scenario-labs/skills --skill scenario-video-to-motion. The install tabs above show the steps for each supported agent. - Which AI agents does scenario-video-to-motion work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is scenario-video-to-motion safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is scenario-video-to-motion still maintained?
- The repository was last updated 29 days ago, so scenario-video-to-motion is actively maintained.
Skill content
View source on GitHubname: scenario-video-to-motion description: "Use when turning a reference video into 3D character animation through the Scenario MCP: markerless motion capture from a phone clip or a generated performance, auto-rigging an uploaded FBX, GLB, or OBJ character and applying the captured motion, raw motion on a Mixamo or MetaHuman skeleton to retarget yourself, in-place locomotion, looping clips, facial capture, or FBX exports for Blender, Maya, Unreal, Unity, or Roblox. Keywords: mocap, video to motion, video23d, animation from video." license: MIT
Scenario Video to Motion
Overview
Video-to-motion members watch the people in a clip and return 3D animation: either your character
mesh, auto-rigged and moving, or the motion alone on a standard skeleton. They are the video23d
capability, and they differ more than their shared name suggests: which character input they take,
which skeleton comes back, and which file formats they write.
Siblings: scenario (connection, scope, upload, jobs_wait), scenario-3d (making or rigging the
mesh first), scenario-video (generating a reference performance when no footage exists), and
scenario-video-editing (trimming and resizing the clip). If a sibling skill named here is missing
from your available skills, load it with skill_get (Scenario MCP) or ask the user to install it
(https://github.com/scenario-labs/skills#install); unattended, proceed from tool schemas and flag
the gap.
Quick reference
| Step | Call | Watch for |
| ---------------- | ------------------------------------------------------------------ | ---------------------------------------------------- |
| Upload inputs | upload_asset with kind: "video", then kind: "3d" for a mesh | The mesh is optional on every member |
| Fit the clip | asset_get, then trim or resize per scenario-video-editing | Duration, size, and even-dimension limits per member |
| Pick a member | recommend with capability: "video23d" and the user's own words | Read next_step per the scenario skill |
| Read the inputs | model_schema_get | Each file field's kind, the output enums |
| Price, then run | model_run with dry_run: true, then wait: false | The video field carries cost_impact |
| Wait and inspect | jobs_wait, then asset_display | Facing, foot contact, and frame count |
Choose the output before the member
Three outcomes, and members cover different ones. Settle it with the user first (unattended: a character whose existing rig the project depends on takes motion only; otherwise animate the mesh).
- Your character, animated. A member takes the mesh, auto-rigs it, and applies the motion. The rig is the member's own: it does not retarget onto a skeleton the mesh already carries, so clips built for an existing rig need bone remapping.
- Motion only, on a named skeleton. A member returns the animation on a Mixamo-style or MetaHuman skeleton without uploading your character. Choose this when the character is already rigged. The file can include a template mesh: inspect it, then omit that mesh when retargeting onto the user's rig.
- Motion only, from a mesh member. Some mesh members also offer an animation-only flag, which drops the mesh from the download.
recommend ranks the members on measured cost and latency and names which take a character. Ask it
with the user's words, including the outcome above, rather than with a bare capability.
Read the schema, field by field
Field names repeat across members with different meanings, so read each field's kind before
filling it:
- One member's
characterFiletakes a 3D mesh; another member'scharacterFiletakes a reference image of the character, while its mesh field ischaracterModel. The field'skind(3dorimage), not its name, says which asset it takes. - Output formats differ: one member writes engine-specific FBX variants (
fbx-blender,fbx-unreal,fbx-roblox, Maya scene files), one a plainglborfbx(its schema namesfbxfor Unity), and one exposes no format field at all. Pick the engine target in the run:asset_download'sformatconversion is not documented to keep the animation. - An FBX export can be ASCII. Blender's legacy FBX importer rejects it; use its newer ASCII-capable importer. Check the imported animation before calling the file Blender-ready.
- Controls worth setting when present:
moveInPlacefor game locomotion driven by code,loopfor cycles, the frame rate field (namedframeRate,fps, ortargetFps), keyframe cleanup, and theforwardandupaxes when the motion arrives turned or lying down. - Some members track several people (
numPeople) or capture the face; both carrycost_impact.
Footage that captures well
- One person, full body in frame for the whole clip, feet visible, a static camera, no one crossing in front. Loose clothing and props hide joints.
- Trim to the move that ships: price follows the clip, and members cap the input. At authoring time
one capped it at 30 seconds and about 30 MB, another required even pixel width and height. Read
max_durationandmax_sizewhen exposed by the schema. An absent cap is not a promise of unlimited input. Fix an over-cap clip with the video editing tools before pricing. - No footage? Generate the performance with a video model per
scenario-video: a single full-body character on a plain background, a locked-off camera, and the action described beat by beat. The generated clip is then the input like any other. - Motion extraction targets human movement. A creature or a non-biped mesh needs checking frame by frame, and often a DCC pass.
Worked example: a dance clip on a game character
The user has a phone clip of a dance and a character GLB, and wants an Unreal-ready loop.
upload_assetthe clip (kind: "video") and the GLB (kind: "3d") per thescenarioskill.asset_getthe clip: read the duration and dimensions. Trim to the eight seconds that loop with the video cut tool, and resize to even dimensions if a candidate member requires it.recommendwithcapability: "video23d"and a prompt such as "apply the dance in this video to my uploaded character mesh, looping, exported for Unreal". Follownext_stepper thescenarioskill: presentask_useroptions; onproceed, take its pick without asking.model_schema_geton the pick. Put the GLB in the field whosekindis3d. Set the Unreal output target if the format enum has one,loop: true, andmoveInPlace: trueif the game moves the character itself.model_runwithdry_run: trueand quote the price. Then run withwait: false: these jobs take minutes. Retire it withjobs_wait, re-calling withpending_job_idson timeout.asset_displaythe result, or open it in a DCC. Check the facing, that the feet meet the ground, and that the loop point does not pop. If facing is wrong, checkforwardandupwhen the schema exposes them before blaming the capture. A preview link alone is not a visual check.asset_downloadwith noformat, and hand over the file with the skeleton it uses.
Common mistakes
- Expecting the motion on the character's existing rig: mesh members auto-rig from scratch. Use a motion-only member and retarget when the rig must stay.
- Filling a field by its name:
characterFileis a mesh on one member and an image on another. - Sending the full source video: the price grows with the clip, and over-cap clips fail.
- Converting the download to another 3D format instead of setting the export target in the run.
- Treating a sideways or upside-down result as a failed capture before trying the axis fields.
- Polling
job_getinstead ofjobs_wait, or re-running a job that only timed out.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
headroom
79.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
