Skip to content
Back to search

ai-game-art-pipeline-skill

Agent skill from Y Build for turning AI images and videos into playable game art assets

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/ybuild-ai--ai-game-art-pipeline-skill/badge.svg)](/listings/ybuild-ai--ai-game-art-pipeline-skill)

HTML

<a href="/listings/ybuild-ai--ai-game-art-pipeline-skill"><img src="/api/listings/ybuild-ai--ai-game-art-pipeline-skill/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Recommended, if you use the Agent Skills installer:

npx skills add ybuild-ai/ai-game-art-pipeline-skill --skill ai-game-art-pipeline -g

Manual Codex install:

git clone https://github.com/ybuild-ai/ai-game-art-pipeline-skill.git ~/.codex/skills/ai-game-art-pipeline

Manual Claude Code install:

git clone https://github.com/ybuild-ai/ai-game-art-pipeline-skill.git ~/.claude/skills/ai-game-art-pipeline

Then ask your agent for tasks like:

- "Use the AI game art pipeline skill to plan a 2D action RPG sprite pipeline." - "Generate prompts and post-processing steps for a combat sprite sheet." - "Turn a cinematic ultimate video into runtime frames and code-owned hit logic." - "Audit these game assets for mobile runtime shipping risks."

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

SKILL.md · Manifest · 82 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. ---
  2. name: ai-game-art-pipeline
  3. 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.
  4. ---
  5. # AI Game Art Pipeline
  6. Use this skill when a user wants to generate, plan, debug, or package game art that must run in an actual game runtime.
  7. 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`.
  8. ## Core Rule
  9. Pick the pipeline by runtime job, not by model hype.
  10. | Runtime job | Pipeline |
  11. |---|---|
  12. | Static props, items, FX icons | Image model + style refs + removable background |
  13. | Existing/brand character | Reuse canonical sprite sheets before regenerating |
  14. | Combat character animation | Keyframe-first + 2D grid + post-processing + curation |
  15. | Walk/run/body mechanics | Prefer video motion reference; use 3D skeleton only when cleanup is acceptable |
  16. | Ambient loops | Video model -> extracted frames |
  17. | Cinematic ultimate / boss intro | Full-screen video-to-frames + code-driven hit logic |
  18. | Runtime feel | Deterministic code: hit pause, shake, particles, trails, SFX |
  19. ## Default Workflow
  20. 1. Identify the runtime job and target engine.
  21. 2. Check whether canonical assets already exist.
  22. 3. Pick one scenario reference below.
  23. 4. Generate the smallest useful vertical slice, not the full asset set.
  24. 5. Post-process with deterministic scripts.
  25. 6. Preview at target size and target device.
  26. 7. Iterate surgically: rerun one animation, reprocess raw output, or repack frames.
  27. ## Scenario References
  28. Read only the relevant file:
  29. - `references/static-assets.md` — props, icons, items, simple monsters, canonical asset reuse.
  30. - `references/battle-sprites.md` — keyframe-first combat sprite sheets, 2D grids, anchors, contact sheets.
  31. - `references/motion-video.md` — 3D skeleton pitfalls, video motion references, Veo/Seedance-style video-to-frames, cinematic ultimates.
  32. - `references/backgrounds.md` — level backgrounds, master-first parallax, outpaint chains, mobile texture limits.
  33. - `references/runtime-shipping.md` — formats, compression, CDN layout, audio/SFX, runtime QA.
  34. ## Bundled Scripts
  35. Scripts are local utilities only. They do not call model APIs.
  36. - `scripts/provider_stub.py` — adapter interface the user can implement for their provider.
  37. - `scripts/chroma_key_magenta.py` — remove magenta background from generated sheets/icons.
  38. - `scripts/sheet_contact.py` — make numbered contact sheets for curation.
  39. - `scripts/extract_video_frames.py` — extract/resize video frames for runtime texture sequences.
  40. ## Provider Adapters
  41. Do not write a full vendor SDK unless the user explicitly asks for one. Prefer a thin adapter around `scripts/provider_stub.py` so credentials, endpoints, retries, billing, and model choices stay in the user's project.
  42. If the user wants examples, point them to `examples/providers/README.md` and adapt only the minimal file they need:
  43. - fake/local provider for testing the pipeline without model calls.
  44. - generic image HTTP provider for a user's image-generation proxy.
  45. - generic async video HTTP provider for a user's video-generation proxy.
  46. ## Output Standard
  47. When using this skill, produce:
  48. - A concise pipeline choice and why.
  49. - The exact assets to generate or reuse.
  50. - Prompt constraints if model generation is needed.
  51. - Post-processing commands/scripts.
  52. - Runtime packaging notes: dimensions, format, anchor, frame rate, texture limits.
  53. - QA checklist for the target device.
  54. ## Hard Warnings
  55. - Do not regenerate a known character if a canonical sheet exists.
  56. - Do not use 1xN horizontal strips for complex combat poses; use 2D grids.
  57. - Do not let cinematic video own gameplay semantics. Damage, hitboxes, target tracking, cooldown, and SFX belong in code.
  58. - Do not ship giant backgrounds because they look fine on desktop. Check mobile texture limits.
  59. - Do not treat AI output as final. The production asset is the generated image plus cleanup, anchors, timing, compression, and runtime test.
README.md · README · 185 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. <div align="center">
  2. <img src="media/pipeline-map.jpg" alt="AI game art pipeline map" width="100%">
  3. </div>
  4. # AI Game Art Pipeline Skill
  5. > Provider-neutral workflows for turning AI images and videos into playable game assets.
  6. [![Stars](https://img.shields.io/github/stars/ybuild-ai/ai-game-art-pipeline-skill?style=flat&color=yellow)](https://github.com/ybuild-ai/ai-game-art-pipeline-skill/stargazers)
  7. [![License](https://img.shields.io/github/license/ybuild-ai/ai-game-art-pipeline-skill?style=flat)](LICENSE)
  8. [![Last Commit](https://img.shields.io/github/last-commit/ybuild-ai/ai-game-art-pipeline-skill?style=flat)](https://github.com/ybuild-ai/ai-game-art-pipeline-skill/commits/main)
  9. [![Skill](https://img.shields.io/badge/Agent%20Skill-Codex%20%2F%20Claude%20Code%20%2F%20Cursor-blue)](SKILL.md)
  10. [![Y Build](https://img.shields.io/badge/Y%20Build-ybuild.ai-111111)](https://ybuild.ai)
  11. This skill helps agents plan, generate, clean, package, and QA game-runtime art assets: sprites, icons, backgrounds, video-to-frames animation, cinematic ultimates, anchors, compression, and runtime checks.
  12. Created by [Y Build](https://ybuild.ai), an AI agent platform for building, launching, and growing apps.
  13. It is not a prompt pack or a model leaderboard. The point is to ship assets that survive a real game loop.
  14. ## Why This Exists
  15. Most AI game art demos stop at a beautiful image. Games need stricter things:
  16. - Transparent sprites that do not jitter.
  17. - Animation frames with stable identity and readable silhouettes.
  18. - Backgrounds that fit mobile GPU texture limits.
  19. - Cinematic effects that look rich without owning gameplay logic.
  20. - Audio, hit timing, anchors, and compression that hold up in runtime.
  21. The core rule:
  22. > Pick the pipeline by runtime job, not by model hype.
  23. ## Install
  24. Recommended, if you use the Agent Skills installer:
  25. ```bash
  26. npx skills add ybuild-ai/ai-game-art-pipeline-skill --skill ai-game-art-pipeline -g
  27. ```
  28. Manual Codex install:
  29. ```bash
  30. git clone https://github.com/ybuild-ai/ai-game-art-pipeline-skill.git ~/.codex/skills/ai-game-art-pipeline
  31. ```
  32. Manual Claude Code install:
  33. ```bash
  34. git clone https://github.com/ybuild-ai/ai-game-art-pipeline-skill.git ~/.claude/skills/ai-game-art-pipeline
  35. ```
  36. Then ask your agent for tasks like:
  37. - "Use the AI game art pipeline skill to plan a 2D action RPG sprite pipeline."
  38. - "Generate prompts and post-processing steps for a combat sprite sheet."
  39. - "Turn a cinematic ultimate video into runtime frames and code-owned hit logic."
  40. - "Audit these game assets for mobile runtime shipping risks."
  41. ## What You Get
  42. | Runtime job | Recommended route |
  43. |---|---|
  44. | Static props, items, FX icons | Image model + style refs + removable background |
  45. | Existing or brand character | Reuse canonical sprite sheets before regenerating |
  46. | Combat character animation | Keyframe-first + 2D grid + post-processing + curation |
  47. | Walk/run/body mechanics | Prefer video motion reference; use 3D skeleton only when cleanup is acceptable |
  48. | Ambient loops | Video model -> extracted frames |
  49. | Cinematic ultimate / boss intro | Full-screen video-to-frames + code-driven hit logic |
  50. | Runtime feel | Deterministic code: hit pause, shake, particles, trails, SFX |
  51. ## Visual Examples
  52. | Combat sprites | Cinematic ultimate |
  53. |---|---|
  54. | ![Battle sprite grid](media/battle-sprite-grid.jpg) | ![Seedance awakening frames](media/seedance-awakening-frames.jpg) |
  55. | Motion reference tradeoff | Pipeline map |
  56. |---|---|
  57. | ![3D skeleton versus video motion reference](media/skeleton-vs-video-motion.jpg) | ![Pipeline map](media/pipeline-map.jpg) |
  58. ## Repository Layout
  59. ```text
  60. SKILL.md
  61. references/
  62. static-assets.md
  63. battle-sprites.md
  64. motion-video.md
  65. backgrounds.md
  66. runtime-shipping.md
  67. scripts/
  68. provider_stub.py
  69. chroma_key_magenta.py
  70. sheet_contact.py
  71. extract_video_frames.py
  72. examples/
  73. prompts.md
  74. batch_generation_example.py
  75. providers/
  76. README.md
  77. minimal_provider_example.py
  78. http_image_provider_example.py
  79. http_video_provider_example.py
  80. media/
  81. pipeline-map.jpg
  82. battle-sprite-grid.jpg
  83. seedance-awakening-frames.jpg
  84. skeleton-vs-video-motion.jpg
  85. ```
  86. ## Bundled Scripts
  87. Scripts are local utilities only. They do not contain API keys, endpoints, private paths, or vendor SDK code.
  88. | Script | Purpose |
  89. |---|---|
  90. | `scripts/provider_stub.py` | Adapter interface users can implement for their own image/video provider |
  91. | `scripts/chroma_key_magenta.py` | Remove solid magenta backgrounds from generated assets |
  92. | `scripts/sheet_contact.py` | Build numbered contact sheets for sprite curation |
  93. | `scripts/extract_video_frames.py` | Extract and resize video frames for runtime texture sequences |
  94. Examples:
  95. ```bash
  96. python scripts/chroma_key_magenta.py input.png output.png
  97. python scripts/sheet_contact.py frames/ contact.png --cols 6
  98. python scripts/extract_video_frames.py ultimate.mp4 frames/ --fps 14 --start 0.6 --duration 3.6 --width 1280
  99. ```
  100. ## Provider Adapters, Not SDKs
  101. The skill intentionally does not ship a real image/video SDK. Model APIs change quickly, and users should own credentials, endpoints, model names, retry policy, and billing behavior.
  102. Instead, the repo includes thin adapter examples:
  103. | Example | Use it when |
  104. |---|---|
  105. | `examples/providers/minimal_provider_example.py` | You want a fake provider to test the pipeline shape locally |
  106. | `examples/providers/http_image_provider_example.py` | You have an image-generation HTTP proxy that returns a URL or base64 image |
  107. | `examples/providers/http_video_provider_example.py` | You have an async video-generation HTTP proxy with job polling |
  108. | `examples/batch_generation_example.py` | You want to turn a small art plan into provider requests |
  109. Read [examples/providers/README.md](examples/providers/README.md) before wiring a real provider.
  110. ## Quick Workflow
  111. 1. Identify the runtime job and target engine.
  112. 2. Check whether canonical assets already exist.
  113. 3. Pick the smallest useful vertical slice.
  114. 4. Generate or reuse source visuals.
  115. 5. Post-process with deterministic scripts.
  116. 6. Preview at target size and target device.
  117. 7. Iterate surgically: rerun one animation, reprocess raw output, or repack frames.
  118. ## Good Fit / Bad Fit
  119. Good fit:
  120. - 2D action RPGs, tactics games, card battlers, mobile games, UI-heavy games.
  121. - Teams using image/video generation but needing runtime-ready assets.
  122. - Agents that can run local scripts and edit asset pipelines.
  123. Bad fit:
  124. - One-off marketing art.
  125. - Pure concept-art exploration with no runtime target.
  126. - Fully automated "make my whole game art set" workflows with no curation.
  127. ## Contributing
  128. Contributions are welcome. The most useful additions are:
  129. - New provider adapters that keep credentials outside the repo.
  130. - Runtime preview templates for PixiJS, Canvas, Godot, Unity, SpriteKit, or web games.
  131. - More post-processing utilities for trimming, anchors, packing, and QA.
  132. - Real pipeline notes from shipped projects.
  133. See [CONTRIBUTING.md](CONTRIBUTING.md).
  134. ## License
  135. MIT. See [LICENSE](LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.