scene-save

Save opened Unity scenes to .unity asset files via HTTP API.

Updated Feb 4, 2024
One-click install
npx skills add https://github.com/sprillion/gem_td --skill scene-save-sprillion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scene-save
Source: https://github.com/sprillion/gem_td/tree/main/SKILLS/scene-save
Command: npx skills add https://github.com/sprillion/gem_td --skill scene-save-sprillion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Saving opened Unity scenes to the asset file can be error-prone when multiple scenes are in flight during development. This Skill automates persisting the currently opened scene(s) to the Unity asset file to ensure consistency between the editor and asset data.

Core Features & Use Cases

  • Save the currently opened scene or a named opened scene to its corresponding Unity asset file.
  • Accept an optional path; if provided, saves to the specified .unity file; if omitted, saves to the existing asset file.
  • Expose an HTTP API endpoint to integrate with automation pipelines (MCP Plugin) for programmatic scene persistence.

Quick Start

Persist the currently opened Unity scene to its asset file using the scene-save tool.

Frequently Asked Questions about scene-save

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

FAQPage Schema
How do I save an opened Unity scene to a .unity asset file programmatically?

Save opened Unity scenes to asset files by invoking the scene-save tool via the MCP Plugin HTTP API at /api/tools/scene-save, passing the openedSceneName and an optional path to persist changes to a .unity file.

When do I need to persist changes for multiple opened Unity scenes?

Persist changes for multiple opened Unity scenes when you have in-flight modifications during development and need to ensure consistency between the editor state and the saved .unity asset data on disk.

Can I specify a custom file path when saving a Unity scene through the HTTP API?

Yes, you can specify a custom file path when saving a Unity scene by providing the path input; if path is null or empty, the scene saves to its existing .unity asset file.

Does the scene-save automation tool work without additional Unity dependencies?

Yes, the scene-save automation tool operates without additional dependencies, using the MCP Plugin HTTP API endpoint to persist opened Unity scenes directly to their corresponding asset files.

What is the best way to automate Unity scene persistence in a development pipeline?

Automate Unity scene persistence by calling the /api/tools/scene-save HTTP API endpoint with openedSceneName and path parameters to save scene modifications to .unity asset files programmatically.

Why does saving multiple opened Unity scenes manually lead to data inconsistency?

Saving multiple opened Unity scenes manually risks data inconsistency because tracking in-flight modifications across the editor is error-prone, whereas automating the save to .unity asset files ensures editor and disk data match.