JavaScript is disabled. Some features may not work.
blender-motion-state-inspection — ★ 220.5K GitHub Stars — Install Guide | SkillsNav
🇺🇸 English🇨🇳 中文
SkillsNav
Home

blender-motion-state-inspection

★ 220K repomlN/AIntermediateClaude
🤖 AI Summary

This skill extracts structured Blender scene data (bone transforms, bounding boxes, contact states, and object hierarchy) to diagnose animation issues like twisting, foot-sliding, or broken imports, rather than relying solely on visual screenshots.

How to Install

Claude Code:
git clone --depth 1 https://github.com/affaan-m/ECC.git && cp ECC/skills/blender-motion-state-inspection ~/.claude/skills/blender-motion-state-inspection -r
# Blender Motion State Inspection ## When to Use - A Blender character looks twisted, mirrored, flattened, offset, or foot-sliding in an animation. - A user asks whether an imported avatar, armature, or retargeted motion matches an expected pose. - You need to compare rendered evidence with structured facts such as bones, bounding boxes, contacts, and facing vectors. - A workflow depends on deciding whether a model is a character, prop, proxy mesh, control rig, or broken import. ## Core Principle Do not judge animated 3D assets only from screenshots. Screenshots are review evidence, but they hide axis conventions, bone names, object scale, local transforms, parented meshes, material slots, and frame-by-frame contact state. First extract structured Blender state, then use viewport screenshots or renders to confirm what the facts imply. ## How It Works 1. Establish the clean scene and asset baseline before judging motion. 2. Extract structured facts from Blender using an exporter or Blender Python run inside Blender's own interpreter. 3. Sample the frames most likely to expose contact, orientation, scale, and retargeting errors. 4. Compare the measured facts against the user's expected pose, direction, ground plane, and render goal. 5. Return a concise report that separates confirmed facts, likely causes, and required fixes. ## Inspection Workflow 1. Inventory the scene. - List meshes, armatures, empties, cameras, lights, modifiers, parent relationships, and hidden objects. - Separate character meshes from helper/proxy geometry before judging the avatar. - Record object-space and world-space bounding boxes. 2. Identify the skeleton. - Capture armature names, pose bones, bone heads/tails, roll, parent chains, constraints, and rest-pose axes. - Map semantic bones such as hips, spine, neck, head, shoulders, elbows, hands, thighs, knees, ankles, and feet. - Flag missing left/right pairs and unusual naming schemes. 3. Determine forward, up, and side axes. - Use the pelvis, spine, shoulders, hips, head, and feet together; do not rely on a single mesh normal. - Compare local armature axes with world axes and imported file conventions such as glTF Y-up vs Blender Z-up. - Mark likely mirrored or backwards imports when face/head/feet direction conflicts with root motion. 4. Sample animation frames. - Inspect first, middle, contact, airborne, and extreme frames. - Record root location, root heading, pelvis height, torso lean, limb directions, foot clearance, and mesh bounds. - For long or fast motion, sample more densely around flips, landings, turns, collisions, and floor contacts. 5. Check model integrity before retargeting blame. - Confirm the clean baseline shape before applying animation. - Preserve original mesh, materials, armature, and skinning unless the user explicitly asks for repair. - Treat unexplained sphere-like blobs, giant proxy meshes, or crushed bodies as import/selection issues unti

Details

Category AI/ML → ml
Sourceaffaan-m/ECC
SKILL.mdView on GitHub →
Repo Stars★ 220.5K
Est. per SkillN/A (shared across 121 skills from this repo)
DifficultyIntermediate
Risk LevelN/A

Related Skills

Works Well With

Skills from the same repository — often designed to work together