SpriteCook Animate Assets

Use this skill for animation workflows. Pair it with spritecook-workflow-essentials for credits, manifests, safe downloads, and shared defaults.

Requires: SpriteCook MCP server connected to your editor. Set up with npx spritecook-mcp setup or see spritecook.ai.

Tool

animategameart

Animate an existing SpriteCook asset into a short pixel-art or detailed animation. The tool returns a job immediately; follow its poll.tool and poll.arguments instead of holding the request open.

Workflow

1. If the user already has a SpriteCook asset, pass its assetid directly to animategame_art.
2. If the user only has a local image file path, use spritecook-upload-assets to call createassetupload, upload the bytes, then call finalizeassetupload.
3. If the user supplies a small data URL or raw base64 value, call importasset first and use the returned assetid.
4. Use the returned assetid in animategame_art.
5. Keep pixel omitted unless you need to force a mode.

The upload/import step is where the source image enters SpriteCook. It is not the animation call itself. Use MCP asset upload tools when they are available.

Consistency Rules

• Always animate the exact source asset that represents the intended character or object.
• If the user asks for multiple motions for one character, run separate animation jobs against the same asset_id for Idle, Walk, Attack, and so on.
• Do not create a new still image for each motion unless the user explicitly wants different character designs.

Source Rules

• Pixel animation is the correct choice for assets up to 256x256.
• Detailed animation is the correct choice for assets between 256x256 and 2048x2048.
• Do not force a sub-256 source into detailed mode.
• Keep edge_margin=6 by default. It helps prevent pixel art from crowding the canvas edge.

Prompt Writing

• Inspect the actual source character before writing the prompt.
• For pixel art, upscale the source with nearest-neighbor to about 1024x1024 for inspection only.
• Identify visible character details first: silhouette, armor, visor, weapon, shield, pose, and facing.
• Only mention details that are actually visible in the source image.
• Write one short paragraph in plain prose, not a label or keyword list.
• Describe what moves, how it moves, what stays stable, and how visible props or weapons are used.
• Keep the motion grounded in the existing character rather than inventing new equipment or effects.
• Avoid generic prompts like idle animation unless autoenhanceprompt=true.

Example idle prompt: The armored soldier in purple tactical gear stands in a steady combat stance, subtly bobbing up and down in a rhythmic breathing idle. His yellow visor catches the light while his rifle shifts slightly in his grip, maintaining a high state of readiness.

Example attack prompt: The armored soldier in purple tactical gear raises his rifle and fires several shots, with yellow muzzle flashes appearing at the tip of the barrel. His body recoils with each shot while his head and visor remain focused forward, maintaining a steady combat stance throughout the firing sequence.

If autoenhanceprompt=true, simple prompts like Idle, Attack, or Walk are valid because SpriteCook can inspect the source asset and expand them automatically.

checkjobstatus

Use the jobid from animategameart with checkjobstatus. On success, use assetid plus the canonical spriteurl; use spritesheeturl only when present. If the response reports warning.code="assetoutputunavailable", execute the supplied warning.recovery tool call.