Skip to content
SkillModel-led1,906 tokens in use

godot-animation

Drives Godot 4.7 animation with AnimationPlayer, AnimationTree state machines, AnimatedSprite2D and Tweens, and tests clip and state names headless.

9,684 stars on the repository Apache License 2.0gamedev-skills/awesome-gamedev-agent-skills · skills/godot/godot-animation
npx skills add gamedev-skills/awesome-gamedev-agent-skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing godot-animation costs

89tokens idle
1,906tokens in use
3,190tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

shelldetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter12/15
  • Structure25/25
  • Examples12/15
  • Output15/15
  • Size13/15
  • Resources15/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent
  • File that was not read−15

    a file the skill ships that was not read, so what it does is unknown

    assets/test_animation_states.gd

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity92
  • Maintenance96
  • Community60
  • Maturity24
  • Momentum40

This skill teaches an agent how Godot 4.7 animation fits together: AnimationPlayer stores keyframed clips, an active AnimationTree owns those tracks and is driven by code, and Tween handles short code-driven moves such as UI pops and fades. It gives one owner per property as the organising rule.

The skill includes patterns for awaiting a clip, travelling a state machine, blending by a 2D parameter and popping a UI element in with a tween. A bundled headless test confirms every clip exists, the tree is active and wired, and each state is reachable. The gotchas explain why travel() does nothing and why tweens snap back.

What You Get

  • A workflow that assigns one owner to each animated property: player, tree or tween
  • GDScript patterns for playing a clip and continuing, state-machine travel, blend spaces and UI tweens
  • A headless test that checks clips exist, the AnimationTree is active and each state is reachable
  • A smoke-run recipe that greps the log for Animation not found and other errors Godot logs with exit code 0

Common Use Cases

  • Wiring an AnimationTree state machine to a character’s movement state
  • Debugging travel() that does nothing or an animation that will not play
  • Fixing a tween that snaps back, stalls or logs an infinite loop
  • Animating UI elements such as pop-ins and fades with Tween

What Makes It Unique

Animation bugs in Godot often log an error and still exit 0, so the skill tells the agent to run the scene headless and grep the log, and it adds a state-reachability test on top. It lists the exact parameter paths for trees and blend spaces and the 4.7 Control offset transform properties that stop tweens snapping back inside containers.

Under The Hood

The agent loads the SKILL.md and, when needed, a reference on transitions, root motion, Call Method tracks, SpriteFrames and the full Tween API. It then runs commands in your project: the Godot binary headless on a scene with the log redirected to a file and searched with grep, the optional Python project checker from the godot-nodes-scenes skill, and a copied GDScript test placed under a tests folder. It reads scene files and writes the test and log files; it makes no network calls. The shipped GDScript test is a file type the scanner cannot read, so what it does was not analysed and is worth a look before you run it.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers