Spine Multi-Skin Export Checklist: Names, Textures, and Handoff

The AI-generated cover is a concept illustration of visual variants. It is not a workbench screenshot or evidence of an exported character package.

You have created several appearances from one character template. What should you check after downloading a multi-skin package? Opening the ZIP is only the first step: mismatched skin names, files from older exports, and an untested second appearance can still cause a difficult handoff.

This checklist divides the Tooliva Spine Workbench workflow into preparation, downloaded-file checks, and project validation. It is a handoff method, not a claim that a particular engine integration has already been tested.

Multiple skins do not mean merging arbitrary character files

Spine skins let a skeleton's animations work with different attachment combinations. See the official Skins documentation for the underlying setup. Similar-looking artwork does not establish that two characters share compatible skeletons and motion structures.

Tooliva's current illustrated Spine Workbench guide selects completed resources belonging to the same template for a multi-skin export. Confirm template origin and resource status before planning that export. Consult the current interface for any other supported workflow rather than assuming different templates can be combined.

Create a small handoff record for each appearance

Do not wait until after downloading to guess which image belongs to which resource. Record the template, resource name, intended exported skin name, and motions you plan to inspect. The following fields are a suggested team record, not an import format required by the workbench:

• Template: a name or identifier that lets you find the source template.
• Resource: the actual completed resource you selected, rather than a vague note such as “red character.”
• Exported skin name: the exact name entered in the interface.
• Validation motion: an action actually available in that template; do not assume every template has an attack or weapon animation.
• Export batch: a date or internal batch label that separates this package from earlier versions.

For example, hero_teal and hero_rust could identify two appearances in your internal record. These are optional naming examples, not mandatory Tooliva rules. Prefer clear, distinct names. When integrating the result, use the names in the actual exported data rather than inferring them from thumbnail order.

Follow the current workbench export sequence

1. Prepare the resources in Spine Workbench and inspect each appearance in animation preview.
2. Mark the resources you intend to export as complete, then open the multiple-skins export option.
3. Select the completed resources you need from the same template.
4. Check their exported skin names and the summary before confirming the export.

This sequence comes from the current public guide. Available actions and costs follow the live interface. It does not establish that arbitrary resources can be combined or that every template offers the same motions.

Keep the files from one export batch together

The package demonstrated in the tutorial contains shared JSON, an atlas, and PNG images for the skins. That describes the demonstrated workflow, not a requirement to rename every package to a fixed set of filenames. Keep the untouched ZIP and inspect the actual files and references.

1. Extract into a new folder. Avoid overwriting an older export and accidentally loading new data with an old texture.
2. Compare against the handoff record. Check that the intended resources and skin names are represented in the actual result.
3. Check image references. Confirm that images referenced by the atlas exist at the expected paths. Pay attention to letter case and relative locations; the presence of some PNG in a folder does not prove the reference is correct.
4. Preserve names unless you update references too. Renaming one file without checking its consumers can create a loading issue unrelated to the artwork.
5. Keep a batch baseline. Separate modified working copies from the original export so a problem can be reproduced against a known package.

Validate every planned skin in the target project

Confirm the skin names the integration actually uses, then select each intended appearance. Compare the same available motion across skins and inspect the head, limbs, clothing overlap, and any relevant grip position. A template without a weapon does not need a fictional weapon check.

Change one condition at a time: hold the motion constant while switching skins, then hold the skin constant while testing other planned motions. Record the skin, motion, and stage where an issue appears. That is more useful than handing someone a note saying only “the animation is broken.”

If the data cannot be read, check the export format and runtime version as well. Spine's versioning guidance requires matching major and minor versions between the exporting editor and Spine Runtimes. This article does not establish a specific version for every Tooliva export. Inspect the actual export information and your target engine's integration requirements before deciding to upgrade anything.

Narrow problems by their symptoms

• An expected skin is missing from the list: check whether that resource was selected, whether the recorded name is correct, and whether the project loaded the intended batch.
• One skin has missing or incorrect images: inspect references, paths, and batch consistency, then compare that resource's preview and export. Do not replace the entire package as the first step.
• The resting pose looks right but motion exposes a bad connection: compare the same action in the workbench and identify the affected part before investigating calibration, cutout boundaries, or the artwork itself.
• No skin plays correctly: investigate data loading, runtime requirements, and integration configuration before deciding that every appearance needs to be redrawn.

These are troubleshooting priorities, not unique diagnoses for every error. For the earlier asset-preparation stage, see the difference between sprite frames and character parts.

What counts as a completed handoff?

Mark the handoff as passed when the planned resources and skin names match, the batch's files and references are intact, and every intended appearance has been checked in the agreed motions with results recorded. Downloading, file presence, and successful project validation are separate milestones.

For the actual control locations, use the illustrated workbench guide before starting your export.