agentleFS
khanhhuyenngo985-syskhanhhuyenngo985-sys/animation-craft/SKILL.md

animation-craft

Skill0 starsChanged 6 months agoMITView on GitHub

Use when creating, refining, or reviewing animation videos, animated shorts, storyboards, animatics, AI-video shots, character performance, scene timing, camera motion, action beats, continuity, editing rhythm, sound cues, or image-to-video prompt plans for Seedance/即梦/可灵/海螺 style workflows. Do not use this as a frontend/UI motion skill unless the user explicitly asks for interface animation.

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. memi-design/design-skills★ 7same name
    2. ZhouYinLong-lab/Dog-Skills★ 7same name
    3. jcoger/skills★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

The file

Show its rules and text

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈13

    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 it to turn an idea, scene, character, reference, or rough prompt into a watchable animated sequence with clear story beats, readable …

    line 12
  2. Distinctive:

    Before producing assets or prompts, identify:

    line 16
  3. Distinctive:

    If the user asks for a quick prompt, still define the shot's beginning, motion, and ending before adding style words.

    line 24
  4. Distinctive:

    Remove decorative movement that does not change attention, emotion, information, or consequence.

    line 47
  5. Distinctive:

    Keep one main action per shot unless controlled chaos is the point.

    line 51
  6. Distinctive:

    Use setup, anticipation, action, impact, reaction, and settle.

    line 59
  7. Distinctive:

    When reviewing an animation video, diagnose in this order:

    line 112
  8. Distinctive:

    Do not polish style before story, staging, timing, and continuity work.

    line 121
  9. Distinctive:

    Do not describe only a beautiful still image.

    line 125
  10. Distinctive:

    Do not rely on abstract emotion words.

    line 126
  11. Distinctive:

    Do not overpack 15 seconds.

    line 127
  12. Distinctive:

    Do not let character identity drift while the state changes.

    line 128
  13. Distinctive:

    Do not invent UI, subtitles, text, logos, app screens, or webpage behavior unless the project explicitly requires them.

    line 129

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Animation Craft

Core Positioning

This skill is for making animation videos. It is not a frontend animation or UI micro-interaction skill.

Use it to turn an idea, scene, character, reference, or rough prompt into a watchable animated sequence with clear story beats, readable staging, stable identity, useful camera movement, and video-model-ready shot instructions.

Start Here

Before producing assets or prompts, identify:

  • Format: animated short, 5-15s AI-video shot, multi-shot sequence, animatic, storyboard, action segment, ad film, MV beat, or style test.
  • Audience effect: joke, emotion, awe, clarity, product proof, character charm, suspense, or action impact.
  • Main subject: character, creature, object, environment, product, vehicle, or abstract force.
  • Change: what is visibly different by the end of the shot or sequence.
  • Production target: storyboard, shot list, animatic timing, Seedance/即梦/可灵/海螺 prompt, review notes, or repair plan.

If the user asks for a quick prompt, still define the shot's beginning, motion, and ending before adding style words.

Video Brief

For substantial work, produce this compact brief first:

FieldAnswer
Premise / task
Format + duration
Main subject
Visual change
Emotional beat
Camera logic
Continuity anchors
Sound / rhythm cue
Model targetSeedance / 即梦 / 可灵 / 海螺 / other
Output neededbeat sheet / shot list / prompt / review / repair

Runtime Flow

  1. Lock the story or motion job.
    • One shot should establish, reveal, pressure, turn, release, or land a final beat.
    • Remove decorative movement that does not change attention, emotion, information, or consequence.
  2. Stage the first readable frame.
    • The viewer should immediately know subject, location, scale, pressure, and visual direction.
    • Keep one main action per shot unless controlled chaos is the point.
  3. Design movement as cause and effect.
    • Want becomes reach, gaze, lean, travel direction, grip, or camera pursuit.
    • Obstacle becomes distance, threshold, surface, opposing force, prop failure, crowd, weather, or timing pressure.
    • Consequence becomes residue, deformation, prop state, body state, lighting change, silence, or next-shot inheritance.
  4. Plan timing.
    • Use setup, anticipation, action, impact, reaction, and settle.
    • For AI video, timebox changes with visible 0-2s / 2-5s / 5-8s / 8-15s beats when useful.
    • Let big turns breathe; do not fill every second with new information.
  5. Protect continuity.
    • Lock character identity, scene identity, prop ownership, screen direction, light source, weather, damage, and ending state.
    • For multi-segment work, state what the next segment must inherit in its first two seconds.
  6. Handoff to production.
    • For storyboard: output panels with duration, camera, action, and transition.
    • For AI video: output prompt-ready shot blocks with timing, camera, subject motion, environment reaction, audio cue, and forbidden drift.
    • For review: lead with story/staging/timing/continuity findings before polish.

Knowledge Base

Load optional references only when needed:

FileRead when
references/animated-shorts.mdPlanning animated shorts, beat sheets, shot lists, storyboards, animatics, character action
references/visual-storytelling.mdMaking a beat readable through pose, props, setting, silence, and consequence
references/animation-fundamentals.mdTiming, spacing, anticipation, follow-through, arcs, squash/stretch, silhouette
references/motion-principles.mdVideo motion language, staging, rhythm, camera/object hierarchy, state change
references/motion-rules.mdPractical rules for readable shot motion, continuity, loops, action, and camera movement
references/implementation-notes.mdAI-video production notes, model handoff, prompt timing, review, and verification
references/review-rubric.mdReviewing generated animation videos or animatics with severity and fixes
examples/storyboard-template.mdStoryboard panel planning
examples/ai-video-shot-template.mdSeedance/即梦/可灵 style timed shot prompt
examples/continuity-ledger.mdMulti-shot continuity ledger

Output Patterns

Shot Prompt Block

SHOT [number] / [duration] / [aspect]
Purpose:
Mounted references:
First frame:
0-2s:
2-5s:
5-8s:
8-15s:
Camera:
Character / object motion:
Scene reaction:
Audio:
Continuity inheritance:
Forbidden drift:

Review Order

When reviewing an animation video, diagnose in this order:

  1. Story clarity: can the viewer explain what changed?
  2. Staging: is the main action readable in the first frame and peak frame?
  3. Timing: do anticipation, action, impact, reaction, and settle have enough space?
  4. Performance: does the body/face/prop motion reveal intention?
  5. Continuity: do identity, scene state, prop state, screen direction, and light track?
  6. Production polish: camera smoothness, flicker, morphing, texture, sound, edit point.

Do not polish style before story, staging, timing, and continuity work.

AI Video Guardrails

  • Do not describe only a beautiful still image; describe visible change over time.
  • Do not rely on abstract emotion words. Convert emotion into posture, gaze, breath, hesitation, contact, residue, or silence.
  • Do not overpack 15 seconds. Give each beat a physical action and a readable ending state.
  • Do not let character identity drift while the state changes.
  • Do not invent UI, subtitles, text, logos, app screens, or webpage behavior unless the project explicitly requires them.

When To Hand Off

  • Character identity, bone structure, costume, or drift → character-design
  • Scene space, light, environment continuity, or scene drift → scene-design
  • Final model-specific prompt packet → prompt-framework
  • Shot-by-shot reference study → shot-study
  • Sound design or music timing → sound-design-to-prompt / score-editing-to-prompt
  • Larger local project routing or creative team workflow → animation-studio

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.