assets-modify

Modify Unity asset files via HTTP API using assetRef and content.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Modifying Unity asset files across a project is error-prone and risky. This Skill provides a controlled workflow: inspect the asset data with assets-get-data, then apply updates to assets only inside the Assets/ folder, disallowing changes in Packages/.

Core Features & Use Cases

  • Inspect asset structure with assets-get-data before applying changes.
  • Enforce asset edits to the Assets/ folder only, preventing edits in Packages/ or other restricted paths.
  • Apply asset updates via a deterministic HTTP API using an assetRef and serialized content.

Quick Start

Inspect the asset with assets-get-data, then invoke assets-modify with an assetRef and new content to update the asset in the Assets/ folder.

Frequently Asked Questions about assets-modify

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

FAQPage Schema
How do I safely modify Unity asset files via API without breaking project references?

To safely modify Unity asset files via API, inspect the asset structure first, then apply updates using an explicit asset reference like instanceID, assetPath, or assetGuid alongside a serialized content payload through a deterministic HTTP workflow.

Can I use an automation API to update Unity assets inside the Packages folder?

No, you cannot use this API to update Unity assets inside the Packages folder. The modification workflow is strictly restricted to the Assets/ folder, disallowing any changes to restricted paths to ensure project stability.

What's the best way to apply serialized content updates to a targeted Unity asset?

The best way to apply serialized content updates to a Unity asset is to provide an explicit assetRef (instanceID, assetPath, or assetGuid) and the new content payload to the HTTP API, enforcing a deterministic workflow with defined input and output schemas.

Do I need to inspect asset structure before modifying Unity assets through an API?

Yes, you need to inspect the asset structure before modifying Unity assets. The controlled workflow requires checking the asset data beforehand to ensure the serialized content payload matches the target asset's structure.

Why does modifying Unity assets programmatically require explicit asset references?

Modifying Unity assets programmatically requires explicit asset references like instanceID, assetPath, or assetGuid to guarantee deterministic targeting. This prevents accidental modifications to incorrect files and ensures the HTTP API applies updates to the exact intended asset.