assets-copy

Copy Unity assets between paths and refresh the AssetDatabase.

1|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/lightvu25/Echoes --skill assets-copy-lightvu25
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: assets-copy
Source: https://github.com/lightvu25/Echoes/tree/main/SKILLS/assets-copy
Command: npx skills add https://github.com/lightvu25/Echoes --skill assets-copy-lightvu25

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Copy assets from a source path to a destination path and refresh the AssetDatabase after copying to ensure the project remains up-to-date.

Core Features & Use Cases

  • Copy assets between specified paths within a Unity project.
  • Ensure AssetDatabase.Refresh() runs after copying to reflect changes in the editor.
  • Useful for asset relocation, backups, and batch duplication within Unity projects.

Quick Start

Copy an asset from a given source path to a destination path and refresh the editor after copying.

Frequently Asked Questions about assets-copy

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

FAQPage Schema
How do I copy a Unity asset to another path and refresh the AssetDatabase?

To copy a Unity asset, provide sourcePaths and destinationPaths inputs, and the script copies the asset between those locations, then executes AssetDatabase.Refresh() to ensure the editor reflects the updated project files.

Why does Unity not show my copied asset in the Project window?

Unity does not show copied assets because the AssetDatabase has not been refreshed. You must execute AssetDatabase.Refresh() after copying files to a new path so the editor recognizes and imports the new assets.

Can I automate batch asset duplication in Unity using path inputs?

Yes, you can automate batch asset duplication by passing multiple sourcePaths and destinationPaths inputs to the script, which copies each asset and triggers AssetDatabase.Refresh() to finalize the bulk relocation workflow.

What is the best way to relocate Unity assets for project backups?

The best way to relocate Unity assets for backups is to copy them from a source path to a destination path and run AssetDatabase.Refresh() afterward, ensuring the project database stays synchronized without manual reimporting.

Does this asset copy workflow require any specific Unity editor components?

No specific editor components are required, but the workflow operates within a Unity project environment and relies on the built-in AssetDatabase API to copy files and refresh the editor state.

When should I not use AssetDatabase.Refresh() after copying assets?

You should avoid calling AssetDatabase.Refresh() unnecessarily if no files were actually copied, as it triggers a full project scan and can cause editor delays when handling large Unity projects without asset changes.