/uipath-solution

name: uipath-solution
description: "Always invoke for `.uipx` files. UiPath Solution lifecycle via `uip solution`: init/download/restore/pack/publish/deploy/activate/upgrade/upload, projects add|import|remove, resources refresh|add|remove|edit, feeds list, `--feed` / `--personal-workspace`. DIAGNOSE lifecycle failures: pack/publish/deploy/activate errors, stale/missing bindings, unimported/unresolved resources, deploy error codes, `--acknowledge-permanent-deletion` consent, publish name+version/processKey collisions, redeploy blocked by an existing deployment (`deploy upgrade`), feed 'not an available publish location', package not in `packages list`, 'unknown command' after new→init rename. Bundles RPA/Flow/Case/Agents/API Workflow/AppV2 projects in one `.uipx`. Routing: PDD→SDD design & task derivation→uipath-planner; non-solution Orchestrator/IS/resources/auth/traces→uipath-platform; .xaml/.cs→uipath-rpa; .flow→uipath-maestro-flow; .bpmn→uipath-maestro-bpmn; agent.json/.py agents→uipath-agents; standalone coded-app deploy→uipath-coded-apps."
when_to_use: "User mentions .uipx / 'uip solution' / 'pack the solution' / 'publish the solution' / 'deploy the solution' / 'activate' / multi-project / Solution scope / Solution Folder. Fires for 'download/export a solution from Studio Web', 'work on an existing solution', 'migrate a solution to another org/tenant', 'create a new solution', 'add project/resource to solution', 'add a queue/asset/bucket/connection to the solution', 'import a cloud queue/asset', 'edit/remove a resource', 'change a queue/asset field', 'set an asset value in the solution', 'upgrade a deployment to another version', 'change the deployed version without losing my configuration', 'publish/deploy to a folder feed or Personal Workspace', 'which feeds can I publish to'. Also fires to DIAGNOSE solution problems: 'why did my solution pack/publish/deploy fail', 'pack ships stale/old bindings', 'my resource edit didn't take effect', 'refresh imported 0 bindings', deploy fails '[1009] Invalid argument Value', publish 'name+version / processKey collision', 'uip solution new: unknown command', 'coded app missing from the .uipx / not packed'. (Solution build-time/CLI faults belong here; faulted Orchestrator JOBS at runtime → uipath-troubleshoot.) Load BEFORE editing .uipx or running uip solution commands. For PDD→SDD design→uipath-planner; for an 'architect then deploy' two-phase request, run uipath-planner first, then return here to pack/deploy."

UiPath Solution — `uip solution` lifecycle

Create, pack, publish, deploy, and manage UiPath Solution packages (`.uipx`) via the `uip solution` CLI surface. A Solution bundles multiple automation projects (processes, tests, agent projects, API workflows) into a single deployable unit. A library is not one of them — it is published on its own and at most declared as a `Library` resource ([Develop a Solution § Step 2](references/develop-solution.md#step-2-add-existing-projects)).

> **Use the CLI. Don't roll your own REST for solution ops.** Hand-rolling HTTP calls misses the `X-UIPATH-OrganizationUnitId` folder header, OData filter shape, pagination envelope, `pipelinesInstall` deploy semantics, retry behavior, and the `Result/Code/Data` output contract. The CLI is the source of truth.

> **Platform support.** Solutions runs on Automation Cloud and on self-hosted Automation Suite **from `2.2510.0` onward**; not on Standalone Orchestrator. Available project types vary by AS version (Maestro self-hosted only from `2.2510.2`). Compat matrix + project-type-by-version table → [Solution Overview — Platform availability](references/solution-overview.md#platform-availability).

When to Use This Skill

<!--skill-flavor:when-to-use-uipx:start-->

• User has a `.uipx` solution and wants to pack / publish / deploy / activate / upload

<!--skill-flavor:when-to-use-uipx:end--> <!--skill-flavor:when-to-use-create:start-->

• User wants to create a new solution (`uip solution init`), add or remove projects, or refresh solution resources

<!--skill-flavor:when-to-use-create:end--> <!--skill-flavor:when-to-use-existing:start-->

• User wants to work on a solution that already exists in Studio Web, or move one to another org or tenant — start with `uip solution download` ([Start From an Existing Solution](#start-from-an-existing-solution))

<!--skill-flavor:when-to-use-existing:end-->

• User asks to set up a CI/CD pipeline that builds, publishes, and deploys a UiPath solution
• User mentions deploy configs, environment promotion, or activating a deployed solution

<!--skill-flavor:when-to-use-detected-uipx:start-->

• A skill or main agent detected a `.uipx` file and redirected the user here

<!--skill-flavor:when-to-use-detected-uipx:end-->

**Skip this skill** when:

• The task is PDD → SDD architecture/design (sdd.md / pdd.md) — load `uipath-planner`.
• The deployable is a single non-solution package (e.g., a one-off RPA library or coded app) — those use `uip rpa publish` / `uip codedapp publish` and route through `uipath-platform` or the relevant specialist.
• The task is non-solution Orchestrator work (folders, jobs, assets, queues, IS connections) — load `uipath-platform`.

CLI Surface Probe

<!--skill-flavor:cli-surface-probe:start--> Before the first `uip solution …` command in a session, probe the `solution` surface to detect pre- vs post-rename CLI:

uip solution init --help --output json

• Result `Success` → post-rename CLI (default). Use the commands and flags as documented in the references.
• `unknown command` / non-zero exit → pre-rename CLI. Translate via the table below before each call. Re-probe on any later `unknown command` error.

<!--skill-flavor:cli-surface-probe:end--> <!--skill-flavor:cli-unavailable:start-->

• `command not found` / `uip: not found` / `'uip' is not recognized` → CLI not installed. Tell the user to run the official installer (`curl -fsSL https://download.uipath.com/uipath-cli/install.sh | bash` on m