skills.rest
sprillion
sprillionCOMMUNITY
Explore all skills by this author →
GitHub

package-add

Install Unity packages from registry, Git URL, or local path by updating manifest.json.

Updated Feb 4, 2024
Search Tags:#git#unity#dependencies#manifest#package-manager#install#local-path
One-click install
npx skills add https://github.com/sprillion/gem_td --skill package-add-sprillion
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: package-add
Source: https://github.com/sprillion/gem_td/tree/main/SKILLS/package-add
Command: npx skills add https://github.com/sprillion/gem_td --skill package-add-sprillion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Install a package from the Unity Package Manager registry, Git URL, or local path. This operation modifies the project's manifest.json and triggers package resolution. Note: Package installation may trigger a domain reload. The result will be sent after the reload completes. Use 'package-search' tool to search for packages and 'package-list' to list installed packages.

Core Features & Use Cases

  • Install from Unity Registry: Install latest or specific versions of packages from the Unity Package Registry.
  • Git URL support: Install packages directly from Git repositories using URLs (with optional branches/tags).
  • Local path installation: Add packages from local file paths for development workflows.
  • Manifest management: Automatically update manifest.json and trigger package resolution, handling domain reloads transparently.

Quick Start

Provide a packageId (for example com.unity.textmeshpro or a Git URL) to the package-add tool to install a package.

Frequently Asked Questions about package-add

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

FAQPage Schema
How do I install a Unity package from a Git URL or local path?▼

To install a Unity package from a Git URL or local path, update the project's manifest.json to include the source path. This triggers package resolution and automatically handles any necessary domain reloads during installation.

What happens to manifest.json when adding Unity dependencies?▼

When adding Unity dependencies, the manifest.json file is directly modified with the new package identifier. The Unity Package Manager then resolves the newly added dependencies, which may trigger a domain reload before completing.

Can I use this package installation method in CI pipelines?▼

Yes, you can use this package installation method across CI pipelines and manual workflows. It applies to project setup and maintenance by updating manifest.json and triggering package resolution transparently for automated environments.

Why does Unity trigger a domain reload when installing packages?▼

Unity triggers a domain reload during package installation because adding dependencies modifies manifest.json and requires package resolution. The installation result is sent only after this domain reload completes to ensure project stability.

Do I need to validate packageId formats before installing Unity packages?▼

Yes, input formats are validated during Unity package installation to ensure the registry packageId, Git URL, or local path is correct. This prevents errors when updating manifest.json and triggering package resolution.

Related Skills

Explore More Software Engineering Skills→
BekaChkhiroBekaChkhiro
1

pfTeamRemove

Remove a team member from a PlanFlow project via the PlanFlow API.

Community
Intermediate
RakameNouyaRakameNouya

package-add

Automate Unity package installation by modifying manifest.json and triggering resolution.

Community
Intermediate
PackmindHubPackmindHub
306

packmind-create-package

Create Packmind packages via the packmind-cli with name and description.

Official
Advanced
tneztnez
3

install-skill

Install agent skills from local paths, GitHub repositories, or the dot-agents library.

Community
Intermediate