agentleFS
arjun988arjun988/blender-skills/.claude/skills/animation/SKILL.md

animation

Skill2.2k starsChanged 4 months agoMITView on GitHub

Game-ready animation in Blender including walk/run/idle cycles, combat, mechanical animation, camera animation, constraints, Graph Editor, and NLA workflows via MCP.

11 other projects use a version of this.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

Who's talking about arjun988/blender-skills

The biggest 5 of 12 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 12

Talked about on GitHub (12 times).

On GitHub · 12

7 more on GitHub

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 3

    Distinctive

    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
  1. Distinctive:

    Use constraints over bone deformation

    line 53
  2. Distinctive:

    Avoid sudden direction changes

    line 82
  3. Distinctive:

    Test cycle loop before export

    line 109

“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Animation

Game-ready motion with clean keyframes. Readable silhouettes in motion. Engine-compatible export.

When to Use

  • Character locomotion (walk, run, idle)
  • Combat animations
  • Mechanical/prop animation
  • Camera animation
  • Object animation with constraints

Workflow

Reference → Blocking → Breakdown → Splining → Polish
    → Cycle Validation → NLA Strip → Export

Locomotion Cycles

CycleKey PosesFrames (30fps)
WalkContact, Down, Pass, Up × 224–32
RunContact, Drive, Flight, Recovery16–24
IdleBreathe, weight shift, blink60–120 loop

Naming: AN_[Char]_[Action]_[Variant]

Animation Principles (Applied)

  1. Timing — Weight through spacing
  2. Arcs — Natural limb paths
  3. Overlap — Secondary motion offset
  4. Anticipation — Wind-up before action
  5. Exaggeration — Style-dependent (see style skills)

Mechanical Animation

  • Use constraints over bone deformation
  • Hinge: Limit Rotation constraint
  • Pistons: Stretch-to or Copy Location
  • Gears: Driver for synchronized rotation
  • Doors: Empty pivot + rotation keyframes

Graph Editor Workflow

1. Block stepped keys (Constant interpolation)
2. Splining: Bezier with auto handles
3. Ease: Weighted handles for acceleration
4. Cycle: Copy first/last frame; verify loop seam
5. Clean: Remove redundant keys

NLA for Game Export

1. Action created and named per convention
2. Push down to NLA strip
3. Strip set to Repeat for cycles
4. Single strip active for export
5. Scale: 1.0; no NLA time remapping unless intentional

Camera Animation

  • Smooth Bezier interpolation always
  • Avoid sudden direction changes
  • Match focal length to subject scale
  • Camera shake: noise modifier on location (subtle)

MCP Integration

  1. Insert keyframes via MCP if supported
  2. Query action names and frame ranges
  3. Validate bone/object animation data exists pre-export
  4. Set frame range via MCP
  5. Export animation with rig via export-pipeline

Game-Ready Requirements

  • Root motion decision documented (in-place vs root motion)
  • Loop seam invisible (walk/idle/run)
  • No bone scale keyframes (engine issues)
  • Animation length matches engine state machine
  • Facial animation on separate action layer if needed
  • Frame rate: 30fps default (confirm project spec)

Constraints

MUST DO

  • Reference video for locomotion
  • Block in stepped mode before splining
  • Name actions AN_ prefix
  • Test cycle loop before export
  • Match animation style to art direction

MUST NOT DO

  • Linear interpolation on organic motion
  • Scale keyframes on rig bones
  • Over-animate idle (subtle is better)
  • Export without action assigned to NLA
  • Skip root motion documentation

Reference Guide

TopicReferenceLoad When
Walk cycle breakdownreferences/walk-cycle.mdLocomotion
Combat timingreferences/combat-animation.mdAction games

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.