agentleFS
JiamingShi-JsPhysJiamingShi-JsPhys/3d-fabric/skills/animation-quality-gate/SKILL.md

animation-quality-gate

Skill2 starsChanged 3 days agoMITView on GitHub

Validate Blender animation attempts before accepting them by rendering contact sheets, checking silhouette stability, flicker, framing, subject dominance, layer separation, export compatibility, and motion-design coherence. Use after animation renders or when the user says motion/morph/outside elements look bad.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    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 when: Animation QA, contact-sheet review, motion critique, morph validation, texture flicker detection, storyboard checks, rejecting …

    line 10
  2. Distinctive:

    Before the first Blender call, read ../text-to-blender/references/mcp-backends.md.

    line 12
  3. Distinctive:

    Do not accept an animation because it rendered.

    line 15
  4. Distinctive:

    If a user calls an animation ugly/bad, stop rebuilding immediately.

    line 29
  5. Distinctive:

    add/refine generic skills only after sanitization.

    line 34
  6. Distinctive:

    only then rebuild the animation.

    line 35
  7. Distinctive:

    No final animation without a contact sheet.

    line 39
  8. Distinctive:

    No GLB claim for texture swaps implemented only with Blender Python handlers.

    line 40
  9. Distinctive:

    No decorative context elements in base avatar export unless requested.

    line 41
  10. Distinctive:

    No morph that violates locked geometry constraints.

    line 42

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

MCP backend

Use when: Animation QA, contact-sheet review, motion critique, morph validation, texture flicker detection, storyboard checks, rejecting bad animation passes, pre-export animation acceptance gates.

Before the first Blender call, read ../text-to-blender/references/mcp-backends.md. Prefer official MCP for shared capabilities; preserve the selected backend for the whole task. Tool names in recipes are client/legacy examples: map them through that reference and its agent-host guide.

Animation Quality Gate

Do not accept an animation because it rendered. Accept it only after a contact sheet and failure analysis pass.

Review dimensions

  1. Subject dominance — the main asset remains readable and is not overwhelmed by HUD/context.
  2. Layer separation — base subject, texture state, glow, HUD, and background are separate enough to control.
  3. Silhouette stability — silhouette stays constant unless deliberate morph is specified.
  4. Texture coherence — no ugly full-image crossfade, crop pop, or unregistered morph.
  5. Motion coherence — arcs/dots have a reason, restrained speed, and coherent easing.
  6. Export truth — the final export can reproduce the effect or limitations are explicit.
  7. Frame aesthetics — sampled frames look good as stills.

RALPH trigger

If a user calls an animation ugly/bad, stop rebuilding immediately. First:

  • collect preview frames/contact sheet;
  • identify the failed dimension(s);
  • invoke quality-refinement-autoloop if the stack lacks a method;
  • add/refine generic skills only after sanitization;
  • only then rebuild the animation.

Hard gates

  • No final animation without a contact sheet.
  • No GLB claim for texture swaps implemented only with Blender Python handlers.
  • No decorative context elements in base avatar export unless requested.
  • No morph that violates locked geometry constraints.

Scripts

  • scripts/animation_contact_sheet.py builds a contact sheet and frame-to-frame difference report from rendered frames.

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.