blender-video-recreate
Skill4 starsChanged 21 days agoApache-2.0View on GitHub
Reconstruct a readable reference video's observable shots, articulated action, contacts, and camera motion as an editable Blender white-model video, then optionally prepare or run an authorized model-video handoff. Use for reference-video recreation, not prose-only original previs or simple video editing.
In this repository44 other files it gives its agents.
- AGENTS.mdAGENTS.md
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-exploreSkill
- openspec-proposeSkill
- openspec-sync-specsSkill
- openspec-update-changeSkill
- blender-ai-replicationSkill
- blender-asset-librarySkill
- blender-background-jobsSkill
- blender-character-animationSkill
- blender-character-riggingSkill
- blender-cinematographySkill
- blender-connectorSkill
- blender-curvesSkill
- blender-design-loopSkill
- blender-designSkill
- blender-exportSkill
- blender-grease-pencilSkill
- blender-hairSkill
- blender-hard-surfaceSkill
- blender-harness-drivingSkill
- blender-harnessSkill
- blender-inspectSkill
- blender-managedSkill
- blender-mcp-setupSkill
- blender-previewSkill
- blender-previsSkill
- blender-procedural-modelingSkill
- blender-quality-validationSkill
- blender-recoverSkill
- blender-render-compositingSkill
- blender-retopologySkill
- blender-scene-assemblySkill
- blender-sculpt-surfaceSkill
- blender-seedance-pipelineSkill
- blender-sequence-editingSkill
- blender-simulationSkill
- blender-to-dreaminaSkill
- blender-trackingSkill
- blender-useSkill
- blender-uv-materialSkill
- blender-video-originalSkill
- blender-visual-loopSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 8 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Use when the user supplies a readable video or bounded clip and wants its action, staging, or camera movement rebuilt as an editable …
- Distinctive: line 27
Read reference-analysis.md before inferring the shot table.
- Distinctive: line 28
Read white-model-production.md before scene mutation.
- Distinctive: line 29
Read generation-handoff.md only when downstream model-video generation is in scope.
- Distinctive: line 76
Use examples/validation.md for the minimum result shape.
- Distinctive: line 80
Do not claim exact 3D recovery from one view or invent unreadable action.
- Distinctive: line 81
Do not replace articulated characters with sliding single primitives when limb motion or contact order is part of acceptance.
- Very specific: line 83
Do not overwrite the only source or approved .blend.
- Distinctive: line 84
Do not upload reference media, incur a charge, or submit a remote task without the required authorization and budget envelope.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Blender reference-video recreation
Recreate what can be observed: timing, framing, screen-space motion, contacts, camera path, and action continuity. Do not pass the source video through a style filter and call that a 3D reconstruction. Monocular footage does not uniquely determine depth or hidden geometry; label estimates and optimize them for the approved camera views.
什么时候使用(When to Use)
Use when the user supplies a readable video or bounded clip and wants its action, staging, or camera movement rebuilt as an editable Blender white model. Do not use for a prose-only concept, look development on an existing approved animation, or VSE-only editing.
输入与前置条件(Prerequisites)
- A locally readable or explicitly authorized reference video, target time range, desired changes, output root, and acceptance priorities.
- A Blender control route capable of scene inspection and mutation. If unavailable, report the missing route; installing or enabling one is a separate action.
- A declared frame rate and delivery size. Preserve source timing by default; do not silently retime it to convenient frame counts.
- Read reference-analysis.md before inferring the shot table. Read white-model-production.md before scene mutation.
- Read generation-handoff.md only when downstream model-video generation is in scope.
执行流程(Workflow)
Step 1. Probe the actual media and extract representative frames around shot boundaries, action beats, contacts, occlusions, and camera-direction changes. If the media cannot be decoded, stop instead of reconstructing from its title or description.
Step 2. Produce shot-plan.md with source timestamps and exact project frames. Record per shot:
composition, subject scale and screen position, environment anchors, articulated action beats,
prop state, contact order, camera intent, observed facts, and estimates.
Step 3. Establish scale, floor, stable subject ids, one object for each continuous prop, and an editable articulated proxy or rig. For domain work, hand off by installed skill name:
blender-scene-assemblyfor objects and collections;blender-character-riggingandblender-character-animationfor articulated performance;blender-cinematographyfor lens, framing, path, and handheld response;blender-quality-validationfor contacts, floor penetration, gait, prop handoff, and visibility.
Install missing domain skills with
npx skills add full-aigc-skills/blender-skills --skill <skill-name>; never depend on sibling
relative paths.
Step 4. Block coarse action and camera first, then refine contacts and transitions. Recreate the source action order and cumulative imbalance rather than resetting the character after every hit or beat. Keep effects, textures, sound, and final styling out of white-model acceptance unless the user explicitly includes them.
Step 5. Render a cheap complete preview. Compare source and reconstruction at representative frames and motion intervals using acceptance-checklist.md. Correct bounded timing, composition, sliding, same-side gait, penetration, prop discontinuity, or camera loss; do not use aesthetic differences to excuse geometric or temporal errors.
Step 6. Save the editable .blend, white-model video, shot-plan.md, comparison.md, and
acceptance record. If authorized generation is requested, prepare prompts.md, choose an actually
available provider route, and keep its result acceptance separate from Blender acceptance.
验证与交付证据(Validation)
Return an evidence packet containing source hash and probed properties, target segment, project
FPS/frame range, Blender scene and preview paths, inspected intervals, representative frame pairs,
measured validation results, unresolved estimates, and artifact hashes. Use PASS, FAIL, or
UNVERIFIED per layer: media analysis, Blender structure, motion/contact, camera/composition,
encoding, and optional generated video. A successful encode is not motion approval.
Use examples/validation.md for the minimum result shape.
Rules 与能力边界(不适用场景)
- Do not claim exact 3D recovery from one view or invent unreadable action.
- Do not replace articulated characters with sliding single primitives when limb motion or contact order is part of acceptance.
- Do not overwrite the only source or approved
.blend; save a new version or transaction. - Do not upload reference media, incur a charge, or submit a remote task without the required authorization and budget envelope.
- Windows foreground Blender and real paid-provider behavior remain
UNVERIFIEDuntil tested in that environment; portable instructions are not runtime proof.
Gotchas(常见问题与恢复)
- Ambiguous depth: match screen-space landmarks and parallax, then document the chosen depth.
- Foot sliding or same-side gait: fix root speed, planted-foot intervals, and opposing limb phase.
- Prop teleport at release/catch: retain one prop and verify world transforms before/after the constraint switch.
- Camera looks smooth but misses contact: validate visibility at the exact impact frames.
- Remote timeout: query the stored task id; never resubmit merely because the client timed out.
- Repeated defect after two bounded repair rounds: preserve the best version and report the exact interval and remaining deviation instead of looping indefinitely. See examples/recovery.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

