Create and manage sprite animations with multiple frames, animation tags, frame durations, and linked cels. Use when the user wants to animate a sprite, add animation, create movement, make it move, mentions "animation", "animated", "frames", "keyframes", "frame rate", "FPS", "timing", "duration", "walk cycle", "run cycle", "idle animation", "attack animation", "jump", "movement", "motion", or describes actions like "walking", "running", "jumping", "attacking", "breathing", "bobbing", "bouncing". Trigger on animation tags, loops, playback, sequences, "add frames", "duplicate frame", "frame timing", "ping-pong", "loop", "sequence". Also for linked cels, static backgrounds, and frame optimization.
Creates sprite animations by adding frames, setting timing, and organizing sequences with tags. Used when user wants to animate sprites, create walk cycles, idle animations, or mentions frames, timing, loops, or motion.
/plugin marketplace add willibrandon/pixel-plugin/plugin install pixel-plugin@pixel-pluginThis skill is limited to using the following tools:
examples.mdreference.mdThis Skill handles all animation-related tasks for sprites, including frame management, timing, animation tags (sequences), and linked cels for efficient animation.
Use this Skill when the user:
Trigger Keywords: animate, animation, frames, walk cycle, run, idle, attack, loop, movement, motion
Frame: A single image in an animation sequence. Sprites start with 1 frame.
Frame Duration: How long each frame displays (in milliseconds). Default: 100ms (10 FPS).
Animation Tag: Named sequence of frames (e.g., "walk" frames 1-4, "idle" frames 5-8).
Linked Cel: A cel that shares image data with another cel. Editing one updates all linked cels.
Playback Direction:
Adding Frames:
Use mcp__aseprite__add_frame to create new frames:
Common Frame Counts:
Duplicating Frames:
Use mcp__aseprite__duplicate_frame to copy existing frames:
Deleting Frames:
Use mcp__aseprite__delete_frame to remove frames:
Frame Duration:
Use mcp__aseprite__set_frame_duration:
Common Timing Patterns:
Even Timing: All frames same duration. Simple and predictable.
Variable Timing: Different durations for emphasis.
Hold Frames: Longer duration for dramatic effect.
Purpose: Organize frames into named sequences.
Use mcp__aseprite__create_tag:
Example Tags:
Benefits:
Purpose: Share image data across frames to save memory and maintain consistency.
Use mcp__aseprite__link_cel:
When to Use:
Workflow:
Workflow 1: Walk Cycle (4 frames)
Workflow 2: Idle Animation (2 frames)
Workflow 3: Complex Multi-Animation Sprite
User Request:
"Add a simple idle animation to this sprite"
Approach:
User Request:
"Create a walk cycle animation for this character"
Approach:
User Request:
"Add an attack animation with a fast strike"
Approach:
User Request:
"Animate the character but keep the background static"
Approach:
2 frames, ping-pong, slow timing (400-500ms)
4 frames, forward, even timing (100ms)
6-8 frames, forward, faster timing (60-80ms)
5-6 frames, forward, variable timing
Cannot delete last frame:
Invalid frame numbers:
Tag frame range errors:
You've successfully used this Skill when:
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.