@uipath/skills 1.195.0 → 1.196.0

package/skills/uipath-platform/SKILL.md

@@ -1,13 +1,13 @@
 ---
 name: uipath-platform
-description: "UiPath platform ops via the uip CLI — use this skill for ANY task hitting UiPath Cloud / Orchestrator / Studio Web / Integration Service / LLM Gateway. Load BEFORE writing any code that calls a UiPath API. Covers auth, folders, assets, queues, storage buckets, bucket files, libraries, webhooks, triggers, processes, jobs, machines, users, roles, sessions, calendars, IS connectors/connections/activities, BYO LLM product configurations (`uip llm-configuration byo-connections` — register / audit / re-probe / troubleshoot tenant-owned OpenAI / Azure OpenAI / Bedrock / Vertex / Anthropic keys against UiPath products), traces, licensing. For `uip solution` lifecycle and PDD/SDD authoring→uipath-solution. For workflow code (.xaml/.cs)→uipath-rpa, .flow→uipath-maestro-flow, .bpmn→uipath-maestro-bpmn, agents (.py/agent.json)→uipath-agents, Test Manager→uipath-test."
-when_to_use: "User mentions UiPath / Orchestrator / Studio Web / Integration Service / LLM Gateway / 'uip' CLI / asset / queue / bucket / library / webhook / trigger / connector / connection / tenant / folder / robot / package / BYO LLM. Also 'upload to UiPath', 'create asset', 'start job', 'list queues', 'deploy a single package to Orchestrator', 'OAuth2 token', 'register my own LLM key', 'configure a model substitution', 'my BYO LLM key stopped working / returns errors', 're-probe / audit a BYO configuration', 'uipath.com REST'. Load BEFORE composing any HTTP request — most UiPath tasks have a `uip` command. For `uip solution` ops or `.uipx` deploys→uipath-solution."
+description: "UiPath platform ops via the uip CLI — use this skill for ANY task hitting UiPath Cloud / Orchestrator / Studio Web / Integration Service / LLM Gateway. Load BEFORE writing any code that calls a UiPath API. Covers auth, folders, assets, queues, storage buckets, bucket files, libraries, webhooks, triggers, processes, jobs, machines, users, roles, sessions, calendars, IS connectors/connections/activities, BYO LLM product configurations (`uip llm-configuration byo-connections` — register / audit / re-probe tenant-owned OpenAI / Azure OpenAI / Bedrock / Vertex / Anthropic keys), traces, licensing. For 'why did X fail' / root-cause / error investigations→uipath-troubleshoot. For `uip solution` lifecycle→uipath-solution. For PDD/SDD design & task planning→uipath-planner. For workflow code (.xaml/.cs)→uipath-rpa, .flow→uipath-maestro-flow, .bpmn→uipath-maestro-bpmn, agents (.py/agent.json)→uipath-agents, Test Manager→uipath-test."
+when_to_use: "User mentions UiPath / Orchestrator / Studio Web / Integration Service / LLM Gateway / 'uip' CLI / asset / queue / bucket / library / webhook / trigger / connector / connection / tenant / folder / robot / package / BYO LLM. Also 'upload to UiPath', 'create asset', 'start job', 'list queues', 'deploy a single package to Orchestrator', 'OAuth2 token', 'register my own LLM key', 'configure a model substitution', 'my BYO LLM key stopped working / returns errors', 're-probe / audit a BYO configuration', 'uipath.com REST'. For `uip solution` ops or `.uipx` deploys→uipath-solution."
 allowed-tools: Bash, Read, Write, Glob, Grep
 ---
 
 # UiPath Platform — uip CLI Assistant
 
-Comprehensive guide for UiPath Cloud / Orchestrator / Studio Web / Integration Service, end-to-end via the `uip` CLI. For `uip solution` lifecycle and PDD/SDD authoring, load [`uipath-solution`](/uipath:uipath-solution).
+Comprehensive guide for UiPath Cloud / Orchestrator / Studio Web / Integration Service, end-to-end via the `uip` CLI. For `uip solution` lifecycle load [`uipath-solution`](/uipath:uipath-solution); for PDD/SDD design & task planning load [`uipath-planner`](/uipath:uipath-planner).
 
 ## Use the CLI. Don't roll your own REST.
 
@@ -17,8 +17,8 @@ Hand-rolling HTTP calls — reading `~/.uipath/.auth` and POSTing to `/odata/...
 
 If you find yourself about to `curl` `https://cloud.uipath.com/...` — stop. Search the command index first. Examples of what people often miss:
 
-- "upload a file to a storage bucket" → `uip resource bucket-files upload` (NOT a `PUT /buckets/.../signedUrl` dance)
-- "create an asset" → `uip resource assets create` (NOT a `POST /odata/Assets`)
+- "upload a file to a storage bucket" → `uip or bucket-files upload` (NOT a `PUT /buckets/.../signedUrl` dance)
+- "create an asset" → `uip or assets create` (NOT a `POST /odata/Assets`)
 - "start a job for a process" → `uip or jobs start <process-key>` (NOT `POST /odata/Jobs/UiPath.Server.Configuration.OData.StartJobs`)
 - "configure an Integration Service connection" → `uip is connections create <connector-key>` (NOT a hand-rolled OAuth flow)
 
@@ -43,7 +43,7 @@ For `uip solution` lifecycle (init / pack / publish / deploy / activate / upload
 The CLI stores credentials at **`~/.uipath/.auth`** after login:
 ```
 UIPATH_URL=https://alpha.uipath.com
-UIPATH_ORG_NAME=my_org
+UIPATH_ORGANIZATION_NAME=my_org
 UIPATH_TENANT_NAME=my_tenant
 UIPATH_ACCESS_TOKEN=eyJ...
 UIPATH_ORGANIZATION_ID=...
@@ -58,7 +58,14 @@ This token can be reused for direct Orchestrator REST API calls when CLI command
 
 Before interacting with Orchestrator, solutions, or Integration Service, the user must be logged in.
 
-**Interactive login (browser OAuth2):**
+**Always check first** — most sessions are already authenticated:
+```bash
+uip login status --output json
+```
+
+If it reports `Logged in`, skip the rest of this step. There is no `--check` flag — `status` is the verification subcommand.
+
+**Interactive login (browser OAuth2):** `uip login` opens a browser window on the user's machine and blocks until they complete it. In a non-interactive or automated session, do NOT run it yourself — tell the user to run it and wait.
 ```bash
 uip login --output json
 ```
@@ -73,11 +80,6 @@ For non-interactive (CI/CD) scenarios, use client credentials:
 uip login --client-id "<ID>" --client-secret "<SECRET>" --tenant "<TENANT>" --output json
 ```
 
-Check login status:
-```bash
-uip login status --output json
-```
-
 ### Step 2 — Select a Tenant
 
 List available tenants and set the active one:
@@ -108,10 +110,10 @@ Choose the appropriate operation from the Task Navigation table below. For `uip
 | **Manage sessions and runtimes** | [references/orchestrator/manage-sessions.md](references/orchestrator/manage-sessions.md) |
 | **Tenant settings, calendars, audit logs** | [references/orchestrator/tenant-admin.md](references/orchestrator/tenant-admin.md) |
 | **Understand Orchestrator concepts** | [references/orchestrator/orchestrator.md](references/orchestrator/orchestrator.md) |
-| **Manage assets** | [references/resources/manage-assets.md](references/resources/manage-assets.md) |
-| **Work with queues and queue items** | [references/resources/process-queues.md](references/resources/process-queues.md) |
-| **Work with storage buckets and files** | [references/resources/work-with-storage.md](references/resources/work-with-storage.md) |
-| **Set up triggers and webhooks** | [references/resources/triggers-and-webhooks.md](references/resources/triggers-and-webhooks.md) |
+| **Manage assets** | [references/orchestrator/manage-assets.md](references/orchestrator/manage-assets.md) |
+| **Work with queues and queue items** | [references/orchestrator/process-queues.md](references/orchestrator/process-queues.md) |
+| **Work with storage buckets and files** | [references/orchestrator/work-with-storage.md](references/orchestrator/work-with-storage.md) |
+| **Set up triggers and webhooks** | [references/orchestrator/triggers-and-webhooks.md](references/orchestrator/triggers-and-webhooks.md) |
 | **Develop / pack / publish / deploy / activate solutions; set up CI/CD** | [/uipath:uipath-solution](/uipath:uipath-solution) |
 | **Debug LLM/agent traces (spans)** | [references/traces/traces.md](references/traces/traces.md) |
 | **Annotate traces with feedback** | [references/traces/feedback.md](references/traces/feedback.md) |
@@ -240,42 +242,13 @@ Every `uip` command accepts:
 - **For `uip solution` pack / publish / deploy / activate flows, load [`uipath-solution`](/uipath:uipath-solution).** This skill owns the auth and Orchestrator surface those flows depend on; the solution skill owns the lifecycle commands.
 - **Fallback: direct REST API.** When CLI tools don't support an operation, use the Orchestrator REST API with the access token from `~/.uipath/.auth`. See [references/orchestrator/orchestrator.md - REST API](references/orchestrator/orchestrator.md).
 
-## Orchestrator REST API (Fallback)
-
-When CLI commands are insufficient, use the Orchestrator REST API directly with the stored access token:
-
-```bash
-source ~/.uipath/.auth
-
-# Upload a .nupkg package
-curl -X POST "${UIPATH_URL}/${UIPATH_ORG_NAME}/${UIPATH_TENANT_NAME}/orchestrator_/odata/Processes/UiPath.Server.Configuration.OData.UploadPackage" \
-  -H "Authorization: Bearer ${UIPATH_ACCESS_TOKEN}" \
-  -H "X-UIPATH-OrganizationUnitId: <FOLDER_ID>" \
-  -F "file=@./MyProject.1.0.0.nupkg"
-
-# Create a process (release) from an uploaded package
-curl -X POST "${UIPATH_URL}/${UIPATH_ORG_NAME}/${UIPATH_TENANT_NAME}/orchestrator_/odata/Releases" \
-  -H "Authorization: Bearer ${UIPATH_ACCESS_TOKEN}" \
-  -H "Content-Type: application/json" \
-  -H "X-UIPATH-OrganizationUnitId: <FOLDER_ID>" \
-  -d '{"Name":"MyProcess","ProcessKey":"MyProject","ProcessVersion":"1.0.0"}'
-
-# Start a job
-curl -X POST "${UIPATH_URL}/${UIPATH_ORG_NAME}/${UIPATH_TENANT_NAME}/orchestrator_/odata/Jobs/UiPath.Server.Configuration.OData.StartJobs" \
-  -H "Authorization: Bearer ${UIPATH_ACCESS_TOKEN}" \
-  -H "Content-Type: application/json" \
-  -H "X-UIPATH-OrganizationUnitId: <FOLDER_ID>" \
-  -d '{"startInfo":{"ReleaseKey":"<RELEASE_KEY>","Strategy":"ModernJobsCount","JobsCount":1,"RuntimeType":"Unattended","InputArguments":"{}"}}'
-```
-
-The `X-UIPATH-OrganizationUnitId` header is the **folder ID** (get it from `uip or folders list`).
-
 ## References
 
 - **[CLI Command Reference](references/uip-commands.md)** — Every `uip` command with workflow links
 - **[Orchestrator](references/orchestrator/orchestrator.md)** — Concepts, folders, jobs, processes, machines, users
-- **[Resources](references/resources/resources.md)** — Assets, queues, buckets, triggers, libraries, webhooks
-- **[Solutions](/uipath:uipath-solution)** — Solution lifecycle (`uip solution init/pack/publish/deploy/activate`) and PDD/SDD authoring
+- **[Resources](references/orchestrator/resources.md)** — Assets, queues, buckets, triggers, libraries, webhooks
+- **[Solutions](/uipath:uipath-solution)** — Solution lifecycle (`uip solution init/pack/publish/deploy/activate`)
+- **[Planner](/uipath:uipath-planner)** — PDD/SDD design + multi-skill task planning (Process → Solution Design Document → task list)
 - **[Traces — Spans](references/traces/traces.md)** — LLM execution trace observability
 - **[Traces — Feedback](references/traces/feedback.md)** — Annotate traces with sentiment and comments
 - **[Integration Service](references/integration-service/integration-service.md)** — Connectors, connections, activities, resources

package/skills/uipath-platform/references/integration-service/http-request.md

@@ -8,7 +8,7 @@ Consumers: Maestro Flow, Maestro BPMN, API Workflows, Case Management, etc. Each
 
 ## What is Managed HTTP Request?
 
-A built-in way to make an HTTP call from a UiPath automation when there's no curated activity for it. Runs in two modes - **connector mode** and **manual mode**:
+A built-in way to make an HTTP call from a UiPath automation. Runs in two modes - **connector mode** and **manual mode**:
 
 | Mode | When | `url` | Auth |
 |---|---|---|---|
@@ -17,9 +17,11 @@ A built-in way to make an HTTP call from a UiPath automation when there's no cur
 
 ## Connector-Mode Rules
 
+- **Connector mode only works if the connector supports HTTP request activity** — verify by running `uip is connectors get "<connector-key>"` and checking the `HasHttpRequest` flag.
 - `url` must be **relative**. Wrong: `"url": "https://example.atlassian.net/rest/api/2/issue"`. Right: `"url": "/issue"`.
 - The connection's base URL is prepended automatically.
 - The auth header is applied automatically - do not set `Authorization`.
+- **`application/json` only - request and response.** No other content type is supported. File upload/download operations are the most common violation (`multipart/form-data`, `application/octet-stream`, binary/stream responses) - check the operation's request and response content types before authoring. If non-JSON, connector mode cannot call it - use a curated connector activity; if none exists, surface to the user.
 - Get the exact vendor base URL for a connection via (so you can compose the relative `url` correctly):
 
 ```bash
@@ -58,7 +60,7 @@ uip is resources run create "<connector-key>" http-request \
 | `method` | Yes | Uppercase HTTP verb |
 | `url` | Yes | **Relative** to the connection's vendor base URL (same convention as Managed HTTP Request connector mode) |
 | `headers` | No | Extra headers. Do NOT set `Authorization`. |
-| `body` | For POST/PUT/PATCH | **Stringified** JSON. Only `application/json` is supported today - non-JSON content types (form-urlencoded, XML, multipart, plain text) are not. |
+| `body` | For POST/PUT/PATCH | **Stringified** JSON. Only `application/json` is supported today — no other content type. |
 
 `http-request` command uses the same connection that Managed HTTP Request will use at runtime, so auth + base URL are applied automatically - same convention as Managed HTTP Request itself.
 
@@ -114,3 +116,4 @@ All steps 1-2 are GETs because we are in the authoring phase. The POST to `/issu
 2. **Do NOT use an absolute URL in connector-mode `url`.** Wrong: `"url": "https://example.atlassian.net/rest/api/2/project"`. Right: `"url": "/project"`.
 3. **Do NOT issue writes via CLI during authoring.** See "Read-Only During Authoring" above.
 4. **Do NOT guess the base URL.** Use `uip is connections base-url <connection-id>`.
+5. **In connector mode, request and response bodies are `application/json` only.** No other content type is supported; do NOT set `Content-Type` to anything else. Same rule applies to the `http-request` helper command body (it runs through a connection). Manual mode has no such limit — you supply your own `Content-Type` and body.

package/skills/uipath-platform/references/integration-service/reference-resolution.md

@@ -148,7 +148,9 @@ Some reference fields point to **search endpoints** that require user input as a
 
 ### How to detect
 
-If `reference.filterPattern` exists, the reference is a **search endpoint** — a plain `list` call without the filter will return no results or an error.
+If `reference.filterPattern` exists, the reference supports server-side filtering. Omitting the filter does NOT reliably error — some connectors (Microsoft Graph-backed: Teams, Outlook) return the **entire unfiltered collection** instead (thousands of rows, 50/page). Arbitrary query params (`searchTerm=`, `where=`, `filter=`) are silently ignored — only the exact `filterPattern` key filters. Always apply it; never brute-force paginate a large directory when a `filterPattern` exists.
+
+`filterPattern` is surfaced only by `uip is resources describe` (IS-level metadata). Representations that strip it (e.g. Maestro flow `registry get` reference object, which keeps only `objectName`/`lookupValue`/`lookupNames`/`path`/`childPath`) are not authoritative — re-describe at IS level before concluding a reference cannot be filtered.
 
 ### Resolution workflow (search)
 
@@ -178,6 +180,22 @@ User says: "Create a ticket for product Widget Pro"
    → `{ "productCode": "WP-100", "id": "1892000000056007" }`
 3. **Use** the `lookupValue` (`id`) → `"1892000000056007"` in `--body`
 
+### Example: Resolving a Microsoft Teams user (OData `$filter`)
+
+`filterPattern` may be a full OData `$filter` expression, not just `key={filter}`. Same mechanic: substitute `{filter}`, pass the whole string as `--query`.
+
+1. **Describe** the activity's object (e.g. `bot_direct_messages`) → `userId` reference has `filterPattern: "$filter=startswith(userPrincipalName,'{filter}')"`
+2. **Substitute and pass as `--query`.** Single-quote the value so the shell does not expand the literal `$`:
+   ```bash
+   uip is resources run list "uipath-microsoft-teams" "users" \
+     --connection-id "<id>" \
+     --query '$filter=startswith(userPrincipalName,'"'"'jane.doe'"'"')' --output json
+   ```
+   → one row: `{ "id": "7a621d6b-…", "userPrincipalName": "jane.doe@example.com" }`
+3. **Use** `lookupValue` (`id`) as the resolved value.
+
+Without the `$filter` this `/users` listing returns the full tenant directory (50/page, thousands of rows). A dedicated by-key endpoint (e.g. Teams `user-by-email/{email}`) is a fallback only when no `filterPattern` exists.
+
 > **If the user doesn't provide a search term**, ask them. Search references cannot be resolved without user input — do NOT call the search endpoint with an empty filter.
 
 ---

package/skills/uipath-platform/references/integration-service/triggers.md

@@ -11,6 +11,7 @@ Triggers are event-based activities that fire when something happens in an exter
 - [List Trigger Activities](#list-trigger-activities)
 - [Trigger Objects](#trigger-objects)
   - [`parameters[]` — canonical event-parameter input fields](#parameters--canonical-event-parameter-input-fields)
+- [Object Name Resolution](#object-name-resolution)
 - [Trigger Metadata (Describe)](#trigger-metadata-describe)
 - [CRUD vs Non-CRUD Triggers](#crud-vs-non-crud-triggers)
 - [Response Fields](#response-fields)
@@ -24,12 +25,14 @@ Triggers are event-based activities that fire when something happens in an exter
 
 ```
 [ ] 1. List trigger activities  →  pick one  →  note its **Operation**
-[ ] 2. If Operation is CREATED/UPDATED/DELETED  →  get objects  →  pick one
-[ ] 3. Get metadata (fields) for the chosen object + operation
+[ ] 2. If Operation is CREATED/UPDATED/DELETED  →  get objects  →  resolve object name (ask user if unclear)
+[ ] 3. Describe the resolved object + operation  →  field metadata
 ```
 
 **Decision point at step 2**: CREATED, UPDATED, and DELETED operations require an intermediate "objects" step. For other trigger operations, skip to step 3 using the activity's **ObjectName**.
 
+> **Source of truth:** Event-parameter inputs come from `triggers objects` → `parameters[]`. Field metadata comes from `triggers describe`. Configure trigger nodes exclusively from these two responses — do not invent parameters or fields, and do not substitute metadata from other commands.
+
 ---
 
 ## List Trigger Activities
@@ -60,20 +63,33 @@ uip is triggers objects "<connector-key>" "<OPERATION>" \
 
 ---
 
+## Object Name Resolution
+
+`triggers describe` requires an exact object name. Resolve it from the `triggers objects` response (`Data[].Name`):
+
+1. Match the user's intent against each object's `Name` / `DisplayName` (case-insensitive).
+2. Exactly one match → use its `Name` verbatim.
+3. No match or ambiguous → **ask the user** — present candidate objects by `displayName`. Do NOT guess or fabricate an object name; `triggers describe` with a wrong name returns empty or wrong field metadata.
+
+For non-CRUD operations there is no objects step — use the trigger activity's **ObjectName** field directly.
+
+---
+
 ## Trigger Metadata (Describe)
 
 Get field metadata for a trigger object:
 
 ```bash
-uip is triggers describe "<connector-key>" "<OPERATION>" "<object-name>" --output json
-
-# With connection (includes custom fields):
 uip is triggers describe "<connector-key>" "<OPERATION>" "<object-name>" \
   --connection-id "<id>" --output json
 ```
 
 Returns field definitions with names, types, and descriptions. Always requests `allFields=true` from the API.
 
+- `<object-name>` comes from [Object Name Resolution](#object-name-resolution) above
+- Always pass `--connection-id` — without it, results omit custom/connection-specific fields
+- The returned fields are the **source of truth** for the trigger's field metadata. Use them verbatim — do not guess field names
+
 ---
 
 ## CRUD vs Non-CRUD Triggers

package/skills/uipath-platform/references/licensing/consumables-report.md

@@ -16,7 +16,7 @@ Report consumption of consumable license units (`AIU`, `AGU`, `RU`, `PLTU`, `HEA
 
 ## Prerequisites
 
-1. Authenticated: `uip login`
+1. Authenticated — verify with `uip login status`; if not, ask the user to run `uip login` (interactive browser flow)
 2. Org admin permissions to read account product allocations
 3. For `daily` / `folders` modes: know the target tenant name and consumable unit code
 

package/skills/uipath-platform/references/licensing/tenant-allocations.md

@@ -15,7 +15,7 @@ Allocate license units (`UNATT`, `RU`, `PLTU`, `NONPR`, etc.) from the account p
 
 ## Prerequisites
 
-1. Authenticated: `uip login`
+1. Authenticated — verify with `uip login status`; if not, ask the user to run `uip login` (interactive browser flow)
 2. Org admin permissions to allocate licenses
 3. Tenant key (GUID) of the target tenant — discover with `uip or settings list --tenant <name>` or the Automation Cloud portal
 

package/skills/uipath-platform/references/licensing/user-licenses-allocations.md

@@ -17,7 +17,7 @@ Assign user-bundle licenses (e.g., `RPADEVPRONU`, `ATTUNU`, `TSTNU`) directly to
 
 ## Prerequisites
 
-1. Authenticated: `uip login`
+1. Authenticated — verify with `uip login status`; if not, ask the user to run `uip login` (interactive browser flow)
 2. Org admin permissions for license allocation
 3. For `users licenses set/get`: the user is resolvable from a directory search — name or email prefix must match **exactly one** user
 4. For `groups rules details/set`: the group name prefix must match **exactly one** group

package/skills/uipath-platform/references/{resources → orchestrator}/manage-assets.md

@@ -2,7 +2,7 @@
 
 Create configuration assets, share them across folders, and manage credential rotation.
 
-> For full option details on any command, use `--help` (e.g., `uip resource assets create --help`).
+> For full option details on any command, use `--help` (e.g., `uip or assets create --help`).
 
 ## When to Use
 
@@ -13,8 +13,8 @@ Create configuration assets, share them across folders, and manage credential ro
 
 ## Prerequisites
 
-- Authenticated (`uip login`)
-- Target folder exists (see [setup-environment.md](../orchestrator/setup-environment.md))
+- Authenticated — verify with `uip login status`; if not logged in, ask the user to run `uip login` (it opens an interactive browser flow)
+- Target folder exists (see [setup-environment.md](setup-environment.md))
 - For Credential/Secret types: a credential store must exist (`uip or credential-stores list`)
 
 ## Flow
@@ -38,13 +38,13 @@ graph LR
 Create a named configuration value in a folder. Type defaults to Text.
 
 ```bash
-uip resource assets create "ApiBaseUrl" "https://api.example.com" \
+uip or assets create "ApiBaseUrl" "https://api.example.com" \
   --folder-path "Finance" --type Text --output json
 
-uip resource assets create "MaxRetries" "3" \
+uip or assets create "MaxRetries" "3" \
   --folder-path "Finance" --type Integer --output json
 
-uip resource assets create "FeatureEnabled" "true" \
+uip or assets create "FeatureEnabled" "true" \
   --folder-path "Finance" --type Bool --output json
 ```
 
@@ -62,11 +62,11 @@ Key options:
 For Credential and Secret types, you must provide `--credential-store-key`:
 
 ```bash
-uip resource assets create "DbPassword" "s3cret-value" \
+uip or assets create "DbPassword" "s3cret-value" \
   --folder-path "Finance" --type Secret \
   --credential-store-key <store-key> --output json
 
-uip resource assets create "ServiceAccount" "svc-user:p@ssw0rd" \
+uip or assets create "ServiceAccount" "svc-user:p@ssw0rd" \
   --folder-path "Finance" --type Credential \
   --credential-store-key <store-key> --output json
 ```
@@ -76,13 +76,16 @@ uip resource assets create "ServiceAccount" "svc-user:p@ssw0rd" \
 List assets in a folder. Requires `--folder-path` or `--folder-key`.
 
 ```bash
-uip resource assets list --folder-path "Finance" --output json
+uip or assets list --folder-path "Finance" --output json
 
 # Filter by name (contains match)
-uip resource assets list --folder-path "Finance" --name "Api" --output json
+uip or assets list --folder-path "Finance" --name "Api" --output json
 
 # Filter by type
-uip resource assets list --folder-path "Finance" --type Secret --output json
+uip or assets list --folder-path "Finance" --type Secret --output json
+
+# List assets across all accessible folders
+uip or assets list --all-folders --output json
 ```
 
 If the user already gives a folder name or path, pass it directly as
@@ -95,7 +98,7 @@ the asset is not present.
 Get full asset metadata by key. Cross-folder -- no `--folder-path` needed.
 
 ```bash
-uip resource assets get <asset-key> --output json
+uip or assets get <asset-key> --output json
 ```
 
 **Note:** Credential and secret values are NOT returned by `get`. Use `get-asset-value` to retrieve decrypted values.
@@ -105,7 +108,7 @@ uip resource assets get <asset-key> --output json
 Returns the decrypted asset value for the current user. Requires `--folder-path` or `--folder-key`.
 
 ```bash
-uip resource assets get-asset-value <asset-key> \
+uip or assets get-asset-value <asset-key> \
   --folder-path "Finance" --output json
 ```
 
@@ -117,14 +120,14 @@ Update an existing asset's value, type, scope, or metadata. Cross-folder -- no `
 
 ```bash
 # Update value
-uip resource assets update <asset-key> "https://api-v2.example.com" --output json
+uip or assets update <asset-key> "https://api-v2.example.com" --output json
 
 # Update description and tags
-uip resource assets update <asset-key> --description "Updated endpoint" \
+uip or assets update <asset-key> --description "Updated endpoint" \
   --tags "production,api" --output json
 
 # Change scope
-uip resource assets update <asset-key> --scope PerRobot --output json
+uip or assets update <asset-key> --scope PerRobot --output json
 ```
 
 Only provided fields are changed -- omitted fields keep their current values.
@@ -134,7 +137,7 @@ Only provided fields are changed -- omitted fields keep their current values.
 Make an asset accessible in an additional folder:
 
 ```bash
-uip resource assets share <asset-key> --folder-path "Production" --output json
+uip or assets share <asset-key> --folder-path "Production" --output json
 ```
 
 ## Step 7: Check Where Shared
@@ -142,7 +145,7 @@ uip resource assets share <asset-key> --folder-path "Production" --output json
 List all folders where the asset is currently accessible:
 
 ```bash
-uip resource assets get-folders <asset-key> --output json
+uip or assets get-folders <asset-key> --output json
 ```
 
 Returns `accessibleFolders` (array of folders you can see) and `totalFoldersCount` (total, including folders you lack permission to view).
@@ -152,7 +155,7 @@ Returns `accessibleFolders` (array of folders you can see) and `totalFoldersCoun
 Remove the asset from a folder:
 
 ```bash
-uip resource assets unshare <asset-key> --folder-path "Production" --output json
+uip or assets unshare <asset-key> --folder-path "Production" --output json
 ```
 
 ## Step 9: Delete
@@ -160,7 +163,7 @@ uip resource assets unshare <asset-key> --folder-path "Production" --output json
 Delete the asset entirely. Cross-folder -- no `--folder-path` needed.
 
 ```bash
-uip resource assets delete <asset-key> --output json
+uip or assets delete <asset-key> --yes --output json
 ```
 
 ---
@@ -171,23 +174,23 @@ Rotate a secret without downtime:
 
 ```bash
 # 1. Create the replacement secret
-uip resource assets create "DbPassword-v2" "new-s3cret" \
+uip or assets create "DbPassword-v2" "new-s3cret" \
   --folder-path "Finance" --type Secret \
   --credential-store-key <store-key> --output json
 
 # 2. Share with all folders that use it
-uip resource assets share <new-key> --folder-path "Production" --output json
+uip or assets share <new-key> --folder-path "Production" --output json
 
 # 3. Update consuming processes to reference the new asset name
 #    (or update the original asset in-place if the name must stay the same)
-uip resource assets update <original-key> "new-s3cret" --output json
+uip or assets update <original-key> "new-s3cret" --output json
 
 # 4. Verify the new value resolves correctly
-uip resource assets get-asset-value <asset-key> \
+uip or assets get-asset-value <asset-key> \
   --folder-path "Finance" --output json
 
 # 5. Delete the old version (if you created a new asset instead of updating)
-uip resource assets delete <old-key> --output json
+uip or assets delete <old-key> --yes --output json
 ```
 
 ---
@@ -198,30 +201,30 @@ Set up environment configuration for a Finance folder with text, integer, and se
 
 ```bash
 # Create text asset
-uip resource assets create "ApiBaseUrl" "https://api.example.com" \
+uip or assets create "ApiBaseUrl" "https://api.example.com" \
   --folder-path "Finance" --type Text \
   --description "Production API endpoint" --output json
 
 # Create integer asset
-uip resource assets create "MaxRetries" "5" \
+uip or assets create "MaxRetries" "5" \
   --folder-path "Finance" --type Integer \
   --description "Maximum retry attempts" --output json
 
 # Create secret asset (requires credential store)
-uip resource assets create "ApiKey" "sk-prod-abc123" \
+uip or assets create "ApiKey" "sk-prod-abc123" \
   --folder-path "Finance" --type Secret \
   --credential-store-key <store-key> \
   --description "Production API key" --output json
 
 # Share secret with Production folder
-uip resource assets share <api-key-asset-key> \
+uip or assets share <api-key-asset-key> \
   --folder-path "Production" --output json
 
 # Verify sharing
-uip resource assets get-folders <api-key-asset-key> --output json
+uip or assets get-folders <api-key-asset-key> --output json
 
 # Confirm value is accessible from Production
-uip resource assets get-asset-value <api-key-asset-key> \
+uip or assets get-asset-value <api-key-asset-key> \
   --folder-path "Production" --output json
 ```
 
@@ -234,7 +237,7 @@ uip resource assets get-asset-value <api-key-asset-key> \
 Credential type assets require `username:password` format. The colon separates the username from the password:
 
 ```bash
-uip resource assets create "WinCred" "DOMAIN\\user:p@ssw0rd" \
+uip or assets create "WinCred" "DOMAIN\\user:p@ssw0rd" \
   --folder-path "Finance" --type Credential \
   --credential-store-key <store-key> --output json
 ```
@@ -247,7 +250,7 @@ uip resource assets create "WinCred" "DOMAIN\\user:p@ssw0rd" \
 
 | Command | Folder required? |
 |---------|-----------------|
-| `list` | Yes (`--folder-path` or `--folder-key`) |
+| `list` | Yes (`--folder-path` or `--folder-key`), or pass `--all-folders` to list across all accessible folders |
 | `create` | Yes |
 | `get-asset-value` | Yes |
 | `get` | No (cross-folder) |
@@ -274,4 +277,4 @@ Decimals and non-numeric strings are rejected.
 ## Related
 
 - [resources.md](resources.md) -- Overview of all resource commands
-- [setup-environment.md](../orchestrator/setup-environment.md) -- Create folders before creating assets
+- [setup-environment.md](setup-environment.md) -- Create folders before creating assets

package/skills/uipath-platform/references/orchestrator/manage-sessions.md

@@ -14,7 +14,7 @@ Monitor robot sessions, check runtime availability, toggle debug mode, and manag
 
 ## Prerequisites
 
-- Authenticated (`uip login`)
+- Authenticated — verify with `uip login status`; if not logged in, ask the user to run `uip login` (it opens an interactive browser flow)
 - Environment set up with folders and machines (see [setup-environment.md](setup-environment.md))
 
 ---

package/skills/uipath-platform/references/orchestrator/orchestrator.md

@@ -19,6 +19,7 @@ All `uip or` commands share a set of cross-cutting options:
 | `--sort-by <field>` | List commands | OData-style sort (e.g., `'Name asc'`, `'Id desc'`). |
 | `--all-fields` | Most get/list commands | Return the full API DTO instead of the curated summary. Use when you need a field the curated view drops. Note: curated keys are PascalCase, raw DTO keys are camelCase — the shapes do not share casing. |
 | `--output-filter <expr>` | All commands | JMESPath expression to filter/reshape JSON output (e.g., `--output-filter "Data[].Key"`). |
+| `-y, --yes` | Delete commands | Confirm the irreversible operation. Required — the CLI never prompts; without it the command fails with "Confirmation required". Where a command also has `--force` (e.g. non-empty `queues`/`buckets` delete), `--force` implies `--yes`. |
 
 **Pagination pattern.** List responses include a `Pagination` block with `Returned`, `Limit`, `Offset`, and `HasMore`. When `HasMore` is `true`, increment `--offset` by `--limit` and fetch again. Continue until `HasMore` is `false` or `Returned < Limit`.
 
@@ -92,39 +93,11 @@ The CLI uses GUID keys for all entity references. Numeric IDs are never exposed
 
 ## REST API Fallback
 
-When the CLI does not cover an operation, use the Orchestrator REST API directly with a stored token from `~/.uipath/.auth`.
-
-**Base URL pattern:**
-
-```
-${UIPATH_URL}/${UIPATH_ORG_NAME}/${UIPATH_TENANT_NAME}/orchestrator_/odata/
-```
-
-**Auth header:**
-
-```
-Authorization: Bearer <UIPATH_ACCESS_TOKEN>
-X-UIPATH-OrganizationUnitId: <FOLDER_ID>
-```
-
-Always check `uip or --help` and `uip resource --help` first -- most operations are covered by the CLI. Only fall back to REST when there is no CLI command for the operation you need.
-
-**Example -- list triggers (no CLI command yet):**
-
-```bash
-ACCESS_TOKEN=$(cat ~/.uipath/.auth | jq -r '.access_token')
-BASE_URL="https://cloud.uipath.com/myorg/mytenant/orchestrator_/odata"
-
-curl -s -G "${BASE_URL}/ProcessSchedules" \
-  -H "Authorization: Bearer ${ACCESS_TOKEN}" \
-  -H "X-UIPATH-OrganizationUnitId: <FOLDER_ID>" | jq .
-```
-
-Token expiry: re-run `uip login` if you get a 401.
+When the CLI does not cover an operation, you can fall back to the Orchestrator REST API using the access token stored in `~/.uipath/.auth`. Always check `uip or --help` first — most operations are covered by the CLI, and a command is safer and more consistent than hand-rolled REST. Only reach for REST when there is genuinely no command for what you need (and consider reporting the gap so the CLI can cover it).
 
 ---
 
 ## Related
 
-- **Resources** (`uip resource`) — assets, queues, triggers, buckets, webhooks, libraries → [`uipath-resources`](../resources/resources.md)
-- **Solutions** (`uip solution`) — pack, publish, deploy solution packages → [`uipath-solution`](../solution/solution.md)
+- **Resources** (`uip or`) — assets, queues, triggers, buckets, webhooks, libraries → [resources.md](resources.md)
+- **Solutions** (`uip solution`) — pack, publish, deploy solution packages → [`uipath-solution`](/uipath:uipath-solution)