DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to rig a character in Rigify and export a Unity walk cycle with Blender Skills

Rig a character with Rigify, add a walk animation and export the result to Unity.

  • Content
  • Advanced
  • 90 minutes
  • From the README
  • Claude Code
  • Codex
  • Cursor
  • Gemini CLI

Who it is forA small studio animator who needs a rigged character with a walk cycle for a Unity project.

The problemRigging, animating a walk cycle and exporting for a game engine are separate jobs, and a mistake in any one stage breaks the next.

The outcomeA Rigify-rigged character with a walk cycle exported for Unity, built by an agent following the rigging, animation and export skills.

What you need first

  • Blender 5.2 or newer installed
  • git to clone the repository
  • An AI coding agent such as Claude Code, Codex, Gemini CLI or Cursor
  • Optional: a Blender MCP server so agents can work in your open Blender session

Steps

  1. Clone the repository: git clone https://github.com/EL4CTEO/blender-skills
  2. Install the skills: ./blender-skills/install/install.sh (macOS / Linux) or .\blender-skills\install\install.ps1 (Windows)
  3. Ask the agent to rig the character with Rigify and to create a walk cycle using the animation skill.
  4. Ask the agent to export the animated character for Unity using the export pipelines skill.
  5. Open the file in Unity and play the walk cycle to confirm the bones deform as expected.

Prompt for your agent

Using the blender-skills repo, rig <character model> with Rigify, add a looping walk cycle and export it for Unity. Expect a rigged .blend or exported file and the name of the walk action. Verify that the walk action loops and that the exported skeleton keeps the rig's bone names.

Caveat. The README names Rigify and Unity but does not state which Rigify bone names or Unity import settings will carry over, so check the skeleton after import.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page