blender-video-original
Skill4 starsChanged 21 days agoApache-2.0View on GitHub
Turn a prose video concept into a timed, editable Blender white-model scene with articulated action, camera motion, preview evidence, and an optional authorized model-video handoff. Use for original concepts without a required reference-video reconstruction.
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-recreateSkill
- blender-visual-loopSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 8 are distinctive, and 0 are 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Use for an original short, one-take action, product beat, scene concept, or story moment that needs 3D blocking, articulated motion, camera …
- Distinctive: line 25
Read shot-planning.md before mutation and white-model-production.md before animation.
- Distinctive: line 27
Read generation-handoff.md only when downstream generation is in scope.
- Distinctive: line 51
Keep one persistent object for a prop across grip, release, flight, catch, and recovery.
- Distinctive: line 73
Do not silently add characters, shots, props, or narrative events that contradict the concept.
- Distinctive: line 74
Do not use a sliding rigid placeholder when articulated action is an acceptance target.
- Distinctive: line 75
Do not treat a successful render, keyframe count, or tool response as proof of good motion.
- Distinctive: line 76
Do not upload, publish, install, charge, or overwrite without the authority required for that action.
≈ “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 original white-model video
Convert prose into an executable shot contract, then build and validate an editable Blender white
model before spending time or money on final styling. A mood image may guide appearance; if a video
must be followed for action or camera timing, use blender-video-recreate instead.
什么时候使用(When to Use)
Use for an original short, one-take action, product beat, scene concept, or story moment that needs 3D blocking, articulated motion, camera timing, and a white-model preview. Do not use for editing existing clips or for rebuilding a supplied reference video's observable movement.
输入与前置条件(Prerequisites)
- A concept, required subjects/actions, output root, and explicit must-preserve/forbidden elements.
- Duration, FPS, dimensions, aspect ratio, and shot structure when specified. If absent, select
reversible defaults and label them in
shot-plan.md; defaults are not user requirements. - A Blender control route capable of scene inspection and mutation. Missing tools do not authorize installation or a substitute provider.
- Read shot-planning.md before mutation and white-model-production.md before animation.
- Read generation-handoff.md only when downstream generation is in scope.
执行流程(Workflow)
Step 1. Create shot-plan.md with stable shot ids, integer frame intervals, role ids, environment
anchors, action beats, contact/trigger events, camera intent, ending state, and documented defaults.
Cause must precede effect; allocate preparation, action, follow-through, and settling time.
Step 2. Build scale, floor, environment masses, articulated characters, persistent props, and the delivery camera. Hand off domain work by installed Skill name:
blender-scene-assemblyfor scene structure;blender-character-riggingandblender-character-animationfor bodies and props;blender-cinematographyfor framing and motion;blender-quality-validationfor measurable acceptance;blender-render-compositingandblender-sequence-editingfor approved output.
Install a missing dependency with
npx skills add full-aigc-skills/blender-skills --skill <skill-name>; do not assume sibling files
exist after a granular install.
Step 3. Animate in dependency order: root motion and balance, planted feet, opposing limbs, interaction contacts, prop constraints/free flight, gaze, secondary motion, then camera response. Keep one persistent object for a prop across grip, release, flight, catch, and recovery.
Step 4. Render a cheap full-duration preview and inspect the intervals listed in acceptance-checklist.md. Repair bounded defects without rebuilding unrelated approved work. Technical validation and visual review are both required.
Step 5. Save the editable .blend, white-model preview, shot-plan.md, prompt package, and
acceptance record. Stop here when the user asks only for a white model.
Step 6. If authorized model-video generation is requested, discover the actual provider capability, bind upload consent and budget, submit at most the authorized request, persist its task id, and validate its result independently from the white model.
验证与交付证据(Validation)
Record assumptions, scene revision/snapshot, project FPS and exact frame range, role/object map,
action intervals, measured gait/contact/floor/camera results, inspected playback ranges, preview
and .blend hashes, encoding properties, and remaining risks. Status each layer separately as
PASS, FAIL, or UNVERIFIED; use examples/validation.md.
Rules 与能力边界(不适用场景)
- Do not silently add characters, shots, props, or narrative events that contradict the concept.
- Do not use a sliding rigid placeholder when articulated action is an acceptance target.
- Do not treat a successful render, keyframe count, or tool response as proof of good motion.
- Do not upload, publish, install, charge, or overwrite without the authority required for that action.
- Windows foreground Blender and real paid-provider behavior remain
UNVERIFIEDuntil exercised; local macOS evidence cannot be generalized to them.
Gotchas(常见问题与恢复)
- Too many beats for the duration: simplify or lengthen the plan before animation; do not compress contacts until they become unreadable.
- Same-side gait or sliding: correct phase, root speed, step length, and foot-lock intervals.
- Trigger occurs early: drive the effect from the verified contact frame, not an approximate beat.
- Camera interpolation overshoots: inspect adjacent frames and adjust handles/path timing.
- Encoded video is valid but performance is not: keep encoding PASS and motion FAIL/UNVERIFIED.
- Two bounded repairs fail: preserve the best version, report the exact interval, and follow 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.

