AI Game Art Pipeline skill
A skill that takes an agent from a generated picture to a game asset: sprites, video-to-frames animation and pre-release checks
- 306 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The agent runs local Python scripts that read and write image and video files in your project
- Through provider adapters the skill sends requests to paid generation APIs, and keys and costs stay on your side
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/ai-game-art-pipelineDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The agent runs local Python scripts that read and write image and video files in your project
- Through provider adapters the skill sends requests to paid generation APIs, and keys and costs stay on your side
This is third-party code. Review the repository files before installing.
What it does
AI Game Art Pipeline teaches an agent to bring generated graphics to assets that work in a game. The skill picks a route per task, from static props and icons to combat sprites and boss-ultimate cutscenes. Its table gives each task a method: combat animation is built from keyframes and a 2D grid, and a cutscene is converted from video to frames. References live in separate topic files, from static assets to shipping into the game, and the agent reads only the relevant one. Four local Python scripts ship with it. They plug in your own model provider through an adapter stub, remove a magenta background, build contact sheets and cut video into frames. The skill is not tied to a model and contains no SDK. Keys, endpoints and retries stay in your project, and the examples include a fake provider for testing the pipeline without calling any model. It targets the PixiJS and Canvas web engines as well as Unity, Godot and SpriteKit.
Who it is for. For indie developers and teams building 2D games with generative art who want assets ready to run on mobile devices.
Good fit when
- You need to plan a sprite pipeline for a 2D action or card game and pick a method per asset type
- A generated sprite sheet needs its magenta background removed with chroma_key_magenta.py
- A cutscene video must become a frame sequence for textures: `python scripts/extract_video_frames.py ultimate.mp4 frames/ --fps 14`
- Before release you want to check assets against mobile limits: texture size, compression, anchors
- You need a numbered contact sheet from sheet_contact.py to curate animations
Not a fit when
- You need a one-off marketing image: the skill targets game runtime and does not touch promo art
- You are only exploring concept art with no target engine and no runtime requirements
- You expect a fully automatic set of all game art: the skill assumes a human curates the results
Example request
Use the AI Game Art Pipeline skill to plan a combat sprite pipeline for a 2D RPG and prepare prompts and post-processing stepsLimitations
- The skill does not call models itself: generation needs your own image or video provider, plugged in through an adapter based on provider_stub.py.
- The scripts run locally; cutting video needs Python and video tooling on your machine.
- The result needs human curation: the skill describes the pipeline and checks but does not guarantee the quality of every animation.
- Adapter examples show the request shape and do not replace setting up keys, limits and billing for your provider.
How to disable. Delete the skill folder: `~/.claude/skills/ai-game-art-pipeline` or `~/.codex/skills/ai-game-art-pipeline`. If you installed through `npx skills`, use that tool's remove command.
FAQ
How do I install AI Game Art Pipeline in Claude Code?
Run `npx skills add ybuild-ai/ai-game-art-pipeline-skill --skill ai-game-art-pipeline -g`. By hand the skill installs by cloning the repository into `~/.claude/skills/ai-game-art-pipeline`.
Which model should I use to generate art for the skill?
Any. You connect your own provider through an adapter modeled on scripts/provider_stub.py, and examples/providers has a fake provider, an image HTTP proxy and an async video proxy.
How do I remove the background from a generated sprite?
Have the model draw on a solid magenta background and run `python scripts/chroma_key_magenta.py input.png output.png`. The script removes the solid magenta background.
How do I turn a cutscene video into frames for a game?
Use `python scripts/extract_video_frames.py ultimate.mp4 frames/ --fps 14 --start 0.6 --duration 3.6 --width 1280`. The options set frame rate, start, duration and width. The skill advises keeping hit logic in game code.
Does the skill suit character walk and run cycles?
Yes. For body mechanics the skill recommends video as a motion reference and a 3D skeleton only when later cleanup is acceptable. Details are in references/motion-video.md.
Discussion
No questions or reviews yet.
Related
SkillsA skill that turns your photo or description into a hand-drawn character and uses it for diagrams, knowledge cards and slides
Codex skills for 2D sprites, animation sheets and layered game maps from a prompt, exported to PNG, GIF and Godot
Twelve skills that make an agent build single-file HTML animations: slides, protocol diagrams, architecture diagrams and demos for screen recording
Two skills for generative video and images: video writes Seedance, Kling and Veo prompts by dramaturgy rules, image picks the model and its syntax
A skill that writes prompts for video, image and music generation on 14 platforms and can submit them in the browser
Aseprite AI Artist: pixel art through an agent
Aseprite AI Artist
A plugin and MCP server that let an agent draw and animate in your open Aseprite window, with every action undone by one Ctrl+Z
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Repository stars | Main difference |
|---|---|---|---|
| AI Game Art Pipeline (this entry) | no | 306 | |
| Sprite Gen | no | 3,101 | builds sprites from one base image and assembles atlases; this one covers the whole path from picking a route to pre-release checks |
| Agent Sprite Forge | no | 4,633 | Codex skills for sprites and maps exported to PNG, GIF and Godot; this one leans on video to frames, backgrounds and mobile runtime |
README in short
The author starts with the problem: AI art demos end with a pretty picture, while a game needs stable sprites within mobile GPU limits. A separate section lists when the skill fits and when it does not.
README badge
Original SKILL.md
##### SKILL.md 200 --- name: ai-game-art-pipeline description: Provider-neutral open-source skill for planning and producing game-runtime art assets and animation: static props/icons, canonical character sheets, combat sprites, 3D/video motion references, Veo/Seedance-style video-to-frames, cinematic ultimates, backgrounds, FX, SFX, runtime packaging, and QA. Use when building actual game assets for PixiJS/Canvas/Unity/Godot/SpriteKit/etc., not one-off marketing images. --- # AI Game Art Pipeline Use this skill when a user wants to generate, plan, debug, or package game art that must run in an actual game runtime. The skill is provider-neutral. It does not assume any specific API key or vendor SDK. If a model call is needed, use the user's available provider through an adapter or ask them to implement `scripts/provider_stub.py`. ## Core Rule Pick the pipeline by runtime job, not by model hype. | Runtime job | Pipeline | |---|---| | Static props, items, FX icons | Image model + style refs + removable background | | Existing/brand character | Reuse canonical sprite sheets before regenerating | | Combat character animation | Keyframe-first + 2D grid + post-processing + curation | | Walk/run/body mechanics | Prefer video motion reference; use 3D skeleton only when cleanup is acceptable | | Ambient loops | Video model -> extracted frames | | Cinematic ultimate / boss intro | Full-screen video-to-frames + code-driven hit logic | | Runtime feel | Deterministic code: hit pause, shake, particles, trails, SFX | ## Default Workflow 1. Identify the runtime job and target engine. 2. Check whether canonical assets already exist. 3. Pick one scenario reference below. 4. Generate the smallest useful vertical slice, not the full asset set. 5. Post-process with deterministic scripts. 6. Preview at target size and target device. 7. Iterate surgically: rerun one animation, reprocess raw output, or repack frames. ## Scenario References Read only the relevant file: - `references/static-assets.md` — props, icons, items, simple monsters, canonical asset reuse. - `references/battle-sprites.md` — keyframe-first combat sprite sheets, 2D grids, anchors, contact sheets. - `references/motion-video.md` — 3D skeleton pitfalls, video motion references, Veo/Seedance-style video-to-frames, cinematic ultimates. - `references/backgrounds.md` — level backgrounds, master-first parallax, outpaint chains, mobile texture limits. - `references/runtime-shipping.md` — formats, compression, CDN layout, audio/SFX, runtime QA. ## Bundled Scripts Scripts are local utilities only. They do not call model APIs. - `scripts/provider_stub.py` — adapter interface the user can implement for their provider. - `scripts/chroma_key_magenta.py` — remove magenta background from generated sheets/icons. - `scripts/sheet_contact.py` — make numbered contact sheets for curation. - `scripts/extract_video_frames.py` — extract/resize video frames for runtime texture sequences.