How do I install the Extract Rpg Asset Board skill?

Run npx skillmds@latest add arcdodo/extract-rpg-asset-board in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Extract Rpg Asset Board safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Extract Rpg Asset Board?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Extract Rpg Asset Board free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Extract Rpg Asset Board?

arcdodo (@arcdodo) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Extract Rpg Asset Board by arcdodo — Agent Skill

Name: Extract Rpg Asset Board
Rating: 4.2 (5 reviews)
Author: arcdodo

Extract Rpg Asset Board

Split RPG game-asset overview images, sprite boards, tileset presentation sheets, or AI-generated asset boards into individually named game-ready PNG files. Use when Codex needs to detect and crop multiple assets from one image, preserve rectangular terrain tiles, remove a flat or near-flat background from props, create transparent cutouts, organize outputs, generate a manifest/contact sheet, or prepare assets for RPG Maker, Godot, Unity, or similar engines.

arcdodo Updated Sep 22, 2026

File contents

Extract RPG Asset Board

Convert one RPG asset-board image into reviewed, individually named PNG assets. Use the bundled script for deterministic image processing; use visual judgment to review candidate boxes and outputs.

Workflow

Inspect the source image and identify:
- rectangular terrain/path tiles that must retain their painted background;
- props/buildings/decorations that should become transparent;
- nearby objects that belong together and should share one crop.
Locate a Python runtime with Pillow and numpy. Prefer the workspace dependency runtime when available.
Generate initial candidate boxes:

python scripts/rpg_asset_board.py detect SOURCE.png --layout layout.json

Review layout.detect-preview.jpg and edit layout.json.
- Give every asset a descriptive lowercase id.
- Set type to tile or prop.
- Merge related fragments by replacing them with one enclosing box.
- Set keep_largest_component: true only when a prop crop contains disconnected neighboring art.
- Delete false positives and expand boxes that clip shadows or painted edges.
Extract the assets:

python scripts/rpg_asset_board.py extract SOURCE.png --layout layout.json --out OUTPUT_DIR --clean --zip

Inspect preview_contact_sheet.jpg on a checkerboard.
Fix layout boxes or alpha thresholds and rerun until no asset is clipped, contaminated, empty, or missing.

Output Contract

Produce:

tiles/*.png: rectangular terrain and path pieces with their painted ground intact
props/*.png: tightly cropped RGBA PNG files
manifest.json: IDs, types, sizes, source boxes, and processing settings
preview_contact_sheet.jpg: visual QA sheet
optional .zip archive

Do not claim success before inspecting the contact sheet and confirming the validation summary reports zero errors.

Processing Guidance

Prefer one logical game object per output, not one connected component per output.
Keep shadows when they visually ground props, unless the user asks for shadowless assets.
Treat doors/windows designed to overlay buildings as props.
Treat square/rectangular grass, dirt, edge, and path pieces as tiles.
Do not force a grid size unless the user names a target engine and tile size.
For complex textured backgrounds, hair-like edges, translucent materials, or overlapping assets, explain that deterministic background removal may need manual masking or image editing.

See references/layout-format.md for the layout schema and tuning fields.

---name: extract-rpg-asset-boarddescription: Split RPG game-asset overview images, sprite boards, tileset presentation sheets, or AI-generated asset boards into individually named game-ready PNG files. Use when Codex needs to detect and crop multiple assets from one image, preserve rectangular terrain tiles, remove a flat or near-flat background from props, create transparent cutouts, organize outputs, generate a manifest/contact sheet, or prepare assets for RPG Maker, Godot, Unity, or similar engines.---# Extract RPG Asset BoardConvert one RPG asset-board image into reviewed, individually named PNG assets. Use the bundledscript for deterministic image processing; use visual judgment to review candidate boxes and outputs.## Workflow1. Inspect the source image and identify: - rectangular terrain/path tiles that must retain their painted background; - props/buildings/decorations that should become transparent; - nearby objects that belong together and should share one crop.2. Locate a Python runtime with `Pillow` and `numpy`. Prefer the workspace dependency runtime when available.3. Generate initial candidate boxes:```bashpython scripts/rpg_asset_board.py detect SOURCE.png --layout layout.json```4. Review `layout.detect-preview.jpg` and edit `layout.json`. - Give every asset a descriptive lowercase `id`. - Set `type` to `tile` or `prop`. - Merge related fragments by replacing them with one enclosing box. - Set `keep_largest_component: true` only when a prop crop contains disconnected neighboring art. - Delete false positives and expand boxes that clip shadows or painted edges.5. Extract the assets:```bashpython scripts/rpg_asset_board.py extract SOURCE.png --layout layout.json --out OUTPUT_DIR --clean --zip```6. Inspect `preview_contact_sheet.jpg` on a checkerboard.7. Fix layout boxes or alpha thresholds and rerun until no asset is clipped, contaminated, empty, or missing.## Output ContractProduce:- `tiles/*.png`: rectangular terrain and path pieces with their painted ground intact- `props/*.png`: tightly cropped RGBA PNG files- `manifest.json`: IDs, types, sizes, source boxes, and processing settings- `preview_contact_sheet.jpg`: visual QA sheet- optional `.zip` archiveDo not claim success before inspecting the contact sheet and confirming the validation summary reportszero errors.## Processing Guidance- Prefer one logical game object per output, not one connected component per output.- Keep shadows when they visually ground props, unless the user asks for shadowless assets.- Treat doors/windows designed to overlay buildings as props.- Treat square/rectangular grass, dirt, edge, and path pieces as tiles.- Do not force a grid size unless the user names a target engine and tile size.- For complex textured backgrounds, hair-like edges, translucent materials, or overlapping assets, explain that deterministic background removal may need manual masking or image editing.See [references/layout-format.md](references/layout-format.md) for the layout schema and tuning fields.

Frequently asked questions