/uipath-ixp

name: uipath-ixp
description: "UiPath IXP (Document Understanding) via `uip ixp` — create projects (with autopilot taxonomy suggestion, an imported taxonomy file, or empty), upload/download/delete documents, author the taxonomy (field groups, fields, data types, per-field and overall extraction instructions), configure the extraction model and pre-processing, review/confirm/unconfirm predictions, mark fields missing, pull metrics and model versions, publish/tag/roll back model versions, deploy a trained version to an Orchestrator folder and move an existing deployment to another version (`deployments create`/`upgrade`/`list`). DO NOT TRIGGER during .flow / Maestro Flow work — discovering or listing IxP / document-extraction models, extractors, or nodes available to Maestro Flow, and adding or wiring an IxP node, belong to uipath-maestro-flow even when they sound like IXP model management."

UiPath IXP Document Extraction Assistant

Skill for working with UiPath IXP (Intelligent eXtraction Platform) projects — creating projects, uploading documents, reviewing predictions, and improving extraction quality.

When to Use This Skill

• User asks to create an IXP project, upload documents, or train a document extraction model
• User asks to label, review, or confirm document predictions
• User asks to improve extraction scores, prompts, or field instructions
• User asks to publish or manage IXP model versions
• User asks to deploy a trained model version to an Orchestrator folder, move a deployment to another version, or list where a project is deployed (`deployments create` / `upgrade` / `list`)
• User provides a taxonomy file to import into a project
• User asks for the project taxonomy at a specific trained model version — what the schema looked like when version N was published (use `deployments get-taxonomy <project-name> --version <N>`)

When NOT to Use This Skill — defer to uipath-maestro-flow

This skill covers standalone IXP-project work. STOP and invoke the `uipath-maestro-flow` skill instead when any of these hold:

• The user asks which IxP / document-extraction models, extractors, or nodes are available **to a `.flow` or Maestro flow** (a registry-listing question, not IXP-project management).
• The request is about adding, wiring, or referencing an IxP node **inside a flow**.
• The working context is a `.flow` file or a Maestro flow rather than a standalone IXP project.

Do not answer these from this skill. Re-activate `uipath-maestro-flow` and follow the commands it documents. This overrides Critical Rule 1.

**Exception — an inbound handoff from `uipath-maestro-flow`:** when that skill delegates because the user supplied documents and no published extractor covers them, the IXP work belongs here even though the surrounding context is a flow build. The handoff supplies the target Orchestrator folder — that is the caller's contract, not a question to re-ask. Create the project from the documents, deploy a trained version to that folder ([Deployment Guide](references/deployment-guide.md) — including the exit when no folder arrived), report the deployment, and hand control back — do not wire or edit the flow from this skill.

Critical Rules

1. **Verify `uip ixp` syntax before running a command** — use a targeted lookup in [CLI Reference](references/cli-reference.md) and copy the exact subcommand and options; never guess. If the request is not covered, report that the skill has no documented CLI path rather than improvising. Do NOT use curl, call REST APIs directly, or explore source code. (Exception: defer flow/Maestro registry questions to `uipath-maestro-flow` — see *When NOT to Use This Skill* above.) 2. **Run workflows end-to-end automatically** — do NOT ask the user to do individual steps. 3. **Always use `--output json`** when parsing CLI output programmatically. 4. **Use `/tmp/ixp/<project-name>/` as the working directory with this structure:**

   /tmp/ixp/<project-name>/
   ├── docs/         # Document files (<document-id>.pdf, .png, …) — downloaded once, reused across sessions
   ├── taxonomies/   # Taxonomy snapshots (v1.json, v2.json, …) — new version after each update-prompts
   └── payloads/     # One-shot JSON request files (Rule 5) — never reused

At the start of any workflow: `mkdir -p /tmp/ixp/<project-name>/{docs,taxonomies,payloads}`. If the directory already exists from a previous session, **reuse the files in `docs/` and `taxonomies/`** — do not re-download documents that are already present. Never reuse files in `payloads/` (Rule 5). Do NOT use the Write tool for `/tmp/ixp/` paths — on Windows it resolves to a different location than bash. 5. **Pass JSON options as files** — never inline the JSON or use `"$(cat ...)"`: Windows cmd/PowerShell strip the quotes inside it. Write the JSON to a file and pass it with `--updates-file <path>`, `--fields-file <path>` or `--choices-file <path>` in the **same command**. Bash: `cat > /tmp/ixp/<project-name>/payloads/field_updates.json << 'EOF' ... EOF` then `uip ixp fields update-prompts <project-name> --updates-file /tmp/ixp/<project-name>/payloads/field_updates.json`. PowerShell: `Set-Content -Encoding utf8 -Path <file> -Value @'` … `'@` then the same `uip` call with that file — without `-Encoding utf8`, Windows PowerShell writes ANSI and non-ASCII text is silently corrupted. Never pass a file you didn't write in that command: any earlier file, from this session or a previous one, holds stale names or occurrence indices. 6. **Never use `UID` as a variable name** — it is a readonly shell variable. Use `DOC_ID`, `DOCUMENT_ID`, etc. 7. **Always use the project `Name`, never the `Title`** — the `project list` output has both `Name` (e.g., `my_invoices-f1afa9ef-ixp`) and `Title` (e.g., `My_Invoices`). All CLI commands require the `Name` (the lowercase slug with UUID and `-ixp` suffix), NOT the `Title`. 8. **Review at field level, not document level** — review each predicted field individual