This skill should be used when the user asks to "make a game", "build a game", "generate a game", or wants to generate or update a complete Godot game from a natural language description. --- # Game Generator — Orchestrator Generate and update Godot games from natural language. ## Capabilities Read each sub-file from `${CLAUDE_SKILL_DIR}/` when you reach its pipeline stage. | File | Purpose | |------|---------| | `visual-target.md` | Generate reference image anchoring art direction | | `decomposer.md` | Decompose game into a development plan (`PLAN.md`) | | `scaffold.md` | Design architecture and produce compilable Godot skeleton | | `asset-planner.md` | Decide what assets the game needs within a budget | | `asset-gen.md` | Generate PNGs (xAI Grok) and GLBs (Tripo3D) from prompts | | `rembg.md` | Background removal guide — read before any rembg operation | | `android-build.md` | Android APK export — read when user requests an Android build | ## Pipeline ``` User request | +- Check if PLAN.md exists (resume check) | +- If yes: read PLAN.md, STRUCTURE.md, MEMORY.md -> skip to task execution | +- If no: continue with fresh pipeline below | +- Generate visual target -> reference.png + ASSETS.md (art direction only) +- Decompose into tasks -> PLAN.md +- Design architecture -> STRUCTURE.md + project.godot + stubs | +- If budget provided (and no asset tables in ASSETS.md): | +- Plan and generate assets -> ASSETS.md + updated PLAN.md with asset assignments | +- For every task in PLAN.md: | +- Set `**Status:** pending` | +- Fill `**Targets:**` with concrete project-relative files expected to change | (e.g. scenes/main.tscn, scripts/player_controller.gd, project.godot) | inferred from task text + scene/script mappings in STRUCTURE.md | +- Show user a concise plan summary (game name, numbered task list) | +- Find next ready task (pending, deps all done) +- While a ready task exists: | +- Update PLAN.md: mark task status -> in_progress | +- Skill(skill="go
Skill files are scattered across GitHub and communities, difficult to search, and hard to evaluate. SkillWink organizes open-source skills into a searchable, filterable library you can directly download and use.
We provide keyword search, version updates, multi-metric ranking (downloads / likes / comments / updates), and open SKILL.md standards. You can also discuss usage and improvements on skill detail pages.
Sort by downloads/likes/comments/updated to find higher-quality skills.
4. Which import methods are supported?
Upload archive: .zip / .skill (recommended)
Upload skills folder
Import from GitHub repository
Note: file size for all methods should be within 10MB.
5. How to use in Claude / Codex?
Typical paths (may vary by local setup):
Claude Code:~/.claude/skills/
Codex CLI:~/.codex/skills/
One SKILL.md can usually be reused across tools.
6. Can one skill be shared across tools?
Yes. Most skills are standardized docs + assets, so they can be reused where format is supported.
Example: retrieval + writing + automation scripts as one workflow.
7. Are these skills safe to use?
Some skills come from public GitHub repositories and some are uploaded by SkillWink creators. Always review code before installing and own your security decisions.
8. Why does it not work after import?
Most common reasons:
Wrong folder path or nested one level too deep
Invalid/incomplete SKILL.md fields or format
Dependencies missing (Python/Node/CLI)
Tool has not reloaded skills yet
9. Does SkillWink include duplicates/low-quality skills?
We try to avoid that. Use ranking + comments to surface better skills: