Introduction to the Asset Library CLI
Understand how the Asset Library CLI finds and imports individual Asset Store assets, which assets you can use, and how asset versions and render pipeline variants work.
Read time 3 minutesLast updated a day ago
The Asset Library CLI works with individual assets, such as a single model, texture, or sound, rather than whole Asset Store packages. You can check an asset's details before you import it, and import only the files that asset needs.
This page explains how individual assets relate to Asset Store packages, which assets you can import, how to identify a specific asset version, and how to use the CLI from coding agents and continuous integration (CI) pipelines.
To install the CLI, refer to Install the Asset Library CLI.
Asset availability and ownership
The commands you can use with an asset depend on whether the asset is free and whether you own its package:
- and
searchwork with free and paid assets.show - ,
import, anddownloadwork with free assets, and with assets from paid packages you own.package
Ownership applies to the whole package. If you own a package, you own every asset in it. To use an asset from a paid package you don't own, buy the package in the Asset Store, and then run the command again. The command prints the package URL.
showThe Asset Library CLI uses your Unity organization to check which assets you own.
Asset IDs and versions
Commands that act on one asset take an asset ID in one of the following forms:
- : uses the latest version of the asset.
assetId - : uses the specified version of the asset.
assetId@versionId
By default, the command prints each ID in the form. To print IDs in the form, add the option. An ID that you copy from those results uses that specific version.
searchassetIdassetId@versionId--versionsRender pipeline variants
Some assets include a separate variant for each render pipeline. For these assets, the , , and commands require the option with one of the following values: , , or .
importdownloadpackage--render-pipelineurphdrpbuiltinAutomation with coding agents and CI
The Asset Library CLI supports automated use from coding agents and CI pipelines:
- Use or
--format jsonfor structured output.--format ndjson - Use so that a missing value causes an error instead of a prompt.
--non-interactive - Use with
--dry-runandimportto review changes before the CLI writes any files.download - Use IDs so that repeated runs get the same files.
assetId@versionId - Run to give your coding agent the Unity CLI skill.
unity skill install <client>
To list the options of a command, run . For the options that all commands accept, refer to Asset Library CLI command reference.
unity assetlibrary <command> --help