Blender Motion State Inspection
Debug Blender characters with Muse: extract structured scene state first (bones, axes, contacts, frames), then confirm with renders. Catches foot sliding, mirrored imports, and scale drift.
- What
- Debug Blender characters with Muse: extract structured scene state first (bones, axes, contacts, frames), then confirm with renders. Catches foot sliding, mirrored imports, and scale drift.
- Cost
- Free
- Needs
- Use "Blender Motion State Inspection" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: an inspection workflow for Blender characters, rigs, and retargeted motion that refuses to judge from screenshots alone. Screenshots hide axis conventions, bone names, object scale, local transforms, parented meshes, and frame-by-frame contact state, so the skill extracts structured facts first (via a state exporter or a Blender Python script run through blender --background, since bpy only exists inside Blender's own interpreter), then uses renders to confirm what the facts imply. The workflow inventories the scene, maps the skeleton with semantic bones, resolves forward/up/side axes (watching for glTF Y-up versus Blender Z-up mismatches), samples the frames most likely to expose problems, checks model integrity before blaming retargeting, and diagnoses ground penetration, foot sliding, leg crossover, twist damage, and scale drift with practical thresholds (1 to 2 cm penetration, 5 percent scale change, 30 degree heading jumps). Reports separate confirmed facts from visual suspicions with frame numbers and coordinates. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: you need Blender and the actual scene file, screenshots alone will not do; it diagnoses, it does not repair meshes unless you explicitly ask. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Blender Motion State Inspection" with your Muse. Prerequisites: Blender installed and the actual .blend scene file. Screenshots alone are not enough. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/blender-motion-state-inspection/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Inspect this Blender character's motion: [describe the symptom, e.g. foot sliding during a walk cycle]." 3. Export structured state first: run the exporter or a Blender Python script via blender --background scene.blend --python collect_motion_state.py, then paste the facts into the chat for diagnosis. Tip: sample the frames the skill recommends (first, middle, contact, airborne, extremes) instead of eyeballing one render. Safety: a skill is plain-text instructions; it runs nothing by itself. Run Blender scripts from trusted sources only. Review generated commands before running them.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.