instantiate-asset-pack

Import multi-slice asset packs into a scene as grouped Sprite2D and NinePatchRect nodes.

66|4|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/SummerEngine/summer --skill instantiate-asset-pack-summerengine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: instantiate-asset-pack
Source: https://github.com/SummerEngine/summer/tree/main/library/skills/instantiate-asset-pack
Command: npx skills add https://github.com/SummerEngine/summer --skill instantiate-asset-pack-summerengine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a generated asset pack (a bundle of cropped slice PNGs with metadata) into a properly laid-out scene is tedious: you must group composite children, sort paint order, compute offsets, and pick the right node types by hand. This Skill automates that entire layout pass. ## Core Features & Use Cases - Pack-level scene layout: Reads per-slice metadata (bbox, zOrder, isComposite, parentSliceIndex) and emits AddNode/SetProp ops that place every slice correctly. - Composite grouping and paint order: Filters out flat composite previews, groups children under a Node2D parent, and sorts by zOrder so layering renders correctly. - Widget-aware node selection: Maps widget metadata to NinePatchRect, TextureProgressBar, sliders, and toggles, delegating geometry wiring to use-widget-asset. - Use Case: You generated a dungeon UI pack with create-asset-sheet and want the settings panel, buttons, and icons placed in your scene with correct layering in one pass. ## Quick Start Import the dungeon UI pack from my library into the current scene with all slices grouped and layered correctly.

Frequently Asked Questions about instantiate-asset-pack

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I import an asset pack into a Godot scene?

Provide the pack ArtAsset produced by create-asset-sheet and the skill reads each slice's metadata, imports textures via summer_import_from_url, then spawns Sprite2D or NinePatchRect nodes with correct position, z_index, and grouping under a Node2D parent.

How do I lay out a generated UI kit or tile sheet in one pass?

Pass the whole pack rather than individual slices. The skill filters out composite preview slices, groups children by parentSliceIndex, sorts them by zOrder ascending, and emits the full set of scene operations including SaveScene.

What is the difference between instantiate-asset-pack and use-widget-asset?

instantiate-asset-pack handles pack-level layout: grouping composites, paint order, offsets, and naming. use-widget-asset wires individual widget slices, configuring NinePatchRect patch margins or TextureProgressBar geometry from frameMargins.

What happens if my asset pack has no zOrder or isComposite fields?

The skill falls back to slice.zOrder ?? slice.layerIndex ?? packFileIndex for ordering, and slice.isComposite ?? slice.isReference ?? false for compositing. If neither exists on any slice, every slice is treated as standalone and spawned at the origin.

When should I not use instantiate-asset-pack?

Skip it when importing a single slice (use a direct Sprite2D import or use-widget-asset), when generating a new pack (use create-asset-sheet), or when applying a slice as a texture on a 3D mesh.

What happens if a slice fails to import or a name collides?

A failed slice import is skipped with a warning while the rest of the pack continues. Name collisions with existing scene nodes are resolved by appending numeric suffixes like _1 and _2, never by overwriting.